JoeViking245

Yes. LaunchBox is designed to be portable (just like MAME is 😎). With some minor caveats: A proper installation of .NET Core is required. Some emulators are not portable. (They need to actually be 'installed' in Windows.) Drive letter and folder/file locations. And possibly some other minor stuff. If you use the LaunchBox installer on the other computer, this will ensure the proper installation of .NET Core. Then you should be able to do a copy and paste and have him place his LB/BB license according to the instructions he receives. That one shows as "Preliminary" in MAME. So you might be able to get it to load (per se), but it may not run. I have no idea as I typically don't mess with MAME chd's. If you wish to put one last good-faith-effort into it, make sure you have all 6 files it needs. Also, this game unfortunately is not in hi2txt's arsenal. So you'd have to resort to screen captures to say "See!! I got a better score than you!" (if it even does actually run) That majestic accomplishment was done by @GreatStone as inspired by Fyrecrypts hitotext utility. 👍

Does it launch in the background without the script? Is it stuck in the test screen without the script? Probably so. Sounds like an emulator setup thing.

"Process, Close" should be closing it the same way as if you opened Task Manager and clicked End Task. Which tells me the Escape sequence isn't getting caught. Maybe try shelling out some money to Escape sequence by adding $ to it. Run, "C:\Users\Gerry\Desktop\X360CE\x360ce.exe",,Min $Esc:: { Process, Close, x360ce.exe WinClose, ahk_exe yuzu.exe } If that still doesn't work, as an "experiment" change $Esc:: to !a:: Load a Yuzu game and once it's fully running, press {Alt}+{a}. If that shuts down X360CE and Yuzu, we're getting somewhere.

With your setup pretty well dialed in and all [but a couple of] games are working, that says there's an issue with those couple of games. Assuming your MAME executable (mame.exe) and the rom set you're using are both release 0.224 and the 'few' games are noted as being able to actually run in MAME (and all other games do work), chances are you're missing a BIOS and/or Device file(s) for them. You shouldn't need to totally revamp your emulator settings nor have to do anything special or drastic in LaunchBox/BigBox for a couple of errant games. You really shouldn't be mixing release versions of the executable and rom sets. Many times, things will still work between them. But when they don't, you have no idea if it's because you're mismatching them, or something else. a.k.a. Never mix MAME releases and rom sets! Without trying to figure out why "a couple games" aren't working first, you could just install MAME 0.240 into a separate folder (i.e. D:\Emulators\MAME0.204\) and place your 0.240 rom set in that new setups' /roms/ subfolder. Now start MAME (mame.exe) from within /MAME0.240/, search for the game(s) in question and run it/them. Once you know they all work via the emulator itself, THEN bring them into LB/BB. 1st Determine if the 'couple games' are supposed to be able to run in 0.224. And if so, figure out why they're not. That all said, what games are causing you issues?

Edit the game in question. Go to Additional Apps. Select Add Application. Give it a Name. Browse to the executable (intro.exe). Check Automatically Run Before Main Application and also check Wait for Exit. That 'should' do what you're wanting. Oh ya, Click OK, then OK again to save it.

Good. Don't do that. So the only line in your Running Script is Run, "c:\blah blah\x360CE.exe",,Min? Nothing else? [correct] And x360ce loads and you controller does what it's supposed to do while playing a game? [correct] And since you no longer have the exit routine in the running script, when you exit the game, the emulator closes as it should but x360ce is "freezing"? Can you give a little more detail about "freezing"? Just X360ce? The whole computer? If not the whole computer, what happens if your start another game using the Yuzu emu?

When PPSSPP is fully running, does anything happen if you press the {Windows}+{Shift}+{Left Arrow} keys manually? In nothing happens, then this will not work. If it does move the window, try setting the Sleep timer to longer that 3 seconds ("3000"). i.e. 10 seconds (10000)

Try: go to Tools, Manage, Emulators, and edit you Dolphin emulator. In the Running Script section, add Run, "D:\Utils\DS4Windows\DS4Windows.exe",,Min Esc:: { Process, Close, DS4Windows.exe WinClose, ahk_exe Dolphin.exe } Change the path to where your DS4Windows.exe is located

Ya, oops! Of course that work change anything. 😊 The 'medieval' method should be: Process, Close, X360CE.exe

You might need to get medieval on closing x360ce. In the escape sequence, change only the one line from WinClose, ahk_exe X360CE.exe to Process, Close, ahk_exe X360CE.exe Keep everything else the same.

Is it saying that every time on all games? Are you getting 'local' high scores? As in, you get to put your initials in (say at 4th place) and next time you load the game it still shows you in the #4 slot? Does your custom command line have anything extra in them? In you Emulator settings and/or in Associated Platforms for Arcade . Or in the override when you edit the game, go to the emulation section and check the box for Custom command-line parameters?

I assume this in your Running Script section of the emulator. Adding a couple of commas and "Min" should start x360ce minimized. Normally you could add the WinClose yuzu after the WinWait. That won't work here because as soon as the emulator (yuzu) exits, this script is abandoned. WinClose would never be reached. So we need to add the Escape sequence to 1st close x360ce, and then yuzu. Run, "C:\Users\Gerry\Desktop\X360CE\X360CE.exe",,Min Esc:: { WinClose, ahk_exe X360CE.exe WinClose, ahk_exe Yuzu.exe } If X360CE needs to be fully loaded before yuzu, you may need to try something different. As in, if this doesn't work, you'll need to go to plan "B".

Configuration files and command line parameters · TheArcadeStriker/flycast-wiki Wiki (github.com)

How long do you have your Startup Screen set for? Have you tried increasing it by 1-2 seconds? Are you seeing this with every emulator (i.e. Platforms that use Retroarch, PCSX2, standalone MAME etc.)? I know for me, this sometimes happens with Steam games. Especially when Steam isn't already running in the background (sitting in the icon tray).

Just a shot in the dark... is Show Videos checked?

Edit you Redream emulator. Are both these boxes unchecked? (they should be)

Select all the games in question (click on one, press and hold Ctrl and then click the others), then right-click and instead of clicking Expand..., click Combine...

If say you double-click on UCR.exe so that it loads (hanging out in the background?) and then start LB... then launch a game [with one of the above methods to load a profile], does it still freeze the emu? If not, you can just have a batch file that will start UCR and then start LB. @echo off f: cd "F:\Misc\UCR" start "" "UCR.exe" cd "F:\LaunchBox" start "" LaucnhBox.exe Adjust the drives and path accordingly.

If you have a 'generic' profile you want to load for all Retroarch games, you can edit your Retroarch emulator and in the Running Script section you'd have something like Run, "D:\utils\ucr\UCR.exe" -p "full/path/to/Some profile.ext" Change the path to your UCR.exe and the path to 'Some Profile'. And keep both those paths in quotes as shown. The potential problem here is, if the profile needs to be fully loaded BEFORE Retroarch starts, it may not work because these 2 (RA and the script) launch somewhat simultaneously. But this method may still work. For individual RA games and Steam games, you can get the profile to load 1st before the 'emulator'. Do this by editing the game(s) and adding an Additional Application and telling it to Automatically Run Before Main Application. Give it a name. Browse to where your UCR.exe is located. Put in the command line, changing the path to YOUR actual profile (and leave the quotes). Check Automatically Run Before...

Sure! Do the exact same steps above, except instead of editing your PCSX2 emulator, edit your Redream emulator. Just be sure to follow the "Notes". Namely note #3 because the escape sequence is different between the 2 emulators.

Put the "other" script above your hotkey script (same Running Script section). Just change the emulator.exe name and replace "send {F11}" with "Send, !{Enter}" (no quotes) (then blow that, put in your escape hotkey sequence)

Running Script Run, "D:\Utils\XPadder\xpadder.exe" -loadme "D:\Utils\XPadder\my_profile.ext" Process, Wait, myEmulator.exe while winExist("ahk_exe myEmulator.exe") sleep 700 WinClose, ahk_exe xpadder.exe It may be apparent that I know nothing about Xpadder. So adjust: Line 1 - the Path(s), executable and command-line to load your profile Line 2 - the actual emulator you're setting this up for (it's probably not "myEmulator.exe") Line 3 - same thing as Line 2 Line 5 - the executable for xpadder as necessary. The last line (5) may or may not work. You may need to swap it with an exit emulator hotkey that includes xpadder. $esc:: { WinClose, ahk_exe xpadder.exe WinClose, ahk_exe myEmulator.exe } If instead of closing xpadder you want to load a different (default?) profile, change the 1st WinClose line to something similar to Line 1 above. Not tested, but JoeViking approved.

Try putting this in the Running Script section of your melonDS emulator. SetKeyDelay, -1, 110 Loop { ifwinactive, ahk_exe melonDS.exe { send {F11} break } } (just in case ) Make sure you set "Toggle Fullscreen" to F11 in the General Hotkeys section under Config, Input and hotkeys in the emulator itself.

What does your script look like so far?

If using this one, you should change it to $Esc:: WinClose, ahk_exe {{{StartupEXE}}} The $ in front of the hotkey does 'something' (I never really looked into exactly what that is). Usually, it's not needed but does help in certain situations. But the main point is changing the "Process" method to "WinClose". The "Process" method is like unplugging your PC to shutdown Windows. Whereas WinClose is a little more 'gentile'. "Return" is not necessary in either case. Cemu shouldn't need anything in the Running AutoHotkey Scripts section. Are you running it as Admin? Here's a thread discussing it. I've never [had to] use SuperF4. Which makes me believe it shouldn't be needed for any emulator. But of course, there's always that odd one. When setting up most emulators in LaunchBox, it will automatically put in any required scripts in the Running [AutoHotkey] Script section for exiting the emulator. If required.