JoeViking245

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.

If you can run the games directly from within RetroArch itself (or via the Command Line, or a batch file), you can launch them from LaunchBox. Make sure you don't have "Extract ROMs" checked in the Associated Platforms section for that platform. Beyond that advice, I have no idea. I have never used RA to launch Arcade games. Though I hear it is possible.

Unless your LaunchBox/BigBox version is also 5 and a half years old (45 releases ago), I suspect it's not the same issue. You may want to open a new thread and include what version you're on and include any screenshots of error messages you're receiving.

There is no reasonable way to determine by just the ROMs what MAME revision they are from. Assuming they even belong to a single set. That said, I always contend, there's pretty much always a way. Reasonable or otherwise. The unreasonable method I've used in the past to narrow it down is to open one of the ROMs' zip file and compare the contents to, starting with the latest set and working backwards, the files in those sets. You can see what files are supposed to be in the zip by going to http://adb.arcadeitalia.net/default.php, search for the ROM, scroll down to and expand Show romset files. By default, it will show the most recent release. Right below "Show romset files" (which now says "Hide romset files") is a dropdown box in which you can select previous releases. Keep selecting previous release(s) until all the files shown match exactly to what you see in your zip file. You can safely compare only the filenames without needing the verify the SHA1 numbers of each one. Note, not all ROMs change between releases. So when you pin down a release # for one of your ROMs, cross check several others in the same manner. Just to be sure.

Try giving this a readthrough and see if it gives any insight to the issue. Big Box Themes and Where They Apply - LaunchBox

Seems reasonable. I suggest submitting an official Feature Request. At the top of this page, click Help & Support, the Request a Feature. Once it gets made public, create a link to it here and if others agree, they can go and can upvote it.

You could try running the MAME Troubleshooting plugin and see if it can shed some light.

Would you please test it again and see if it's now working again? (Appears they removed the "Verify you are human" feature.)

Pointing to the exe should have worked. Unless the games exe is another sub-launcher. Plan "B": Let's get medieval on this game. Revert the games application path to the Steam URL [and parameters] Create a new AHK script (just for this game) Use this new script as the Run Before app for the game You do not need a Run After additional app The script: gameID=2215430 Send, #!b isRunning := "0" While (isRunning = "0") ; Wait until the game is launched RegRead, isRunning, HKCU\Software\Valve\Steam\Apps\%gameID%, Running Sleep, 500 Sleep, 15000 While (isRunning = "1") ; Wait until the game is closed RegRead, isRunning, HKCU\Software\Valve\Steam\Apps\%gameID%, Running Sleep, 500 Send, #!b Change 2215430 on line 1 to the games actual Steam ID number This assumes once the game is launched, you will play for at least 15 seconds (Sleep, 15000)

Until the development team gets this resolved, you do also have the option in LaunchBox itself (which does direct you to a valid location). Menu < Help < Tutorials... Takes you to: LaunchBox Tutorials - YouTube

Steam is essentially a launcher for the game. So in your scenario, you launch the game (steam.exe plus game ID and some other parameters). But 1st LB starts the Run Before additional app to turn on HDR, then the steam.exe stuff. Then Steam launches the game.exe and closes itself (steam.exe). At this point, LB sees the "game" it launched (steam.exe) has exited (but the game.exe is still running for you to play it). Here, I'm surprised your Run After additional app doesn't execute, turning off HDR [right as the actual game is starting]. If it's just the one game (Ghost of T..) you need HRD for, you might be able to find the games exe and set that as the games application path (Edit the game and change it in the Launching section). This way, both Run Before and Run After should work properly. And as a bonus, if enabled, the Shutdown screen should now show when you exit the game (as in, you're not seeing them now for Steam games. Startup screens, yes. But not shutdown.).

Yeah, I explained similar in the beta thread comments that I posted a link to above. But you never indicated what version of LaunchBox you're using. My comment (in the link) only applies if you're on the beta. The local database only [essentially] mirrors the metadata that's in the LaunchBox Games Database. It will only affect your collection if you update the metadata for your existing games or add a new game. e.g. Tools < Download < Update Metadata and Media for All Games... (not to be confused with Tools < Download < Force Update Games Database Metadata...) (the latter only updating your "copy" of the database) There is no risk in running Force Update Games Database Metadata... (Or as I lazily called it earlier, Force Updating the local database).

The override is only for disabling the startup screen. The only "option" to display a different startup up screen per-platform is to have an xml file in your selected startup theme's folder named the exact same as the platform. And note, that is per-platform. Not per-emulator. As in, the emulator is (should be) irrelevant. Example: look in your \LaunchBox\StartupThemes\Default\ folder. If you launch a game from your "Sony Playstation 2" platform, it will use the "Sony Playstation 2.xml" file for the startup theme. If you launch a game from your Windows platform, since there isn't a Windows.xml file, it'll use the Default.xml. Since you're using the StageBox startup theme and it ONLY has its' Default.xml file (no platform-specific xml files), setting StageBox as your Startup Theme in LaunchBox, all platforms will use the same file when loading a game. Unless you disable it specifically for the platform or a game(s). When disabled, it won't show any startup screen. Why your Windows platform is using the Default.xml from the /Default/ theme folder instead of the /StageBox/ folder, I have no idea. Can you share screenshots of the loading screen when launching from a platform it does work in, and then one when launching a game from your Windows platform.

When that window opens, can you press Enter "to start"? Or do you have to mouse-click the Click to Start? In you can [just] press enter: ; Start PrismXR application Run, "C:\Users\tonys\Desktop\VR\PrismXR_Desktop_App\PrismXR\PrismXR.exe" Sleep, 2000 Send, {Enter} ; Start Virtual Desktop Streamer Run, "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" Otherwise, you need to find where (in pixels) on the screen that button is. ; Start PrismXR application Run, "C:\Users\tonys\Desktop\VR\PrismXR_Desktop_App\PrismXR\PrismXR.exe" Sleep, 2000 ; move mouse pointer to center of monitor (1920x1080) DllCall("SetCursorPos", int, 960, int, 540) Send, {LButton} ; Start Virtual Desktop Streamer Run, "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" Adjust "960" (1920/2) and "540" (1080/2) as necessary to "land" on the button to click.

What version of LaunchBox are you currently using? I ran some tests... using the beta release 13.25-beta-1, even after updating the local database, I could not get it to find the game. (See comments here) However, in v13.24 [official release] it did work.

Try changing the title to "Project X: Light Years", then searching. If it still can't find it, try force updating your local database under Tools - Download - Force update...

If it's just for the one game, you can Edit that game. Add a new Additional Application and point the path to your renmameThatFile.bat file. Check the box "Run BEFORE main application". Once done, click OK to save and close.

Glad to hear. The error looks to a TeknoParrot UI error. I don't use that app, so can't be of any help. Hopefully someone else can chime in to help.