JoeViking245

You'd be best off posting in BitBucket a Feature Request (if it isn't in there already). At the top of this page, click Help & Support, then click Request a Feature. Then add a link here to get others to vote on that feature request. If there's significant interest, the feature may get added to the next poll for the entire community to vote on. (Don't ask when the next poll will be as nobody really knows. They happen when they happen. ) In the meantime, you might look at using GameSave Managers' built in Scheduled Tasks Wizard and set it up there to have it done automatically for you. If you wanted to get a little more hands on, you could create a batch file that will start LaunchBox and then after it exits, run the command for GSM to do its backups. Another interim option is to add (import) GSM into LaunchBox. Put the exe in within an existing platform (kind of ugly) or create a new platform ("Utilities"?) and put it in there. This would give you direct access to its GUI for doing custom and/or full backups and restores.

I think "extra setup" is the key phrase here. (To iterate, what we're trying to accomplish here is to run (close, actually) an application After running/playing a Steam game that is loaded via its ID#.) Using the Additional App script technique works for you and will work for me and everyone else as well. Unchecking "Use an emulator..." and having the game point to "steam://rungameid/######". The key that makes it work is the WinWait line in the script. Plus, of course, having the Additional App checked to run Before the Main Application. However, that one script will only work for that one game because you have to tell WinWait specifically what to wait for. This is where the "extra setup" comes into play. You have to create a script specific to each game. But that's easy... copy the 1st script and change the game_name.exe on the WinWait line. Well, after you find out what the exe name is. Save the new (2nd) script then add an Additional App to your 2nd Steam game using this [2nd] saved script. Now do this for the rest of your Steams games that need to use JoyToKey. If you have 25 Steam games needing j2k, you now only have to do this 23 more times. If you only have 3 or 4 games that require J2K, this is the way to go. But I assume if [for whatever reason] you need to use JoyToKey for some Steams games, you need to use it for all. This is where (I feel) the "scenic route" is pretty, in nature. (pun intended ). * Create one script. Create one new emulator. Set it as the Default Emulator for your Steam games Platform. If only certain games require J2K, then the process will become a little more scenic. Don't set it as the Default Emulator. While holding Ctrl, click the games that require J2K. Click Edit to start the Bulk Edit Wizard. Set 'emulator' to the one-script emulator you created. Ideally, you'd not have to use J2K at all. Again, I don't use it myself and don't know the circumstances that it's required. *I'm not saying my 'emulator script' is pretty, by any means. If fact it can probably be considered a Hack. Which by definition, is ugly in itself. lol But it is one way to accomplish our desired goal. The per-game script is another. And setting the games to launch directly to the exe is yet another. But not ideal.

How did you setup the emulator in LaunchBox? Show a screenshot of the Details section.

Ya, what @skizzosjt said.

With a Steam game, what's happening is as I described above. When you launch the via "steam://rungameid/248610", it opens steam THEN opens DoorKickers.exe. Also, what's happening with your script is it's ran BEFORE the main application (which is what you want) and the 1st thing it does is wait for DoorKickers to get closed (exited). Since at this point DoorKickers isn't even running, the script "is done waiting" and goes to the next line. Which is to shutdown/exit joytokey. You say "it doesn't seem to have any effect". Is it not even closing joytokey? Do you have a 2nd additional app (also set to run BEFORE) that's starting joy2key? I suppose you'd kind of have to. So, these 2 scripts [at this point] are butting heads. Easy fix, combine the 2 scripts. You'll want to (NEED to) add in a WinWait to wait for DoorKickers.exe to actually be running. THEN you can wait for it to close. Run, "D:\Utilities\JoyToKey\JoyToKey.exe" WinWait, ahk_exe DoorKickers.exe WinWaitClose ;WinClose, ahk_exe JoyToKey.exe **DOES NOT WORK WITH JoyToKey.exe** Process, Close, JoyToKey.exe The issue doing it this way is you need to create a different script for each game. Replacing DoorKickers.exe with the 'new' games [actual] executable. Which, beyond being tedious, isn't that big of a deal. EDIT: I am told (I've never used it myself) JoyToKey.exe is one of the few programs that require "extra force" when closing. WinClose will not work. You need to use: Process, Close, JoyToKey.exe Codes has been edited to reflect this change. Another option is to create a new "emulator" which is actually an AutoHotkey script used to launch your Steam games. It's a onetime setup and will work for all your Steam games that are launched via "steam://rungameid/xxxxxx". The script would look something like this: Run, "D:\Utilities\JoyToKey\JoyToKey.exe" ;**** Verify Path **** Run, "C:\Program Files (x86)\Steam\Steam.exe" -applaunch %1% ;**** Verify Path **** isRunning := "0" While (isRunning = "0") ; Wait until the game is launched RegRead, isRunning, HKCU\Software\Valve\Steam\Apps\%1%, Running Sleep, 500 While (isRunning = "1") ; Wait until the game is closed RegRead, isRunning, HKCU\Software\Valve\Steam\Apps\%1%, Running Sleep, 500 Process, Close, JoyToKey.exe In LaunchBox add a new emulator. Use (Browse.. to) AutoHotkey.exe that comes with LaunchBox as your Application Path, so you don't have to install it. (LaunchBox will convert it to a Relative Path, as shown.) Point to the script as your Default Command Line. ("Put this path in quotes.) Check BOTH boxes. Save. Set the Steam games you want to use JoyToKey with to use this emulator. If you want all your Steam games to use JoyToKey, when creating the "emulator", go to the Associated Platforms section, select "Windows" (or whatever you've named the Platform, default is "Windows") under Associated Platforms and check the box Default Emulator. Skip the above Edit Game all together.

The screen positions you show with the marquee on the right, and lined up on the top, is how you want them set in Windows. So that part's good. For troubleshooting, if you go to Options in BigBox and set marquee to None, does everything look as it should? As in, the TV is showing BigBox and the marquee shows nothing? I ask because in BB you have your Primary Screen set to "1" and in Windows, your TV is "2". I know what Windows "says" isn't always as we see it, hence the test. (Assuming that's all good...) Someone on Discord said they fixed their marquee issue by shutting down Windows, powering off and physically disconnecting the marquee from the computer, restarting the computer, and then reconnecting the marquee after Windows is all booted and turn it on. This might change "2" and "1" to "1" and "2" and you may need to move the marquee so it's positioned like you image above.

Thanks for the suggestions. This would be a duplicate effort of LaucnhBox's Update Metadata and Media tool option. You'll be using that tool anyway to at least get the games Notes, at which time will also add developer, release date and a whole lot more. You're talking about setting the platforms Scrape As value. This would be wonderful! Unfortunately, LaunchBox's default scrape-as values are not available through the API (unless I missed it somewhere). As in, there isn't an available list automatically generated to select from. To make this work, I would need to manually create a list of the currently 190+/- existing possibilities. Me (or someone) creating the list is not the problem. Updating the plugin every time new ones are added, is. I had thought about this early on in the project. But I was also trying to somewhat mirror what the built-in MAME Import Wizard does. As soon as I saw the Wizard didn't deal with clones [beyond the option of adding as Additional Apps to the Parent], I abandoned the thought. The option to add a Custom Field "Clone of" is not an unreasonable one. But this will only work when selecting Import clones separately. Additional Apps (when selecting Import clones as additional apps) don't have the option of Custom Field. Not sure if this helps any, release v4.05 puts any information found in ( parenthesis ) in the games Title into that games "Version" metadata. Generally indicating that game is a clone. However, it doesn't indicate what it's a clone of. If you wanted to make a playlist of parents only or clones only, you could filter it off of "Version" being empty or not. Unless of course the games Title has something in parenthesis that is actually part of the name and has nothing to do with versioning. 😊 Maybe if I had a real-life example(s) of how you'd use "Clone of" to create a Playlist, we can come up with something that would be practical to implement. Version 1.32 (March 4, 2020) - New Feature: If a newly imported game is tagged as not supported by MAME, it will be marked as "Broken". Will also check existing games in the Platform being imported to (in case MAME updated its' status) (Not applicable to clones when imported as additional apps)

Thank you! After 3 years, I have no plans of adding new features. But that's only because I haven't thought about it, and no one's suggested any recently. The original intent of the plugin was to simply provide a means of getting MAME's softlists into LaunchBox using their proper game titles and pointing LB to the ROMs. It has expanded beyond that to working with CHDs, accommodating ROM updating and even auditing your currently imports set. Maybe even some other stuff I've forgotten about. lol As with all my plugins, I am ALWAYS open to suggestions and ideas. I would like to hear what you have.

What do your settings look like under Options, General for Marquee Screen?

Read through here and see if anything helps shed some light. (having had custom command-line parameters per game seemed to be a common issue)

Glad it [almost] worked. I've never had the comical mouse pointer thing happen. Do you by chance have your connected TV's "Scale and layout" in the Windows Display Settings set to something ither than 100%?

@JoeViking245 Can you confirm you're seeing this update corrects the issues you brought up related to your plugin and data saving? Works perfectly! Thank you.

So you know, I'm the only one that I know of here on the forums that uses "Monitor Profile Switcher" for this purpose. It's a small simple program that does only what is needed and works perfectly. A lot of people like using Display Fusion. Probably because it has a lot of other "bells & whistles", it's frequently updated, and (just guessing) "if you have to pay for it, it must be good". The views and opinions expressed here are those solely if the author and in no way reflect those of management. 1st thing you'll need to do is to download Monitor Profile Switcher and then create/save the profiles for you monitor configurations. Their Wiki page also describes how to do this. Download the zip file, right click it and select Properties, check Unblock and click OK. Extract the files to somewhere convenient. i.e. F:\MonitorSwitcher\ Start MonitorSwitcherGUI.exe. This will show an icon on your task bar. Setup your monitors via Windows Display Settings with your PC as the Primary Monitor (I assume it's that way now). Click the icon and select Save Profile, New Profile, and name it something you'll remember. i.e. PC_Primary. Now in Display Setting, set your monitors so that the TV is the Primary Monitor (and any other adjustments you may need to make). Click the icon and select Save Profile, New Profile, and name it something you'll remember. i.e. TV_Primary. The 2 profiles you just created will be saved in C:\Users\YourUserName\AppData\Roaming\MonitorSwitcher\Profiles\ Now that you monitor settings are all screwed up for working from the PC, click the icon and select PC_Primary. You monitor settings will now be back to your "normal" settings. Click the MonitorSwitcherGUI icon and select Exit. Copy (or move) the 2 'profile' files ("PC_Primary.xml" and "TV_Primary.xml") from where they were saved to where you extracted the files above (F:\MonitorSwitcher\) 2nd thing, create a batch file. In your MonitorSwitcher folder, create a new batch file and name it something you'll remember. ("BigBoxOnTV.bat") The batch file will something like this: start /w "" "MonitorSwitcher.exe" -load:TV_Primary.xml start /w "" "F:\LaunchBox\Core\BigBox.exe" start "" "MonitorSwitcher.exe" -load:PC_Primary.xml On lines 1 and 3, change the file name (right after "-load:") to whatever you called them (if different than my example names). On line 2, change the path to where your LaunchBox is installed ("F:\LaunchBox"). But leave it pointing to "BigBox.exe" that is in the "Core" subfolder. If you have it point to BigBox.exe that's in LaunchBox's root folder ("F:\LaunchBox\BigBox.exe"), this batch file won't work as intended. Double click on "BigBoxOnTV.bat" and if all goes well, watch magic happen. Once this is all working as expected, to make the Command Prompt Window not show a 'popup' when you start the batch file, create a shortcut to batch file (in the same folder or somewhere else). Right click the shortcut and select Properties. Next to Run:, change it to Minimized and click OK. Now use the shortcut to start the batch file.

Did some more testing based on what @Headrush69 said. Setting the DIP switch to cocktail, then restarting/resetting the game does make P2 controls work as assigned. But if you're on a single upright monitor, the screen does go upside down for player 2.

At least for keyboard inputs... Even though (for some reason) MAME shows P1 and P2 in the Input Assignments, it's still an alternating controller game. Whereas Gauntlet can actually be played with 2-4 concurrent players. Your DK work around is to double up the P1 input assignments. The problem with that is, while P1 is playing, P2 [controller] can mess with P1. At least that's what my testing came up with... couldn't get P2 to have its own key assignments. I don't know if it's different using actual controllers (like Xbox controllers). Didn't test it.

Never said it was elegant. Just simple. And it is a solution. What you're needing to do is wait for a new instance of rpcs3.exe to open and then move that window. I don't have that game to test with, so now really sure what all it's doing. Window-wise. You may need to tweak it a little depending on what rpcs3 is actually doing with its windows for your game. WinWaitActive, ahk_exe rpcs3.exe WinGet, var, PID, A Send #+{Left} WinMaximize Loop { IfWinActive ahk_exe rpcs3.exe WinGet, var2, PID, A if var = var2 Sleep 500 Else { Sleep, 2000 ;give it a sec or two to actually appear (may not be necessary?) Send #+{Left} WinMaximize, ahk_exe rpcs3.exe Break } } $Esc::Send !{F4} Depending on how many instances it opens to finally get to the actual game, you may need to add one or more loops to get and compare PID's. If the "exclusive features" opens yet another instance of rpcs3 windows (as does the game), that'll really screw things up (using the above example script). But if you go straight to one of the games, you should be OK. I don't know what the exclusive features actually are, but for me, if I'm putting a game on "the Big Screen", I'm just wanting to play the game. If you plan to pop in and out of exclusive features before actually starting a game, that could get messy. Each instance of rpcs3 you start, you'll need to win+shift+left and maximize. Between new windows opening up, you need to capture which window instances you've moved/maximized or nest more loops. I think the most straight forward solution might be to set the TV as the primary monitor before starting LaunchBox/BigBox when you want play games on it. I use a program called Monitor Profile Switcher and created 2 different profiles. One where the arcade cabinet is the Primary monitor and another where the TV is the Primary monitor. I then created a batch file that will: load the profile for the TV as primary, start BigBox, then when BB exits, loads the cab as primary profile. No fuss. No muss. No Win+Shift+Left. Ever.

If I'm reading this correctly, the simplest fix might be to set up a new ("2nd") RPCS3 emulator in LaunchBox, pointing to your same rpcs3.exe but with a different Running Script. In the new script, add a Sleep timer right after the WinMaximize line. Set it to however long you think it takes to select one of the 3 games have it start running. Then add another Send and WinMaximize lines after the sleep. Then set "The Sky Collection to use this new emulator. WinWaitActive, ahk_exe rpcs3.exe Send #+{Left} ;Send Win+Shift+Left WinMaximize, ahk_exe rpcs3.exe Sleep, 10000 ;10 seconds Send #+{Left} ;Send Win+Shift+Left WinMaximize, ahk_exe rpcs3.exe $Esc:: { ;Process, Close, {{{StartupEXE}}} WinClose, {{{StartupEXE}}} ;better method to exit a program ;WinClose, ahk_exe rpcs3.exe ;alternate, direct method to exit a program } Adjust the Sleep timer accordingly.

That was going to be my next suggestion if indeed the above worked.

Not sure what you mean by Kodi integration, but what you did to start (launch) Kodi will work. I might suggest turning off Startup screens.

Try this: Create a text file that contains the following, save it, and rename it to a .ahk file extension. Something like "ClosePhoenixEmu.ahk" Be sure it doesn't get saved with a .txt on the end. Like "ClosePhoenixEmu.ahk.txt" $Esc:: WinClose, ahk_exe PhoenixEmuProject.exe ExitApp Edit one of your games, go to Additional Apps and click Add Application For the Application Path, Browse to ..LaunchBox\ThirdParty\AutoHotkey\ and select AutoHotkey.exe In the Application Command-Line Parameters field, enter the full path to where you saved the file you created, in "quotes". Check the box Automatically Run Before Main Application. Click OK Play the game and see if it works.