JoeViking245

Refreshing to hear. Thank you! It should work fine. Admittedly though, I've never the avx2 variant. My shoot-from-the-hip guess is that it's running Exclusive fullscreen. vs. just fullscreen or borderless fullscreen. You're quite welcome. Glad it's helping you work towards your goal.

No. Games saves are integral to RetroArch. However, some cores may not be able to support them. (I don't know this for fact but seems to make sense.) If you're referring to being able to manage them in LaunchBox (as shown in the 1st link I sent you), not sure. Is the menu item saying it's a premium feature?

Note that both LaunchBox and Big Box after closing/exiting, by design, does do work in the background to save data (aka, save any changes and create backups of changes to your Data folder). Depending on the size of your build, what changes were made [and to a degree, your system specs] this may take upwards of a couple minutes. But typically, shouldn't take that long.

My disclaimer: I've never used this feature. That said, It looks like maybe, possibly, a shoot-from-the-hip guess... LaunchBox is searching for Saves via Emulator - Platform, and assumes you'd only have one [valid] core associated with it, so grabs the 1st one (regardless of Default) it comes across. Which coincidentally? alphanumerically? is the fceumm core. Not to simply "pass the buck".... May want to file a Bug Report.

Tools < Options < General < Save Management

Hopefully you can find some useful information here: Managing Save Games and States - LaunchBox

You might try Tools < File Management < Restore Data Backup... I personally haven't used this tool, but I presume the prompts should be fairly descriptive.

Based on information you've provided... the exact same zipped ROM file will launch directly from within RA, but not when launched via LB, yet others in the exact same platform do launch [via LB], and all ROM files being used are zipped (e.g. "gameROM.zip"), ...leads me to there's something amiss with the specific game settings in LB for the non-working games. My last-ditch effort (akin having you share screenshots of everything) Edit (in LaunchBox) a game that's not working [in LB, but does direct from RA] Check the ROMs path (Launching section) Click Browse and verify it's pointing to the correct/same zip file and location used in both tests Check the assigned emulator (Emulation section) Verify it's assigned to your RetroArch emulator If you have more than one instance of RA make sure it's assigned to the same one being used by games that do launch via LB Make sure it's not using a Custom Command-line Parameter for the game (un-check the box) If you are using Custom Command-line Parameters for individual games, that's a different story/issue which you need to elaborate on Beyond that, I'm out of ideas.

No. This is the only instance in my 8-9 years here where I've heard of this being an issue. I mean, you could put in a feature request. I suppose.

In the emulation section of the game you launched, is it set to use the batch-file/emulator? If you've created more than one test-emulator, is it pointing to the correct one? Is the script I gave you the only thing in the Running Script section? If not, make sure it's at the top. Try changing where caption='fusion.exe'" to where name='fusion.exe'" (in that script). Try using a different emulator that is actually currently active. Like RetroArch with the Genesis Plus GX core. Or Ares. Try removing the 1st line in the batch file (set __COMPAT_LAYER=highdpiaware). Verify it works (even if it's only shows on 1/4 of the screen) with it removed when used as the emulator. Is there something in your graphic card settings you can change specific for "Fusion.exe" where you could run the emulator directly without the need of a batch file. Does the "1/4 of the screen" change to show everything when using the emulator directly from LB if you change your screen Scale (in Windows Display Settings) to 100%?

And when you edit the game in LaunchBox, the game's ROM path is pointing to the correct .cue file? (Not "and its tracks") Good! Now in LB, use the 1st of the 4 examples as your batch-file/emulator. In the Running Script section of this emulator, put Sleep, 3000 queryEnum := ComObjGet("winmgmts:").ExecQuery("" . "Select * from Win32_Process where caption='fusion.exe'")._NewEnum() While queryEnum[proc] t .= proc.CommandLine "`n`n" FileAppend, % t, .\Plugins\CommandLine_Fusion.txt Launch a game using the batch-file/emulator. Wait at least 3 seconds before closing the emulator. Close the emulator. Navigate to your /LaunchBox/Plugins/ folder and open CommandLine_Fusion.txt What's it say?

Did you verify your account (in Steam) is set to public?

Again, I don't use/have that emulator setup. So flying blind here. Remember, you're passing along whatever details to your batch file. So, whatever your batch file requires to be sent to it. And since you're running 'my' batch file, no boxes should be checked. Including boxes in the Associated Platforms section (except for Set As Default Emulator for the platform). I presume when you imported the games, you imported the .cue files. Correct? Try creating a batch file and run it by itself, outside of LaunchBox to start a game. You indicated you did that and it worked, but you didn't show what that one looked like. Should be something like set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd "D:\myGames\Sega cd\my favorite game.cue" pause Change the above path to reflect the game that you were testing in LaunchBox, its ROM path. Now see if that works. I added a pause at the end (for testing purposes) so if any errors come about, you should be able to see them.

This won't load a game. Just the emulator (because it wasn't told what game to load). That's where %1 comes into play. to use an emulator, try: set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd %1 You might need to put quotes around it set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd "%1" Or you might need to declare it 1st set game=%1 set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd %game% And possibly add quotes set game=%1 set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd "%game%"

Inside of the .zip's that are not working, is there just the single game2.a26 file? (vs. more than one file) If you edit your RetroArch emulator (in LaunchBox), under Associated Platforms - Atari 2600 [platform], is the box Extract ROMs checked? Since the Stella core can handle .zip files directly, try unchecking that. (If it's already unchecked, try checking it??)

What's the difference between the ROM file types that work vs. not work? e.g. game1.zip vs. game2.a26

It's not very often the integrated plugins actually need updating. In the message/notification is a link to the plugins section [of the UI]. In that section, select the plugin in question and click the Update button. It will take 1, maybe up to 3 full seconds. When done, it well tell you LaunchBox needs to restart. Once restarted, you will not see the damn stupid notification. Many people do, whether they realize it not. Not saying you do use it, unknowingly. This method of updating them allows rare, yet minor fixes to be pushed without the need for a complete new release of LaunchBox being pushed. e.g. A fix can be realized within a matter of hours, rather than waiting until the next release. Thank you for your patience and understanding.

I was referring to when you set the batch file as an emulator, LB will pass the games ROM path [as a variable] to it. And in the batch file it (the ROM path) becomes the variable %1.

Can you show what your batch file looks like? Also, how are you running it from LaunchBox? As the game (e.g. it's the games application path)? Or did you set it up as an emulator? Can you share screenshot of this?

Ahem...the OP was for minimum requirements. lol To be fair though, they did also ask for 'your setup'.

OK. So it was a bad guess. 😊 If you have CTC, you could download the CTC files, load it up and snoop around there. They looked to be available on the actual theme's download page. Which TBH, is probably where this thread should have been. Granted, the author hasn't been around since March, there may be others that follow that main thread and possibly have some insight.

Pretty positive there isn't via LB API. I've used Process.GetProcesses(). Then whittle down to the emulator. Works well in my application. Looks like you've already found "the solution" to this. Well done. If your games have consistent file naming conventions, you could super crazy/creative... Using your OnBeforeGameLaunching() override method and the available IGame game, you can: if (game.GetAllAdditionalApplications().Length > 0) foreach (var g in game.GetAllAdditionalApplications()), if g.ApplicationPath.EndsWith("Disk 2.img") (You've found Disk 2) Now use game.ApplicationPath and g.ApplicationPath in your override. (Then restore things OnGameExited()) Alternately, Create "an emulator". Use C# or even AutoHotkey. Pass %romfile% to the "emulator". Do a file = Path.GetFileName. Search the ROM files' path for a file that starts with file.Split(" Disk")[0] and ends with "Disk 2.img". If it exists..... and build your command line from there. Then it's just a matter of Process.Start() blah blah blah WaitForExit() ... return "done". this.Close(). (or in AHK... RunWait, emu.exe...parameters...) That should keep the startup/shutdown screens working, as well as work for any multi disk games. Personally, I'd just stick with the individual games' command-line override. Always glad to help.

Looking through the Views files and taking a super wild guess, try placing an image for a game in the /Images/[your_platform]/Screenshot - Game Title/ folder. And see if it shows up when selecting that game.

Did you set the batch file as an emulator with no command line parameters and in the batch, capturing %1 to pass as the game/ROM? If it works outside of LB, it'll work in LB. I don't have the abandoned Kega Fusion emulator setup on my machine, but if the different platforms it emulates requires different parameters, you'll want to capture %1, %2 (and/or more?) as well.

[For all readers...] This has been reported and is a known issue that is under investigation. Read more about it here: Feedback - LaunchBox: Date formatting crash with Arabic regional settings on Windows 11