JoeViking245

Create a new text file and save it to somewhere you won't forget nor accidentally delete. Say somewhere like "D:\LaunchBox\ThirdParty\AutoHotkey\MyAHKs\" Inside that text file, put: Sleep, 20000 Send, ^0 $Esc:: { Send, !{F4} ExitApp } Now save the file, but save it with an "ahk" file extension. Say something like "noxScript.ahk". (make sure it doesn't save as "noxScript.ahk.txt") In Edit Game, go to the Additional Apps section and click Add Application... Give it a Name. In the Application Path, Browse to your ../LaunchBox/ThirdParty/AutoHotkey/ folder and select AutoHotkey.exe. In the Application Command-Line Parameters:, type in the full path to where you saved the file you created above. And put quotes around it. Check the box Automatically Run Before Main Application. Click OK and OK. Run your game and wait 20ish seconds and see if it goes fullscreen.

MAME stand alone (i.e. mame64.exe) and MAME being ran through RetroArch, though essentially the same, are 2 different animals when it comes to troubleshooting. You indicated you have RetroArch and MAME installed and mentioned you tried 'in just MAME' (leading me to think you tried in MAME stand alone). Please clarify. A lot of times, "missing files" can be caused by using mismatched roms and the executable (or in the case of RetroArch, core). But probably more-so are caused by acquiring incomplete rom sets. Does your rom set version match the version of your MAME executable and/or the core you're using in RetroArch? What game are you trying and what files does it say it missing? (a screenshot of the error message would work best for this).

You're missing files. Are you getting your MAME emulator from https://www.mamedev.org? The 1st error is referring the folders/files that should be in the language subfolder of MAME.

@Jayinem Ya, I was thinking more along the lines of type that into a Google search and see what comes up. The 2.0 vs 3.0 thing just happened to have gotten caught in the snapshot. Am pretty sure there are several other things listed to check.

To [initially] create the "mame.ini" config file, at the command prompt type mame64.exe -cc and press Enter. It'll either save it in MAME's root folder or in it's "ini" folder. Check both locations. But when you double clicked Save Configuration, it should have (I think) created it.Regardless, the above command will create it. If it doesn't, you have other underlying issues.

You could probably write a script to check it (and possibly reconnect it). But you'd be much better off fixing the underlying issue.

Hmmm... it worked here on my tests. CXBX may be launching a sub process, so from the main script, RunWait 'quits' right a way but the files will still be locked so FileRemoveDir can't touch them. Though if that were the case, you'd probably also see "Thanks For Playing" right away as well. Try putting in a Sleep timer before deleting the files. Giving CXBX a chance to release the files.

mame64.exe ti99_4a -ioport peb -ioport:peb:slot3 speech -cart rom_name This only works from the command line or a batch file if you change "rom_name" to an actual rom's name. In LaunchBox, you could instead edit your MAME emulator and in the Associated Emulators tab, do something like thisNote: the line above also sets the emulated memory to 32k. Also, don't put "mame64.exe" at the beginning nor the "rom_name" at the end as with a batch file.

Speaking of "quotes"... Looks like they need to be REMOVED from the last line (FileRemoveDir.....). And since it's also creating the subfolder, you'll need to set recurse to "true". FileRemoveDir, I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%, 1

Nice catch!! Glad to have helped guide you and that it's working now.

After the xbeFilePath line add in MsgBox, %xbeFilePath% ;See what it's finding. If anything. The "R" on the Loop line... "R = Recurse into subdirectories (subfolders)" So basically it will drill down through the subfolders looking for the specified "F"ile ('default.xbe'). May need to add quotes.?.?. (just a guess) RunWait, "I:\LaunchBox\Emulators\CXBX-R\CXBX.exe" "%xbeFilePath%", 1

If it's safe to say, that after extracting "Futurama[!].7z", of all the folders, subfolders and files that are extracted from it, no matter how many there are, there is ONLY ONE file that is named "default.xbe"... then this should work. fullPath = %1% SplitPath, fullPath,,,,romName RunWait, "I:\LaunchBox\ThirdParty\7-Zip\7z.exe" x -y -o"I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" "%1%",,hide xbeFile = I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%\default.xbe Loop, Files, %xbeFile%, FR xbeFilePath .= A_LoopFilePath RunWait, "I:\LaunchBox\Emulators\CXBX-R\CXBX.exe" %xbeFilePath%, 1 ;FileRemoveDir, "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" Note: The 1st RunWait line was modified. If all goes well, xbeFilePath should equal I:\LaunchBox\ThirdParty\7-Zip\Temp\Futurama[!]\Futurama\default.xbe

Stupid illegal characters. lol My bad... Change the "SplitPath" line ;Not this any more ;SplitPath, %1%,,,,romName ;Now this (these) fullPath = %1% SplitPath, fullPath,,,,romName The rest should be the same. I hope.

Gotch'ya. My Mini's super old and don't thing it'll even take the 5.0 firmware.

Can the mini even be switched to Xinput?

Your best bet might be to create an AHK script that is the emulator. Something similar to ; %1% = "I:\LaunchBox\Games\XBox\my_game.zip" MsgBox, %1% SplitPath, %1%,,,,romName ; romName = my_game MsgBox, %romName% RunWait, "I:\LaunchBox\ThirdParty\7-Zip\7z.exe" x -y -o"I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" "%1%",,hide if FileExist("I:\LaunchBox\ThirdParty\7-Zip\Temp\default.xbe") { MsgBox, It exists FileMove, "I:\LaunchBox\ThirdParty\7-Zip\Temp\default.xbe", "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%.xbe", 1 } RunWait, "I:\LaunchBox\Emulators\CXBX\CXBX.exe" "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%.xbe", 1 FileRemoveDir, "I:\LaunchBox\ThirdParty\7-Zip\Temp\%romName%" The MsgBox's are for testing. I've never used CXBX, so don't know if it looks for an xbe file or something else (adjust accordingly) "my_game" needs to be named whatever it is CXBX is looking for (minus the extension). Save the above script somewhere (i.e. I:\myScripts\CXBX.ahk) For the "new emulator", set the Emulator Application Path to "ThirdParty\AutoHotkey\AutoHotkey.exe" (relative path works) Set the Default Command-Line Parameters to the full path of you created .ahk script [above], all inside quotes. ("I:\myScripts\CXBX.ahk") Leave all boxes unchecked. The Sample Command will look something like AutoHotkey.exe "I:\myScripts\CXBX.ahk" "FULL\PATH\TO\ROM\FILE" Now set your games to use this "emulator". This isn't tested and probably needs some adjustments but should give you a good idea of how to make what you're after, work.

Write that script to a text file and save it with the .ahk extension. (i.e. test.ahk) For the game(s) needing this, Edit the game, select Additional Apps, then Add Application. For the Application Path:, Browse through your LaunchBox folders and select AutoHotkey.exe. (i.e. D:\LaunchBox\ThirdParty\AutoHotkey\AutoHotkey.exe) For the Application Command-Line Parameters:, type, between quotes, the full path to your saved .ahk file [from above]. Check the box "Automatically Run Before Main Application". Then click OK. Oh.... don't forget to give it an Application Name. You'll probably need to lengthen the Sleep time. I'd say start with 10 seconds (10000) just to verify that it works. Then dial down from there. You may be able to avoid the 'Sleep' altogether if the Window title is ALWAYS going to be "M.U.G.E.N." as in your screenshot. SetTitleMatchMode, 2 SetKeyDelay, -1, 110 Loop { ifwinactive, M.U.G.E.N. { Send !{Enter} break } }

$n:: Click, Left $b:: Click, Right ; Alternate $a:: Click, Left $s:: Click, Right $h:: Send, p Sorry. Know nothing about ScummVM.

It depends on the emulator. Some will have in their settings a check box (or something similar) to 'start fullscreen'. Or they may have an available command line parameter (i.e. -fullscreen) that you put in with your emulator settings in LaunchBox. Tools, Manage Emulators, Edit [the specific emulator] It would then go in the "Default Command-Line Parameters" box.

Tools, Manage Platforms. See if it exists. If it does, (and it's not showing 'on the left') it probably says "Associated Games" is 0 [zero]. No sense in showing a Platform that doesn't have any games. Once it has games in there, it'll show up. Some thoughts: On the left, in the dropdown, select Platform (vs Platform Category) until you get 'the hang of things'. Helps me at least. lol. You can call 'this' Platform anything you want (i.e. MAME), but in the long run it may be better to call it "Arcade". Only reason being when you search for help or watch videos (tutorials), "Arcade" is what's more-so commonly used. Or just be prepared to interpolate.

When you use the Full Set Import Wizard, it doesn't actually look at the roms you physically have. It imports based on what MAME says is included in the Full Set (minus any items you checked to not import). I think what yo can do is, after using the wizard, click Tools and then 'scan for deleted roms' (don't have LB open for the exact wording). This should then get the games in your Arcade Platform that point to a file(s) that doesn't exist and give you the option to remove those form LaunchBox.

No. At least I don't think so.

From PD. It'll be with the Full Set [as opposed to the Software List ROMS (split)] And will contain 5 files.

When you run MAME by itself (mame64.exe), do the games work from there? Also, when in MAME, be sure to click "Available" on the left pane first.

Wasn't a Star Rating popup 'thing' done in one of Jason's YT Plugin tutorials? It's been [quite] a while, but I know there was at least a something he did using Star Ratings.