JoeViking245

Well, you shouldn't have to. "pressing Alt+Enter" was meant to be symbolic of what the script does (on the 2nd line). If you don't mind physically pressing Alt+Enter yourself, you can remove those 2 lines altogether. What the script is supposed to do is: (green = the actual script. orange = description of what it's doing.) Sleep, 9500 ;Wait 9.5 seconds Send {Alt Down}{Enter}{Enter Up}{Alt Up} ;"Press" Alt+Enter

If you weren't getting fullscreen before, then you usually need to increase the delay time. aka, wait longer before pressing Alt+Enter. If it's still not working after increasing it, try something crazy like 20 seconds (20000). Start the game and wait at least 20 seconds to see (1) the emulator load, and (2) the script sending it to fullscreen. If after 25 seconds the emulator has loaded but nothing changed, edit the emulator (in LaunchBox) and share with us a screenshot of the Running Script section.

The Sleep, 9500 is the 'delay time' in milliseconds. 9500 = 9.5 seconds.

In short, No. Which platforms specifically did the fresh installation install? A new install 1st launch will scan for StoreFront games you have. But should not be looking-for/auto-installing regular platform console games (i.e. Atari 2600, Playstation etc.).

In MAME, you need to manually configure it for XInput. This might be able to help you along.

My guess is that the auto-play videos feature is part of the Video Playback Support which is not available in the free version.

My antique test PC with no GPU will do that sometimes (Rarely. But sometimes). I've always been able to click Wait for the program to respond, exhibit a little patience in waiting (that means no clicking around on things and just wait), and shortly thereafter have LaunchBox continue as normal.

If it's the same theme as here: Slipstream Theme - Custom Themes - LaunchBox Community Forums ...that particular theme was created using the Community Theme Creator (CTC), a 3rd party [paid for] GUI app to create Big Box themes. You can find the CTC files for the theme here: Slipstream CTC-files - Custom Themes - LaunchBox Community Forums You can edit the .xaml Views files with any text editor. But I'm not sure (never really looked) if there are tutorials/videos available for doing so this way ("manually"). Also, CTC adds in a bunch of [useful] plugin code to make the views do what they do. And could be difficult to decipher when just starting out with XAML. This link... well, is pretty self-describing by its title: Tips for using the Community Theme Creator - video bookmarks and other notes - Custom Theme Tutorials - LaunchBox Community Forums.

Correct. From the Windows Command Prompt within your Dolphin emulators folder, you can type dolphin.exe -h [and press Enter] to get a list and descriptions of the available parameters.

Pretty sure the -b ("batch") parameter is what hides/disables the UI.

Using Custom platform icon images is not available in the free version. If you decide to get a premium license, then it's simply a matter of placing the image files in your /LaunchBox/Images/Platform Icons/Platforms/ folder. i.e. DREAMM.png Installed eXoDOS Games.png ScummVM SVN.png

Yeah, I hear ya. So just contact Support, state your case (just as a formality) as to why you want to change the name that shows and what name you wish to appear. "ABC123" might not still be available, so you may need to get creative. jk You could probably also inquire there about the background history of the display names and any further thoughts. They're the ones (well, the only ones) that can address the issue/concern/thoughts/opinions/changes/etc. regarding the names.

I think we agree that 'a name' needs to be there. Do you think a better way might be, being able to change the name that appears in LaunchBox to something like a username? Or to some other name you wouldn't mind having plastered on your videos/screenshots?

You can’t remove it because it’s a security feature (as you presumed). You can email support (support@unbrokensoftware.com) and ask them to change it though if you’re streaming or something similar and have a personal security issue with your real name being displayed.

No. The LaunchBox folder structure is "self contained" (i.e. Images and Videos folders are inside the LaunchBox folder). Being setup that way, LaunchBox uses relative paths to those [and all folders within the structure]. You may be able to get creative and setup symlinks to the folders you "wish to leave behind".

Relatively old post, recently revived (and expanded upon in the above-linked Feature Request) by @crusadeRGP. From the OP question, this can be accomplished by editing the emulator (i.e. MAME) in LaunchBox. In the Pause Script section, add the following: file = Full/path/to/ArcadeAmbianceSounds.mp3 SoundPlay, %file%, wait Change the path and MP3 filename to match your location. .mp3 files works best. But some other audio file types may work as well. This is a one-emulator, one-song kind of thing. As in, you need to set it up on a per emulator basis. Which is good because you can select a different 'song' based on the emulator. You can also do this per game. Edit the game, go to the Startup/Pause section, check Override default Pause.... Click Customize and in the On Pause section, place the above code, respectively. Getting a little crazy, you could create an array of files and then have SoundPlay 'pick' a random file from the array. Yes. This is all "manual labor". But the take-away is, it can be done natively from within LaunchBox. 😎

If you by-chance have a Pixelcade marquee, you could use this plugin to create them for you. Or if you'd prefer to 'play' with Python, continue on.

The [GUID] Image FileName shown is how it's stored on the Games Database website. In normal operations when you download the image, LaunchBox will rename the image file to your games' Title (replacing invalid characters with _ (underscore)) and adding the 'next available image count' (in your case, -01). Then of course, keeping the file extension. If you're wanting to get the images you have already per game, you'd need to look in your Images folder. LaunchBox doesn't store information anywhere about your local images. It simply looks in the respective folder(s).

When launching a MAME game from LaunchBox, I can't say I've ever heard of it only opening the MAME UI. Unless of course when you right-click a game and select Open MAME. Usually if there's an issue, you'd see a flicker of a black screen, then it goes right back to LaunchBox. The only thing I can think of that may be the issue is the ROMs being in the root of the drive (vs in a folder), in conjunction with using the -rompath parameter to tell MAME where the ROMs are located. Not that using the parameter is bad. It's it pointing to a root drive instead of a folder. As a test, could you put a rom into a folder, change the games path in LaunchBox to this [test] location and try launching it? I always use 1942 (1942.zip) because it's near the top and easy to find. So maybe try something like D:\games\1942.zip and see if that launches correctly. EDIT: Just did some testing and appears MAME doesn't like (or doesn't know how) looking in a root drive for ROMs. aka, you need to place the ROMs into a folder. You can create the folder name of your choosing and move the ROMs there. Then in LaunchBox, in the Arcade platform, select a game then press Ctrl+A to select all games. Then go to Tools < File Management < Change ROMs Folder Path for Selected Games... and point to the new folder they're in.

Thanks for the screenshots. Are your MAME ROMs really located in the root of your D drive? If so, that's fine. A little unusual. But fine. Also in the same location, do you have the file namcoc71.zip? (required along with timecris.zip for Time Crisis to run)

To better help you, can you please share some screenshots of how it's setup in LaunchBox? Edit your MAME emulator and show screenshots of - the Main Details section - the Associated Platforms section Edit one of your Arcade games and show screenshots of - the main Metadata section - the Launching section - the Emulation section

Ya, rename it back. Now that you have the DB ID# associated with, you're good to go.