JoeViking245

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.

Since pcw8512 has 2 FDD's, could you do something like pcw8512 -flop1 cpmplus -flop2 or pcw8512 -flop1 %romfile% -flop2 cpmplus or pcw8512 -flop2 cpmplus -flop1 I honestly have no idea and have no intention/desire to test it. But I do love what you're doing with Lua scripting. 👍

As an Addition App set to Run Before Main app. 'We' removed the hotkey part and replaced it with a Sleep timer. So when you launch the game, this script will load 1st and then the game. The script will Sleep for 5 seconds, giving the game time to load. Alternatively (and better), replace Sleep with a WinWait statement (just like your above post). This way you don't have to guess at the "5 seconds" (more or less).

Can you provide a little more detail? Does any of it work? Where does it stop working? Possibly at "Return"? If you're running it Before Main Application, the window might not be active yet. You may need to WinWait, ahk_exe TFOC.exe before trying to Send, ^!{Up} or Send, 2.

I'm afraid I can't really help with this as I've never used the Universal Control Remapper program. Is this opening a Command Prompt Window? When this happens, if you use {Alt}+{Tab}, can you switch to the game and then play?

If the 'normal' Save Game State keypress is F2 1Joy9:: If GetkeyState("Joy7") { Send {F2 down} Sleep 50 Send {F2 up} } If the 'normal' Load Game State keypress is F4 1Joy10:: If GetkeyState("Joy7") { Send {F4 down} Sleep 50 Send {F4 up} } On both of these you'll need to press and hold Joy7 FIRST, then the other button (Joy9 or Joy10, respectively). Copy these into the Running [AutoHotkey] Script section of the emulator(s).

It's not innate to LaunchBox (yet?), but there is a plugin that'll do just that.

Because it's a plugin for LaunchBox, it's process is LaunchBox. I strongly suggest fixing this. The easiest way to do that is to use standalone PCSX2 instead of the Retroarch core. Which I'm pretty sure is what's recommended. But I understand if you have an affinity towards RA. Regardless, that really should be resolved. In the meantime, if you have a keyboard and mouse handy, when that banner/image/window is there, and you don't want it there anymore... Hold the {Alt} key and tap {Tab} (still holding the {Alt} key) You'll see a display of all your open windows. Still holding down {Alt}, look for the window that's the image-window needing closed. Using the mouse, point to the upper right corner of that window and click the "X".

What @neil9000 said. But also, I read there was a recent cease-and-desist order against the emulator developer(s) for [I thought] a couple of Cave machines. One of which is "Akai Katana" which will be "removed" in v0.240. So I suppose that could be considered "a risk".

Does it load full screen when you launch it on its own? It should load the same via BigBox as it does when double-clicking the exe file in Windows Explorer. I don't have any [old] PC games on my setup, so can't help with any PC game particulars. But being as we're in the AutoHotkey Scripts section of the forum: You could setup an Additional Application for the game(s) and point it to your myScript.ahk file and check Automatically Run Before Main Application. In your script, remove the ^!{Up}:: hotkey label and add a Sleep, 5000 to the beginning. Adjust the Sleep 5 seconds ("5000") up or down to accommodate game load time, before moving the window. If launching the game full screen (vs windowed) opens where it should (on the TV), but there's flickering, then there's most likely a game/display/monitor/tv setting that needs adjusting. But that stuff is beyond me.

Well, almost. Until you see that ugly Windows Command window. Create a shortcut to this batch file. Right click the shortcut and select Properties. On the Shortcut tab, next to Run:, change it to Minimized. Click OK to save. Run the batch file using the shortcut. Play games.

How about a batch file then? @echo off start /w "" "F:\LaunchBox\core\BigBox.exe" start /w "" "F:\Pixelcade\pixelcade-lcd-shutdown.exe" shutdown /s /f /t 0

Nice find, ElStocko!!! Thanks! To expand on this further: If you wanted to use this in the Running AutoHotKey Script tab for an Emulator, queryEnum2 := ComObjGet("winmgmts:").ExecQuery("" . "Select * from Win32_Process where caption='hoxs64.exe'") ._NewEnum()[process] CommandLine = % process.commandline Then from here, the string %CommandLine% can be used with StringSplit and SplitPath to get what's needed. i.e. MsgBox, %CommandLine% ; "D:\Emulation\C64\Emulators\Hoxs64\hoxs64.exe" -fullscreen -autoload "D:\Emulation\C64\Games\Freeze\space pilot.prg" StringSplit, cl, CommandLine, " MsgBox, %cl2% ; D:\Emulation\C64\Emulators\Hoxs64\hoxs64.exe MsgBox, %cl3% ; -fullscreen -autoload MsgBox, %cl4% ; D:\Emulation\C64\Games\Freeze\space pilot.prg SplitPath, cl4,fullrom,fullDir,,romName MsgBox, %fullRom% ; space pilot.prg MsgBox, %fullDir% ; D:\Emulation\C64\Games\Freeze MsgBox, %romName% ; space pilot

I'm curious, you say it didn't 'help'. But did it even do 'anything'? Good, bad or indifferent? And you tested it on the executable in the /Core/ folder? Actually, that's all more-so out of morbid curiosity because I don't think you're going to be able to accomplish what you want via Windows. As you've seen, it's pretty much all or nothing. Have you messed with the adjustments under Tools, Options, Visuals, Boxes, Spacing? That might just be your ticket.

If you don't see anything on the "General" tab when you right click the file and select Properties, it should be ok. I've no idea when/why/how Windows decides to block it or not. If you have the dll file in your ../LaunchBox/Plugins/ folder, then start LaunchBox, you'll be able to use it when you select more than one game and right-click on one of the selected games and select "Bulk Run Before/After Main Application".

Try unplugging one or some of the other USB devices, then restarting the computer. I know on my cab, if I have the USB dongle for my wireless 360 controller plugged in, and I turn-on/restart the computer, it won't recognize any of the buttons or joysticks connected to the I-Pac (even though their basically just keyboard key presses). But if I unplug the dongle, restart the PC, then plug it [back] in, everything is recognized. Just a thought. Process of elimination.