JoeViking245

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

At this point, the game/emulator/etc. to be used are already committed. So can't really change any of that. As for canceling it, I suppose you could OnAfterGameLaunched(), capture the emulators HWND (or similar) and force close the window. Then use the PlayGame() method to launch the game using whatever args you like. Is this something that changes between different launches of the particular game? Or is this something that could be added to the specific games' Emulation section and using override command line parameters.

Would deleting those platforms and reimporting the games be out of the question? Doing so won't remove the images (unless asked... select, don't delete the images) which are generally associated to the games via their platform/game_title. Thus will get reassociated and not need to be redownloaded after reimporting. The reimport process should be fairly painless and relatively quick. This will also get the games associated to the proper LaunchBox DB ID.

If it's a video, you'll see the "Play" triangle. (Grasping at straws...) if it's not displaying them, check Tools < Options < Visuals < Game Details - Show Videos

Since you've been around a while, I presume your license is a premium lifetime license. Do the videos show, and just not play? As in if you click it, it'll start playing. If so, maybe just a matter of: View < Media < Auto-Play Videos (or Ctrl+Alt+V) For LaunchBox at least.

That's definitely a different error. I suggest submitting a bug report (top of this page, click Help & Support, select Report a Bug). This way it will "officially" get reported and a better chance of getting looked at. Be sure to include your details and the actual error (you show above). Actually, as I think about it, you should be able to instead, just click the Report Error button on the error itself. (Never done that myself, but I presume it goes to [or at least ends up in] the same "official" location.)

Not sure what's going on then. You might start (continue?) researching that app (Google, their forums/wiki, etc.) to see if there's a way to auto-start it without having to "click the button". Something like a command line parameter. Or if there's an option to load it when Windows starts, test that to see if it loads without having to click anything. If so, look at the shortcut they created in your Startup folder to see how they did it, and duplicate that. (then remove the shortcut) And if nothing else, you've learned a couple new AHK script testing/troubleshooting techniques.

1st off, COOL CAB!!! May sound weird, but what happens if you slide the marquee (2) to the left side of the main monitor (1) [keeping the tops still aligned]? (Display Settings)

What's the error? Is it a TP error? A script error? Some other error? If it's a TP error, I can't help you. Not that I won't. It's that I can't. I don't use TeknoParrot. Well, you're halfway there. You're welcome.

If after the full 5 seconds has lapsed, and no circles appear, does anything happen if you [manually] hit Ctrl on your keyboard? If so, is it (the circles) in the correct location (above the button)?

You created a text file which had the one line: Run, E:\Launchbox\nomousy.exe /hide in it. You saved that file and changed the file extension from .txt to .ahk. e.g. You saved and renamed it to: E:\My AutoHotkey Scripts\HideMouse.ahk Your Command-line Parameters for this Additional App will then be "E:\My AutoHotkey Scripts\HideMouse.ahk" (the full path to the file you previously created, all within quotes)

If it works outside, I'd check that the Additional App is setup correctly. Give it a name Point to LaunchBoxs' AutoHotkey.exe WITH QUOTES, add the "full/path/to/your/script.ahk" Check Run Before Click OK to save and close

This will hide it, then (I presume) show it, right away. I "presume" because I didn't see in the documentation where is says to add "/show" as a parameter to show it again. [Just] this should work. If your Additional App has both Run commands, it won't work. After deleting the Additional App, did you click the OK button (vs. clicking the X in the upper right corner)? Are you testing nomousy and starting the game? Maybe try that. Run, E:\Launchbox\nomousy.exe /hide RunWait, E:\LaunchBox\Emulators\Demul\demul.exe -run=naomi -rom=hotd2 MsgBox The game has exited Run, E:\Launchbox\nomousy.exe (change the path to Demul as necessary)

Not sure if any of your "few different ahks" used a DllCall method. Or were just different trial-and-errors for using nomousy. You didn't show your work. That said, an AHK script using a DllCall method is doing the exact same thing as nomousy is doing. And according to sindenwiki, should just work. What platform/emulator? It may be a setting in the game itself. If you added both the HideMouse (Run Before...) and ShowMouse (Run After...) Additional App scripts, try removing the latter and see if it then hides it during the game. (You will need to manually Un-Hide after testing.)

If "similar" looks like this: ...it can be resolved by: Go to Tools > Download > Force Update Games Database Metadata... (more details about his error can be seen here: Troubleshooting: "Year, Month, and Day parameters describe an un-representable DateTime" Error - LaunchBox) If it's not that, it could really help the developers to show the actual error message.

This is outside the scope of this plugin. Also, the plugin's not setup to do "bulk" in the manner in which you need. But you may already have means available to something similar to what you want. I'm not sure how you're distinguishing if your games are non-working [to be able to grab them in bulk in the first place], but rather than say... replacing "those games'" box-front images with a red X image, you could enable the "Broken" badge. (View < Badges < Game Attributes < Enable Broken) This of course assumes you're checking the "Broken" box on games that are non-working. If you're not fond of that particular image, you can replace it with any red image of your choosing. If you're using some other means of determining non-working games, e.g. a Custom Field, you could create a Custom Badge that looks for the Value of the Custom Field. Another alternate solution (closer to what you may have envisioned) could be... replace the platforms default box-front image with your red image. In Windows Explorer, navigate to ..\LaunchBox\Images\[your platform]\Box - Front\ and delete all images and folders. Then in LaunchBox, select your platform and click View < Hide Games < Marked Broken (or press Ctrl+Alt+R). Again, this assumes "Broken" is how you're determining non-working games. With the non-working games "out-of-the-way", select all [remaining] games and (re)download just the box-front images.

Note: removing -keyboardprovider dinput from the Command-line Parameters will make the LaunchBox pause menu NOT WORK. But that's ok. Pausing an Arcade game is sacrilege anyway.

With MAME 0.139, the command-line parameter -keyboardprovider dinput is not an available parameter. It was added in version 0.168. So you will need to remove that from the Default Command-line Parameters in BOTH the Details section, and in the Associated Platforms sections (if it's also in the latter). If after removing that parameter they still don't launch, as @mikekim suggested, place (move) your ROMs into your ../Arcade Flag ship Gametron Mala/Mame/mame0139s/roms/ folder. Then in LaunchBox, you can: Select all games in that platform (click one, then press Ctrl+A to select all), then go to Tools < File Management < Change ROMs Folder Path for Selected Games... and select the "roms" folder [above]. This will point the ROM paths to their new location [without having to reimport them].

It sounds like you're compiling your ahk script to an exe file. Which should be fine. Are you using AHK v1.1? Or v2.0? For using scripts with LaunchBox, I suggest V1.1. (Ignore that it says depreciated.) I don't have any more thoughts on this as in my tests here, it works. But I do have a suggestion for testing and working with scripts: Download CodeQuickTester, place the file in a location where you won't forget where it is and use it for testing. If you have AutoHotkey (v1.1) installed on your system (recommended), you can download the CodeQuickTester_v2.8.ahk file. Otherwise, download CodeQuickTester_v2.8.exe. Neither will work with AHK v2.0. Run the app, click Edit and select Script Options. Click Pick AHK Path and go to and select your Autohotkey.exe file. Close the window. If you don't have AHK installed, you can point it to your /LaunchBox/ThirdParty/AutoHotkey/AutoHotkey.exe file. Close (red x) that window. In the script body, type in DllCall("SetCursorPos", int, 960, int, 540) Send, {Ctrl} Then click Run. This should move the mouse and show the circles. Once satisfied that it is working, add above those 2 lines your Run....PrismXR.exe and Sleep lines and click Run. See if the app starts and the mouse moves and shows circles (be sure to wait the full 2 seconds to see the circles). Continue adding the rest of your script and testing until you satisfied with the results. Don't forget to eventually change {Ctrl} to {LButton}.

This feature came out in v13.13 (May 2024). When you setup PCSX2, the BIOS files/location should have been set then (on 1st run of the emulator). You could try running the emulator [standalone] and re-set it up. Assuming you have a correct BIOS file, the default location for them should be /PCSX2/bios/. This also assumes you have a "portable.ini" file in your PCSX2 folder. Depending on how you created the backup of your PS2 BIOS, the file name may vary from what's shown. Fortunately the plugin checks the file(s) hash more-so, rather than the filename.

Assuming you copied and pasted the script (vs retyping), only changed the necessary items and no errors were given... it may be that the 2 second delay is too short. (i.e. not enough time for the window to fully load) It may be that the coordinates are incorrect. e.g. the coordinates are in the window vs for the whole monitor. It may be that there's a command line parameter you can add to bypass that window and not have to click it at all. You can verify the coordinates by checking the box in your Windows' Mouse Properties - Pointer Options, "Show location of mouse pointer when I press the CTRL key". Then change {LButtun} to {Ctrl}. When you run the script this way, if all goes well, you'll see the "target rings" appear over the "Click to Start" button when you get to that part of the script. Even if the window doesn't have focus, if it's showing and the mouse clicks in the correct location, it'll click that button.

You need to contact your vendor regarding how they setup your pre-configured drive. Support for these will not be given here.