JoeViking245

It'd be nice to know what scripts you actually tried so we don't create duplicative efforts. The fork you use might have been helpful also. Since you didn't mention the fork you were using, I tested with the 'regular' flycast.exe. First thing I did was to edit the file emu.cfg and set fullscreen = yes. This alleviates any need for Alt+Enter. 'Regular' Flycast doesn't discern window titles between the 2 windows. They're both simply titled Flycast. So in that regards, you're better off using the fork. For BigBox, I tested using a sleep timer then sending Alt+Tab and that worked perfect. But breaks in LaunchBox because when launched from there, there's not the focus issue and it changes it the screen we don't want. Since your version distinguishes the window titles, you can use WinActivate. At least with the 'regular' version, when exiting this particular game from LB or BB, you need to exit twice. Once for each window. Maybe it's different with your fork. Based on the information you provided, here's what I came up with. Sleep, 5000 WinActivate Flycast - multiboard slave 1 $Esc:: { WinClose, ahk_exe flycast.exe WinClose, ahk_exe flycast.exe } You can adjust the 5 second sleep timer as necessary. For WinActivate, the window title used is case sEnSitiVE. It can also be truncated to just enough where it will distinguish it from another window's Title. i.e. Flycast - m would work.

RetroArch will create a Log file in this situation if adding in the -v parameter. Even though it doesn't appear to launch. Looking closer at the partial debug log you shared, the missing file has to do with the assembly file System.Runtime. So, not related to launching the game. LaunchBox knows the games' file exists because of what's in the games Application Path. In fact, you'd get a popup message box [from LaunchBox] stating it doesn't exist if it didn't. Also, LB doesn't care about what's in the command line parameters, either correct for the emulator or otherwise. As long as the physical game file exists (except in the case of MAME) and the emulator application exists, it'll attempt to pass the parameters as shown to the emulator. The command line LaunchBox passes to the cmd line is [typically*] what's shown in my screenshots above under the Sample Command. RetroArch is unique in that you also need to figure in the core that is passed. i.e. add in -L cores/xxxx.dll *Also note that any parameters (if any) shown in the Associated Platforms section of the emulator for the specific Platform will take precedence over what's shown in the Details section. LaunchBox will always pass the result of %romfile% at the end the command line string, taking into account the checkboxes that are checked. The exception is if you manually insert %romfile% in the middle of your parameters. Then it won't [also] add it to the end.

I can't attest to what is or isn't in the log file. But I can tell you is that what's passed in place of the variable %romfile% directly depends on what's in the emulator settings. You can also either turn on Logs in RetroArch or pass -v to create a Log file. (\Retroarch\logs\retroarch.log) I understand this all in retrospect/hindsight. But may help in the future or someone else reading this sometime down the line.

Try: Edit MAME (in LaunchBox) and un-check "Attempt to hide console window on startup/shutdown".

Glad you like the new additions that you asked for. I will add your suggestion to the 'For Consideration' pile. But there's a really good chance it'll sit there a long time. In the meantime, you could check/un-check the Hide images you already have as a sort-of toggle.

These 2 pretty much counter each other out. Since TP ('for some games') launches another exe (the 'actual game') and then closes itself (the emulator LB initiated), all associated scripts for that emulator are also closed (abandoned / become un-available). I don't have workaround for this as I got rid of TP several years ago. But shared the above so you don't waste time looking for a script that works for those 'some games'.