JoeViking245

On method is to use a plugin as it's not innate to LaunchBox. This post has an ini file for vertical [MAME] games, but it's about a year and a half old. There are instructions on how to get create your own. Also, 2 posts below it tells how to 'fix it' if you create your own following the instructions. 😊 Then at the top of the page is the plugin that can create the playlist for you.

Well, I have never seen this before. Both of these games say the display is rotated 180º. lol But when I load them here, they look fine. Start the game (either one), press Tab, select Video Options, Screen #0, Rotate. If it says None, you got something screwy. Press the right arrow key until the display is right-side up. Once it's correct, Press Tab, then Escape to exit the game. Start the [same] game again and see if it's now showing correctly.

If there are other games doing this, which ones? (may help narrow things down) Plan "B": Look to see if you have the file /MAME/ini/splater.ini. (It may be in your MAME root folder instead.?.?..) If you see one, delete it (or move it). And try again.

Look for a file in your /MAME/cfg/ called splatter.cfg and delete it (or move to somewhere else). Open the game again and see if it's still uʍop ǝpᴉsdn.

On the menu bar, select View, Show / Hide, Versions. Or press Ctrl+R.

Are you putting them in the Running Script section? Can you show what you've tried? I've never use Xemu, but this person said this one worked.

Another approach that's a little less 'hacky' (and possibly a little more stable/reliable) is to create an AHK script and use that as your emulator. This way you can use %1% to get the "FULL\PATH\TO\ROM\FILE". (actually it may be %4% because of the other parameters) Just throwing out options.

I've never used that emulator... but are you sure? "In addition to supporting uncompressed games, Mednafen supports loading games from several different compressed file formats. For non-CD games, Mednafen supports loading from naked gzip- and Zstandard-compressed files, and ZIP archives."

Sure it does. The top half is the Auto Execution Section and the bottom half are the HotKeys. As soon as you start the script, the hotkeys are all active, while the top half executes in-order. (At least it does when I changed your game and LEDBlinky to notepad and wordpad. ) Does the auto execution section seem to be working properly when you run the game with the single script? It's just when, in-game, pressing "1" doesn't "press F"? If instead, you press "f" directly, does that work (like it's supposed to)? I presume 1, a, c, d, s are all used for the game (vs some LEDBlinky function)? I've never used LED-B, so I have no idea how all it works. Maybe put the test MsgBox back in (for testing/troubleshooting). Also test with exaggerating the Sleep timer (10 seconds?). Coul also try adding another WinWait, ahk_exe backtobed.exe after the Sleep timer.?.?. But it 'should' work as one script. ....or just stick with the 2 scripts. 😊

It sounds like you un-checked Check for Updates and/or Update to Beta Releases after you clicked No on the "Do you want to install the update now? popup. When it's set to check for updates and there is an update, and you then click No (don't install), LaunchBox creates a temporary file in the /Updates/ folder called "UpdateStatus" (no file extension). This tells LaunchBox/BigBox to [automatically] install the update next time it starts. When you do got to install it again, 1st delete the file ../LaunchBox/Updates/UpdateStatus, if it exists. Run the installer and then when LaunchBox starts, go to Tools, Options and make sure the Update boxes are un-checked, and click OK. (Just to be sure....) now exit LaunchBox normally and look in the /Updates/ folder. If there's a file called "UpdateStatus", delete it. You should be good-to-go.

Nicely done. And it shouldn't be any different when running in BB. ;One file, set to Run Before WinWait, ahk_exe backtobed.exe ; wait for the exe to load Sleep 5000 ; wait 5 seconds to allow for the random re-opening Run, C:\Users\Arcade\LaunchBox\LEDBlinky\LEDBlinky.exe BACK_TO_BED WINDOWS ; Run LEDBlinky with the correct ROM WinWaitClose, ahk_exe backtobed.exe ; Wait for game to close Run, C:\Users\Arcade\LaunchBox\LEDBlinky\LEDBlinky.exe 4 ; Tell LED Blinky game has closed ExitApp 1::f a::Space c::Send, {Wheelup 6} d::Send, {WheelDown 6} s::f

Ahh... you're right. MAME -listxml does list the display types for each machine. <!ATTLIST display type (raster|vector|lcd|svg|unknown) #REQUIRED> So the only thing the LB developers would need to do is add a new element to their metadata when they parse -listxml and add a new field the UI. Then adjust any other methods that are affected by this. Including Search, Filters and Arrange By. Sounds simple enough. Because this unique to just the MAME/Arcade platform, it'd probably only happen by an upvoted Feature Request and then a "popularity vote" on the Community Poll. I've recall people asking about Arcade display types once or twice (or more?) since I've been here, so it may already be on BitBucket.

Not really sure what to say about the game(s) that launch using "steam:..." where Run Before AND the Run After both do work. I wonder if you rebooted your computer and tried these games again, if it (Run After) will still work? The ones where you tried the exe directly and run after doesn't work, those few might have a similar 'launcher' affect. That all depends on how determined and creative you're feeling.

You're probably launching directly to the games .exe file (vs "steam://rungameid/xxxxxx") for these.

LaunchBox doesn't store display type information about Arcade machines. So it can't be filtered. In fact, there isn't really an up-to-date definitive list that sorts by display types for MAME. I think your only option might be to create a Playlist for each one. You'd 1st need to manually generate a list for each display type (see attached). The Arcade Database can help you with that using their Additional Filters and then exporting the results to an ini file(s). MAME Raster.ini MAME Vector.ini Next, install the plugin that can create playlists using these ini files and follow the How to use instructions.

As Retro808 said, you can put the ROMs anywhere you want. But MAME needs to somehow still know where they are. An alternate to adding the path in MAME itself, you can add edit your MAME emulator in LaunchBox and add to your Default Command-Line Parameters -rompath %romlocation% Then if you move them again (aka, import them into some other folder), when you load the game, this will tell MAME exactly where the ROM is.

First, note that the Exit Script is only for when exiting from the Pause menu. As you've discovered, you can't pass a variable to a Running Script, an Exit Script nor an Additional App. But you can get creative and find them. To get the "FULL\PATH\TO\ROM\FILE" from inside a Running Script, you can follow this example. In this post, it gets the variables passed to "hoxs64,exe". Change that to "vmware.exe". After that part, you'll need to add an overriding escape sequence so you can run the vmrun.exe sequence. Making use of the appropriate variable you extracted. Something along the lines of: $Esc:: { RunWait, "C:\Program Files (x86)\VMware Workstation\vmrun.exe" stop "%theVariableYouExtracted%",,Hide Run, "C:\Program Files (x86)\VMware Workstation\vmrun.exe" reverToSnapshot "%theVariableYouExtracted%" LaunchBox,,Hide WinClose, ahk_exe vmware.exe }

I see a couple of options. You could create a shortcut to the batch file. Then right-click the shortcut and select Properties. In there, set Run: to Minimized. Then point your game to the shortcut instead of the actual batch file. Alternately, have a batch file that [only] replaces the ini file and set the game to launch with DEmul as normal. Next, add an Additional App to the game that will run this batch file Before Main Application and check the box Wait for exit.

Change the LaunchBox Games Database login credentials.

Do a Google search for something like "LaunchBox MAME hlsl". You should be able to find enough info to give you MAME HLSL sensory overload.

Tools, Manage, Emulators. Select your MAME emulator and click Edit. Looke at where it says Default Command-Line Parameters. If it is in there, try removing it and click OK (to save the change). Then start a game and look at what (if any) changes you see.

In LaunchBox, for your MAME emulator, do you have anything like "-nofilter" listed in the Default Command-line Parameters?

It depends on if they updated the [individual] ROM. If you have a ROM for v0.230 and your mame.exe is 0.249, if they haven't updated the ROM in 19 versions you should be fine. BTW, there's no easy way to determine which version your ROM set is for. Most of the time when you find a set, they should say for what version of MAME they are. If not, you're playing roulette. If you had LB install it for you, you manually changed the default command-line parameters. Edit your MAME emulator and add a Space and then this right after "dinput" -rompath %romlocation%