JoeViking245

Because of how AHK reads one button and then the other, LaunchBox's Exit Game might intercept the combo-press 1st. You said the script and the Lightgun software are still running when pressing the [LB] button combo (and I assume the mouse wasn't restored also), but not when shooting offscreen or pressing Escape. I assume the latter are triggering the escape hotkey sequence (and those 2 methods still worked with the 'new' code that uses the ExitRoutine() method). Take 2: Essentially what's happening, if the emulator is closed via the Exit Game button combo, the script (still running) will 'see' that the emulator isn't running [any more] and jump to ExitRoutine(). Hopefully resolving the issue. #SingleInstance Force SetWorkingDir C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun Process, Exist, Lightgun.exe If (!ErrorLevel = 0) { Process,Close,Lightgun.exe Sleep, 1000 } Run, C:\Utils\Sinden Lightguns\Mouse Mode - RPCS3\Lightgun.exe Run, C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\rpcs3.exe C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\games\BCES01070\PS3_GAME\USRDIR\timecrisis4.self --config "C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\config\custom_configs\config_BCES01070_tc4_2p.yml" Sleep, 1000 Run, C:\Utils\NoMousy\NoMousy.exe /hide ;Hides mouse cursor with NoMousy Process, WaitClose, rpcs3.exe ExitRoutine() ;Start Button $MButton:: { send {LButton down} sleep, 60 send {MButton down} sleep, 20 send {MButton up} sleep, 60 send {LButton up} } $Esc::ExitRoutine() ExitRoutine() { Process,Close,Lightgun.exe Process,Close,rpcs3.exe Run,taskkill /im "rpcs3.exe" /F Run, C:\Utils\NoMousy\NoMousy.exe ;Restores mouse cursor Sleep, 500 ExitApp }

When you press the button combo 12+1, you need to press (and hold) 12 then 1. You can still do it real fast, it just needs to be "done in order". If it's more ergonomic to do 1 then 12, swap Joy1 and Joy12 (keeping "1" in front of the first "joy" as shown). Not tested, but looks really good 'on paper'. #SingleInstance Force SetWorkingDir C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun Process, Exist, Lightgun.exe If (!ErrorLevel = 0) { Process,Close,Lightgun.exe Sleep, 1000 } Run, C:\Utils\Sinden Lightguns\Mouse Mode - RPCS3\Lightgun.exe Run, C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\rpcs3.exe C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\games\BCES01070\PS3_GAME\USRDIR\timecrisis4.self --config "C:\Utils\LaunchBox\Emulators\RPCS3_Lightgun_2Player\config\custom_configs\config_BCES01070_tc4_2p.yml" Sleep, 1000 Run, C:\Utils\NoMousy\NoMousy.exe /hide ;Hides mouse cursor with NoMousy ;Start Button $MButton:: { send {LButton down} sleep, 60 send {MButton down} sleep, 20 send {MButton up} sleep, 60 send {LButton up} } ;Press Joy12 then Joy1 1Joy1:: { If GetKeyState("Joy12") ExitRoutine() } $Esc::ExitRoutine() ExitRoutine() { Process,Close,Lightgun.exe Process,Close,rpcs3.exe Run,taskkill /im "rpcs3.exe" /F Run, C:\Utils\NoMousy\NoMousy.exe ;Restores mouse cursor Sleep, 500 ExitApp }

Apologies. You did say that earlier. And I presume you're meaning on this particular cab build, launching it directly from GroovyMAME, it runs fine. ?. My guess is, the command-line parameters (LaunchBox - Tools - Manage - Emulators ...) contain -rompath %romlocation% and your CHD's are not stored in subfolders below the regular ROMs as I depicted above. Remove that parameter and try launching it again. If that doesn't work, we'll go to plan "B".

Do you have the CHD file for it? It should get located in a subfolder where your ROMs are located called /gauntdl/gauntdl.chd Foe example: D:\ROMs\MAME\gauntdl.zip (the original ROM you're launching) D:\ROMs\MAME\gauntdl\gauntdl.chd (CHDs are in a different romset than MAME's regular Arcade romset.)

Which game? (what's the ROMs name?)

Can you share what your script(s) looks like? Also, is Button 12+1 what you have mapped in LaunchBox to Exit Game (in Tools - Options - Game Controllers - Mappings)?

Glad that solved it. Just passing along what I've learned on the forums. That one I learned from @C-Beats. Credit to where credit is due.

I was referring to your MAME emulator settings in LaunchBox itself. (Tools - Manage - Emulators - [select MAME] - Edit) No matter how you have things set in mame.ini, if you pass a parameter(s) via the command-line, it will take precedence over what's in any of the MAME configuration files.

If all you have to do is double-click the document in Windows Explorer to open it, then all you have to do is add the document to LaunchBox and don't have an 'emulator' associated with it. Add a .txt file and it'll open in Notepad. Add an .xlsx file and it'll open in Excel. Add a .doc file and it'll open in Word. Add an .html file and it'll open in your default web browser. You can see where I'm going with this.

Edit your MAME emulator in LaunchBox. If the Default Command-line Parameters has -artwork_crop in it, remove that part.

If the bezel default.lay files are consistent in how they're created (they most likely are), as illuded to earlier, you can use the -view parameter so you don't have to hit Tab while in game and then select the correct bezel. odyssey2 -override_artwork odyssey2/%romfilename% -view bezel voice -cart2 There. Now it's automatically done. And really, the beauty is you only need to add the parameters once. If you really want to reduce what's in the command line, create an odyssey2.ini file and put it in MAME's /ini/ subfolder. Inside the file put: artpath artwork/odyssey2 view bezel Then your command line parameters can be: odyssey2 -override_artwork %romfilename% voice -cart2

Do Wii games exhibit this same behavior? I'm assuming you're using stand-alone Dolphin for both of these. Can you share some screenshots of your Dolphin emulator settings? The Details, Associated Platforms and Startup Screen sections

I'm curious as to how you have LaunchBox 13.14 and BigBox 10.1 setup. Are they in the same folder (as per typical)? I guess that's pretty cool considering they're about 4 and half years apart. If you have 2 separate LaunchBox installs (one with v10.1 and the other current [10.14]), that makes more sense. To disable updates, open LaunchBox and go to Tools - Options - Updates and uncheck all the Boxes.

Usually, I ignore any post that has to do with RL. So does MAME. I see where you're going with this. Right concept. But unless in the 'default.lay' file, the view you want to use is titled "ufo", wrong execution. On the ones I've seen, the view is called [generically] "Bezel Artwork". Also, softlist bezels need a little more love and attention. The default location for MAME bezels is in its /artwork/ subfolder. Since softlists may have ROM names the same as Arcade, you'll want to place the soflist bezel(s) in its own subfolder below that. Something like D:/LaunchBox/Emulators/MAME/artwork/odyssey2/ So for 'timelord', you'll have D:/LaunchBox/Emulators/MAME/artwork/odyssey2/timelord/... Where ... is (typically) "default.lay" and "Bezel.png". Not sure why the override is needed, but this is what worked in my test... [from the Window Command Prompt] mame odyssey2 -override_artwork odyssey2/timelord voice -cart2 timelord And of course in LB, remove 'mame' and the last 'timelord' Now, if you're on at least LB v13.15-beta-1, the command line parameter could look like this: odyssey2 -override_artwork odyssey2/%romfilename% voice -cart2 LB will add mame.exe to the beginning, replace %romfilename% with timelord and add timelord to the end.

Who's confused now?? (Hint, it me. ) The "above" command you mentioned at 1st and said didn't work is: odyssey2 -cart1 voice -cart2 (guess I missed this..) The command you said that did work ["in MAME"? From the Windows Command Prompt??] is: mame odyssey2 voice -cart2 timelord Interpolating between the 2, I'd say the command-line parameter for you to use in LaunchBox would be odyssey2 voice -cart2 LaunchBox will add mame to the beginning and timelord (or whatever the ROM filename you're launching is) to the end.

As you know, MAME's softlists need to be in an accessible folder to MAME. In the case of Odyssey 2, the softlist folder is (by default) videopac. There is also the BIOS file (odyssey2.zip) and the device file (i8244.zip) that need to be accessible too. If you have -rompath %romlocation% in your default command-line parameters for the Odyssey 2 platform, be sure those 2 files are in the same folder as your Odyssey 2 ROMs. Alternately, if you added paths to rompath(s) to mame.ini, have those 2 files in one of the folders listed and also the 'videopac' folder. (Or you can add the videopac folder (or whatever you have them in) to 'rompath'.)

-state <slot> "Immediately after starting the specified system, will cause the save state in the specified <slot> to be loaded." i.e. load save state 1 "-state 1"

Can search for Marble Madness II (that's 'eye' 'eye'. Not 'ell' 'ell'. And not "too" or "two") Or as noted above, search for Marble Man: Marble Madness II. Or simply Marble Man. And even Marble Madness. You'll need to scroll down a little to come across it ("Marble Man: Marble Madness II"). The ID shown when you edit a game (as depicted in the screenshot above) is the ID# that's used in the file "Metadata.xml". That number differs from the database ID# found on the [Web] Game Database.

The Windows and Android licenses are 2 separate licenses. Not interchangeable.

@kingkoopa505 @Frankie_Sambuca I've recently heard of a couple others having similar issues (not the exact same, but related to 'window focus' issues and 'MAME'). The fix for both of them in their case was to edit the MAME emulator (in LaunchBox) and on the main Details page, un-check the box Attempt to hide console window on startup/shutdown. This relates to the comment "this seems to happen to games that are not using Fullscreen (Borderless window is not recognized as exclusive full screen.)" Again, I'm not saying this is "the fix" for your situation(s). But something worth trying.

With what you're showing, the 2 Atari (category)'s I think would actually be (Platform)'s. (As in, you can't import games into a 'Category'.) You can put the Playlists under Root, like you depict. (again, this is just me...) When you expand 'Kitchen Sink', you might have upwards of 40 Platforms. I think under "Kitchen Sink" you'd want to have the 'sub' Categories i.e. Arcade, Computers, Consoles, Handhelds, Pinball.. and then 'sub-sub' Categories i.e. [under Consoles] Atari, Nintendo, Sega. And then Platforms under those. Respectively. If it's Playlists you mostly prefer, (which myself, I only look at then maybe a couple times a year. Just to remind myself they're there. lol) you can do like you show. Then if, you have a hankerin' to play something/anything in i.e. Wii, you can expand the Kitchen Sink. Alternatively, have the Playlist view your default View. Then, easily enough, switch to Platform Category View. I believe in BigBox, you can set a button (button-combo) to switch directly form one View to the Other. No matter how you go about it, you'll need to do some manual editing on the Platform/Category/Playlist 'Parents' tab to get the hierarchy the way you want. But that's the beauty of it all. The feature to be able to do is there. And if after a while Plan "A" isn't to your liking, it's easiest enough to make changes and go to Plan "B". And the number of 'plans' are endless. Ya, it may be construed as "A lot of work". But with 'high expectations' come great responsibility. But in the end you'll have something beautiful to look at. And then maybe even play some/several/many/all of those 'EVERY game on each platform'. 😎

Wouldn't "Kitchen Sink" be the same as [the built-in] "All"? Pretty sure it's enabled by default. If not, Tools - Options - Visuals - Filters Side Bar. Check the box Show "All" Item. Heck, you could even rename it to "Kitchen Sink" if you wanted. "EVERY game on each platform" at this point [of the planning] is insignificant. You may want to start by jotting down what all platforms you'll be importing since that's the 1st thing that has to be done before you can organize it all. [Eventually] you'll be using the View Platform Categories. So think about what makes the most sense to YOU as to how you categorize the platforms and organize your setup. To me, what makes sense is something like how you have it currently. And add in some subcategories. Just don't overthink it and break it down TOO far. Enough, is enough. Arcade (Category) Arcade (Platform) Sega Model 2 (Platform) Sega Model 3 (Platform) Computers (Category) Windows (Platform) Steam (Platform) Consoles (Category) Atari (Category) Atari 2600 (Platform) Atari 7800 (Platform) Atari Jaguar (Platform) Nintendo (Category) Nintendo 64 (Platform) Nintendo Entertainment System (Platform) Sega (Category) Sega Dreamcast (Platform) Handhelds (Category) Nintendo HH (Category) Nintendo 3DS(Platform) Nintendo DS(Platform) Sony HH (Category) Sony PSP Pinball (Category) Pinball FX2 (Platform) Pinball FX3 (Platform) Visual Pinball X (Platform)

Ya, if it's not running in your old version of MAME OR a newer one, it's probably as Neil said... corrupt CHD.

Does the error still occur if you go back to your previous version of MAME? Your original non-error screenshot looked like it was creating the nvram. May try deleting the existing nvram file and let it initialize (create a new one) again.

An example of one of those might be -config "D:\emulators\myEmu\Configs\%romfilename%.ini" "FULL\PATH\TO\ROM\FILE" Where you need both boxes un-checked, but need the ROM filename for a config file.