Monyet

Thanks, I also tried your settings, similar issues. This definitely seems to be a mame issue rather than just a game and watch issue. Ok we are now getting somewhere, I completely removed Mame from the list and added it back, then had to set my rom path in the mame.ini, a few command line options like turning off nag screens and it finally loads mame games. So now I am back to the Game and Watch issue, I think Im on the right track. I realised that my game and watch set was pointing at the "games\nintendo game and watch" and that set wasn't named like the mame set, for example Green House in MAME is gnw_ghouse.zip so I have tested on Green House, editing the rom file name under Launching to point at the mame one. I removed and re-added the game and watch set and pointed it to the mame set, but when it tries to load a game now and uses mame I see this console error ever so briefly, So is Launchbox throwing the wrong name to mame now?

Ok thanks for some insight. So I just tried a random mame game and that launches into the MAME GUI itself and doesn't choose a game. I thought I would update and have gone up to 0.289 and the same thing happens, So I'm guessing that MAME is the common denominator here and it's some kind of path issue. All my settings were the same as yours So, what I did next was to run a game from within mame, and that works fine. When I load in any game from Launchbox, it just takes me to the GUI. It did... after removing some commands in my command line it now shows the splash screen, says almost ready, then almost done, and then game over. It doesn't even save anything to the mame log so I have to assume Mame isn't even loading now. I've never had this issue before with mame, it has always just worked. I don't know what Ive done wrong. Current config attached.

Doing my bloody head in. I am not using Retroarch, because I have the mame set with the G&W roms. I can get any G&W game to run inside Mame 0.288 by itself. When I try to load it from Launchbox it shows the now loading screen and has a message "Waiting for the game to be ready" It stays up for 5 seconds and then closes out. The logs, I guess I can't read them because they are less than helpful, I was expecting to see a message so I could diagnose where the issue is but I can't see anything that shows up as an error. I probably have a setting wrong somewhere. Extra in case it helps: Win 10, 3900X CPU, 32GB, 4070TI Super, Latest launchbox, Mame 0.288 - same as romset. Anyone got any ideas? Debug 2026-11-08 04-41-26 PM.log

Is there any chance you can get it so that it will scan archives for the iso? I have all my roms zipped so I can continue seeding and I can't set up ps3 as a usual system because of that limitation.

You can actually use the old Hyperspin flash themes that people have saved as movies and then when you configure LB/BB, you tell it to just play the video snap full screen.

Typing this on my mobile since my system is updating everything and RAM usage is now a glorious 26 GB out of 32GB installed. Is this normal or is it my circumstance where I started a brand new install and added 12 complete systems, it started to download all the artwork and set up 18,000,000 images for downloading. Weirdly it was erroring out on many of them, whatever it was downloading had the same filename so I left it running and came back to see over 400,000 errors.

All good, same here. They fixed the regression which caused the problem I had. Hopefully you're able to get it working.

Hmm... SHA-1 hash is the same in the hires file? Did you extract the pack to a directory with the same name? Because in RA it won't work with a zipped pack. Also, even after I got it right and opened it, it still didn't work, and then the next time I opened it it worked.

After posting that above and investigating it more with a person that works on the core it looks like there was a regression introduced recently so I guess my problem was different to yours since yours happened last year. Did you figure it out in the end?

Hey mate, I was running into this problem today. It worked fine in the standalone Mesen but wouldn't load in the RetroArch Mesen Core. I think I've tracked it down to the fact that the ROM is zipped. While Mesen supports loading from zips, it doesn't look like it can also apply an HDpack while opening from a zipped file in RetroArch. The Mesen core was made by the same guy that wrote Mesen I think, M. Bibaud (aka Sour) is the name I've seen. The project looks to be archived on github and I'm not signed up so I don't even know if I could email the guy. Maybe someone here knows? I also could be wrong, can anyone else load an HDpack while opening the rom from a zip?

Yes, that line doesn't actually delete the files with and without the quotemarks. I tried putting it as the exit script but that didn't make a difference either.

Hey! I just figured it out, because it was talking about Absolute paths I used the command A_LoopFileLongPath and it parsed the right thing to the emulator. It also needed "" around the Xbe path so here's the final code: fullPath = %1% SplitPath, fullPath,,,,romName RunWait, "I:\LaunchBox\ThirdParty\7-Zip\7z.exe" x -y -o"I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" "%1%",,hide xbeFile = I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%\default.xbe Loop, Files, %xbeFile%, FR xbeFilePath .= A_LoopFileLongPath RunWait, "I:\LaunchBox\Emulators\CXBX-R\CXBX.exe" "%xbeFilePath%", 1 FileRemoveDir, "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" Thank you so much for your help, I'm a complete muppet at this stuff but you gave me the guidance to figure it out.

The MsgBox comes up with nothing, then CXBX starts but no loading of xbe's or errors. I think it must come down to the way CXBX handles the command line, I read somewhere that it needs absolute paths to load. What I noticed was that if I put anything infront of %xbeFilePath%, for example I put a - , that CXBX would throw up an error saying it couldn't load - so I think it must be ignoring %xbeFilePath%. I'll have to look in to how it handles paths.

Unfortunately, this seems to just open the emulator but not open the xbe, it doesn't throw up any errors either. There is only the one defualt.xbe in this example, some things I then tried: I tried changing FR to DFR, and that made no difference. I thought that maybe xbeFilePath .= should have been := and changed that but it made no difference either. I tried changing A_LoopFilePath to A_LoopFileDir with the same result. I added this line above the xbeFile line: SetWorkingDir, I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%\ with no change either. I then changed all those things back to what you had. I was looking at this line: "xbeFile = I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%\default.xbe" and wondering if it needs to have the other directory in there after %romname% which is the crux of the issue anyway. Someone on the AHK discord said I could use a WatchDirectory script to get the name of the folder, but I like the idea of just searching for the default.xbe because 99.9% of disc images are like that I think.

Thanks, I have slimmed down the script with no need to rename the xbe and I know what the problem is, just not how to fix it. fullPath = %1% SplitPath, fullPath,,,,romName RunWait, "I:\LaunchBox\ThirdParty\7-Zip\7z.exe" x -y -o"I:\LaunchBox\ThirdParty\7-Zip\Temp\" "%1%",,hide RunWait, "I:\LaunchBox\Emulators\CXBX-R\CXBX.exe" "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%\default.xbe", 1 ;FileRemoveDir, "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" So basically the issue is that the rom file, for examples sake, is called "Futurama [!].7z" but the folder inside the archive doesn't contain the [!] on the end, it's just Futurama. So if in between those two RunWait commands if I can tell the script to delete the [!] from directory name, or just use the extracted directory name instead of %romName%, I think it should work. Any idea how I can accomplish that?