JoeViking245

I don't use that emulator, but I do have a little understanding of AHK scripts. The 1st one looks to have some extra , (commas) and other formatting issues that may affect your script. Also I've read that others use Alt+Ctrl to go fullscreen. Suppose that depends on how you have it set in the emulator. I presume the window Title actually has 3 spaces between "Roms" and "Screen"? Or is there only supposed to be one space? Here's your 1st one cleaned up a little (leaving the spaces as is): WinWait, Roms Screen 1 IfWinNotActive, Roms Screen 1 WinActivate Send, !{Enter} WinWait, MK6 Emulator IfWinNotActive, MK6 Emulator WinActivate WinMove,1,600 WinSetTitle, CLICK HERE TO USE BUTTONS

Correct. %romlocation% does add quotes around the full path. Take a look at how @cpujunkie did it (above). And don't forget to check the 2 boxes as noted. You should be able to put in relative paths to keep it portable. Make them relative to where ares.exe is located as the command will be executed from 'that' directory.

Right before ExitApp, add 2 lines WinActivate, ahk_exe LaunchBox.exe WinActivate, ahk_exe BigBox.exe ExitApp If you never use LaunchBox, you can omit the 1st line. But it doesn't hurt anything having them both in.

Woot! Woot! Glad to hear!! Also, I have never ventured into V2.0+. So you would have been on your own. lol

Maybe try what Kiinkyfox suggested in leu of the batch file shortcut(s). Note to add at the end ",C:\WINDOWS\system32, hide" to give the working directory and hide the window.

That's an AHK error message. Quote the %1% Run, "C:\Visual Pinball\VPinballX.exe" -minimized -exit -play "%1%"

Not sure why it wouldn't work as a .ahk but does as a .exe. Here's some code streamlining... Reduced the sleep timer from 10 seconds to 2 seconds (guessing that it doesn't actually take that long) Removed #IfWinActive and SendMode. (At least with my keyboard and Xbox controller, it's not needed.) Combined the 2 hot keys since they are to do the same thing. Still gives the option to press one or the other. Changed Process, Close to send Alt+F4. No particular reason. They do the same thing (in this case) #SingleInstance, Force Run, "C:\Users\Arcade\LaunchBox\Tools\Pinscape disabler\Pinscape_enable.bat - Shortcut.lnk" Sleep, 2000 Run, "C:\Program Files (x86)\Steam\Steam.exe" -applaunch 442120 -class -table_"%1%" $Esc:: $vk07:: Send, !{F4} Run, "C:\Users\Arcade\LaunchBox\Tools\Pinscape disabler\Pinscape_disable.bat - Shortcut.lnk" ExitApp

Can you share a screenshot of the main details section for your AHK-VPX emulator (whatever you called it)? Side note: Looking through some notes, instead of the 2 lines (While WinExist... and Sleep...), you could use 1 line: Process, WaitClose, VPinballX.exe (if you want, both ways do the same thing)

You forgot to tell it what to -play. "%1%"

That game had only become available in MAME a couple days ago. Probably just need to let the dust settle a little. But as always, where there's a will, there's a way. 😎

No. The rule of precedence is Edit Game - Custom Command-line parameters will override.. Associated Platforms - Custom Command-line parameters will override.. Edit Emulator - Default Command-line Parameters. They will not be compounded.

In addition to those, there's %romlocation% (added sometime early in 2022) which will give the "full\Path\To\Rom\". Path only.

While in the Arcade platform, go to Tools - Import - Manually Add Game This will bring up a 'blank' game. Add the Title, and in the Launching section, browse to your jumbogod,zip file. You can try to Search for Metadata. But you won't find anything. Click OK to save.

I believe it tells you somewhere onscreen how to do that. But I think you select the control/key and then press delete.

For VPX, just do the same as you did for FP (create a new "emulator") but change the references from FP to VPX. Run, "C:\Games\Visual Pinball\VPinballX.exe" -minimized -exit -play "%1%" Sleep, 10000 While WinExist("ahk_exe VPinballX.exe") sleep 700 Oh, and shouldn't need "Run, "dmdext.exe"....". FX3 might be a little trickier as I believe it uses a 'launcher' of sorts to open the table. So you'd need to figure out what to put in the line for "While WinExists...". This may be different (the exe or window Title to look for) for each Table.

LaunchBox and BigBox have separate controller mappings. Mapping one doesn't affect the other. So you need to map them individually. BigBox itself has separate Controller mappings and Keyboard mappings. In BigBox, it's in Systems Menu - Options. Near the bottom you'll see Keyboard Mappings and Controller Mappings. In LaunchBox, it's under Tools - Options - Game Controllers - Mappings.

It would be in ..\LaunchBox\Data\BigBoxSettings.xml <UseAllControllers>false</UseAllControllers>

Earlier you said you couldn't Run a file that is a shortcut. At the time I ignored that. I think now, times are a changin'. If you have a batch file located: D:\MyFiles\myBatchFile.bat ..and you create a shortcut in the same folder to that file, the file will show as D:\MyFiles\myBatchFile.bat - Shortcut To execute the shortcut in an ahk script, use: Run, "D:\MyFiles\myBatchFile.bat - Shortcut.lnk" ..adding the file extension .lnk (that's an L (ell). Not an i (eye). Short for LINK). Since your shortcut is already set to run as admin, this should work. And you shouldn't need to use "Run *RunAs". At the end of the batch file, add "pause" (without quotes). This will hold the command prompt window open until you press the 'any' key. If and when everything gets to working properly (fingers crossed), you'll want to remove that. Then, as a bonus, edit the shortcut file(s) (properties) and in the Shortcut tab, change Run to Minimized. That will then hide the command prompt window. Giving it that finishing touch. Your emulator settings look fine. The scripts have the file extension .ahk . If you have AutoHotkey installed, that file extension will be registered to it. When double clicking the file, it will open with your installed version of AutoHotkey. Not everyone has it actually "installed". So double clicking a file with a .ahk extension would do nothing (except ask you what application you want to open the file with). In my examples of creating an AHK script 'as an emulator', it was just easier to have them launch the script using AutoHotkey that comes with LaunchBox than to assume they have it installed. To use your installed version of AutoHotkey, replace the Application Path with the path to your installed copy of AutoHotkey.exe. Alternately, since the file extension .ahk is registered to AutoHotkey (that you installed on your system), you could replace the Application Path with the path to your script (.ahk file) and then remove the Default Command-line Parameters.

[Future] support for plugins is best found on that particular plugins' Support Page. The link to the support page can be found at the top of the page in which the plugin was downloaded. Here's a direct link to the Support Page for the Multi Monitor plugin you're referring to.