JoeViking245

Process, Close is the most forceful way (in AHK) to 'kill' a program. The fact that you got it working outside of LaunchBox is a bit disconcerting. If Lichtknarre actually has some sub-process (multiple instances), you could try something like (replacing the 1st line): Loop 10 { Process, Close, Lichtknarre.exe Process, Exist, Lichtknarre.exe } Until not ErrorLevel This will look for up to 10 instances (which is a bit overkill) of the app, closing each one, until none exist, or 10 loops have been reached. If that doesn't work... not sure what to tell you. Especially since you got it to work outside of LaunchBox.

I have no idea what the command line is to mount/unmount an ISO to a drive letter, so I'm going to pretend it's -mount, -unmount and -driveletter. Process,Exist, dtagent.exe If ( ErrorLevel = 0 ) { Run, "C:\Program Files\DAEMON Tools Lite\dtagent.exe" -mount "D:\Roms\Microsoft DOS\Roms\Where in the World is Carmen Sandiego 1996\csworld96.iso" -driveletter G } $Esc:: { Run, "C:\Program Files\DAEMON Tools Lite\dtagent.exe" -unmount "D:\Roms\Microsoft DOS\Roms\Where in the World is Carmen Sandiego 1996\csworld96.iso" Return } The 1st line looks for the process. If the ErrorLevel (2nd line) = 0, then it's not running. Once you figure out the correct command lines, change the 2 "Run" commands to those (i.e. something that actually works. ).

Correct. You'd add it to the Running Script. But of course, you won't be starting ('RunWait') Dolphin as LaunchBox is already doing that. What you're needing to do at that point is wait for Dolphin to be running and then wait for it to 'no longer exist' (aka, you exit the emulator). Process, Close, Lichtknarre.exe Process,Wait,Dolphin.exe While WinExist("ahk_exe Dolphin.exe") Sleep 700 run "G:\LaunchBox\0-UTILS\Lichtknarre\Lichtknarre.exe - Shortcut.lnk" A potential problem is, when you exit the emulator, the Running Script gets abandoned. Possibly not allowing the last "run" to execute. I don't know how fast it gets abandoned when the emulator closes. As in, it may still execute the last Run line. If you find it isn't restarting Lichtknarre.exe, you can try replacing the last "run" line with: $Esc:: { run "G:\LaunchBox\0-UTILS\Lichtknarre\Lichtknarre.exe - Shortcut.lnk" WinClose, ahk_exe Dolphin.exe }

Sure. Anyone could make a plugin for those. The issue is, there are some "boxes" that need to be checked. The person doing so would need to have at least a little desire to use it personally. Then there'd need to be an expressed interest from the community to make the time, effort and commitment worthwhile. (Worthwhileness comes in many forms and is in the eye of the beholder.) Spending time to create a plugin that 1, 2 or maybe 3 people [think] they need to have may not be considered a good use of one's personal time. Conversely, it could/would be a great learning tool for that person [creating the plugin]. Making it totally worthwhile. For me, none of those boxes are checked. You mentioned a couple times, comparing the ability to view high scores and achievements. Neither of those are directly related to dynamically parsing MAME features. Unless you're talking about the high-scores plugin that can show you your MAME hiscores. The feature built into LaunchBox only shows the Community High Scores, which are captured when you exit a game and then get uploaded (if certain criteria are met). The achievements are something you find using RetroArch. Which of course is not recommended for Arcade (MAME).

There's always Help & Support > Request a feature. 😊

Myself, I've never found the information MAMEinfo.dat provides too useful. History.xml has similar info to what we get when scraping metadata (release date and a [more-brief] description). True, 'history' does have other info not available elsewhere. That said, I do keep those 2 updated for when I'm messing around inside mame.exe. Though not mentioned, gameinit.dat is useful for games that need it. Once. I do however see some practical use for command.dat. Hence, the View game specific commands from MAME's command.dat plugin. To answer your question, there is currently no way to view the 2 you asked about (1 .dat and 1 .xml) in LaunchBox. Nor is there a Theme that supports them.

Check that you don't somewhere, somehow have 2 copies of that particular dll file. It could be in a different folder. Had this happen to me just the other day and was driving me crazy. Plan B is to post on that themes Support Page.

In that case, in LaunchBox, Edit the game you want to change the default version to be played when you click Play. When editing that game, go to the Additional Apps section [for that game]. There you'll see the different versions of that game. [Single-]click on the games' version you want to set as default. On that same screen, click Make Default [located on the bottom right of that screen]. Click OK to save and close the edit window. Now when you click Play, that version you selected previously and had clicked Make Default for is the version that will be launched.

In LaunchBox you can edit the game and in the Additional Apps section, select the version you want as default and [at the bottom right] click Make Default. This will make it default for BigBox as well. As an aside, in BigBox when you select a game and go into the Game Details screen, you can select the option Additional Apps/Version and from there select the version you want to play. (This assumes you don't have Skip Game Details Screen turned off)

In FinalBurn Neo: Misc < Configure ROM paths... Set the path to your ROM folder(s) [if not already]. In LB, edit the emulator and check the boxes Remove Quotes and Remove file extension and folder path. At least that's what worked for me. I got the same error with those 2 un-checked.

Are your ROMs really file_name.z? (vs. file_name.zip) If they're actually .zip and you think it's a bad setup in LB, can you share some screenshots of your settings (in LaunchBox)? Edit the game, show a screenshot the Launching section. Edit the emulator, show a screenshot the Details section. show a screenshot the Associated Platforms section

May look at moving (installing?) \Lichtknarre\ to anywhere but C:\Program Files\. Perhaps to somewhere like G:\Lightguns\Lichtknarre\... \Program Files\ can be a stickler for allowing/denying access.

Glad that worked. I can't even run Simple64 on any of my [old] machines. So if this doesn't work, hopefully someone else can chime in.. In LaunchBox edit the emulator. In the Startup Screen section (if not already) un-check Hide All Windows that are not in Exclusive Fullscreen Mode

Un-check Remove Quotes. Also, add --nogui to the Default Command-Line Parameters.

As @Layer0730 indicated, since your cab is accessible to the public you really should turn off all updates. Then you, as admin periodically/occasionally/however-often, un-lock BigBox and then in the System Menu select Switch to Desktop Mode. Then once in LaunchBox, go to Menu, Help, Check for Updates.

I don't have anything in my Running Script section for Xenia and it exits fine using the controller button-combo I have assigned to "Exit Game" (LaunchBox) / "Close the Active Window" (BigBox). aka: You shouldn't need any script for exiting Xenia. Is it simply not doing anything when pressing your button(-combo)?

Correct. BigBox is not setup to manage your games. Just looks pretty and plays games.

There's an option that you would have had to specifically tell it "Yes" to delete them. It was probably hidden in amongst all the words in the warning message. By default, LaunchBox will not delete any game/ROM files. Glad you were able to get them installed. Rename the games Title to just "Space Invaders" (not 'Space Invaders / Space Invaders M') then to the right of that click Search for Metadata.

Yeah. I indicated it would be. lol So a quick search came up with this solution: In Windows Explorer, navigate to: \PPSSPP\memstick\PSP\SYSTEM\ppsspp.ini Edit ppsspp.ini Look for FullScreenMulti Set it to True Save and close the file Remove that crap I said to add to the Resume Script

Without digging into the issue too deeply... This may be a bit cheesy, a little crude, but a quick and easy resolve: In LaunchBox, Edit your PPSSPP emulator Go to the Resume Script section and add the following Send !{Enter 2} Click OK to save and close Play games You may see a slight flicker when resuming as it switches [back] to full screen.

MAME is for Arcade games. Appears you had imported them into the Windows platform (vs the typical Arcade platform). By default, LaunchBox sets the metadata/media scraping for Windows platform to Windows [PC Games]. If you wish to keep your Arcade games in the "Windows" platform, edit the platform and set the Scrape-As value to "Arcade" and re-scrape the metadata/media. A more prudent approach could/would/should be to remove all the MAME (Arcade) games from the Windows platform and then [re]import your MAME ROMs into the Platform "Arcade". Then when you download images, you'll get the ones for Arcade games and not PC Games.

I'm fairly certain your "mame64.exe" is from an older version of MAME. Being older is not the issue (and nothing to be concerned with). However, having the command-line parameter -keyboardprovider dinput would be an issue with older versions. Edit your MAME64 emulator ('Edit/Bewerken' from screenshot above) and try removing that and see if it [now] works.

Asked and answered in the previous 2 posts. If you are unable to locate them there, you will need to contact your vendor regarding how they setup your pre-configured drive. [Further] support for pre-configured drives will not be given here.

I trust you're talking about stand-alone MAME (vs (MAME through RetroArch). In LaunchBox, can you edit your MAME emulator share some screenshots. Main Details screen Associated Platforms screen Running Script screen Also, how are you [attempting to] exit the game? Controller (binding to Close Active Window)? Keyboard (Escape)? Does this only happen in BigBox? Or does the same thing happen in LaunchBox as well?