JoeViking245

They were both found here. Make sure your Platform is set to Windows. May also try to force update your local database. Tools < Download < Force Update Games Database Metadata...

Ahh. I don't know how to use RetroArch as a frontend.

I think.... Go to System Menu < Options < General < Remember Last Platform (enable this) Go back to your platforms view and select your Windows platform. Exit Big Box Restart Big Box (should start at the Windows platform) Go back and disable Remember Last Platform

The yellow light means the hash value of the file doesn't match what our records show it should be. I believe if you mouse-over the yellow dot, it'll tell you that. When you launch a game, it'll tell you it's "missing". If you do it in LaunchBox there is a "stop reminding me" button you can check and then launch the game, and it won't bug you about it anymore. But since the game won't launch (after bypassing that message), you most likely have the wrong, or a corrupt version of the BIOS file. So probably don't click the 'stop reminding me' button until that's resolved.

Drag and drop the .zip file onto LaunchBox. Or press Ctrl+N to add a new game.

Edit your PacMan game. Under Emulation, check the box Use Custom Command-line Parameters. in the space below it, add -plugin pactrainer. This will actually send the command mame -plugin pactrainer pacman. But should work just the same. If you use the LaunchBox Pause Menu for Arcade, shame on you. But if that's your thing, you'll need to add -keyboardprovider dinput -plugin pactrainer for it to work.

If you have games in a single platform that use different cores, you will need to add the Custom Command-line parameter to the ones not using the default core for that platform (as described above). One-by-one. Alternately, for the games using the non-default core, you can (after importing) add the Custom Command-line parameter to them all-at-once using this plugin:

If you reinstalled LaunchBox, check your install location. Make sure it's not something like D:\LaunchBox\LaunchBox\LaunchBox.exe

Well.... I didn't before. But with a little ingenuity, I know it now.

from hod2bios.zip, copy epr-21330.ic27 into naomi.zip and it'll work. Not sure why Demul is looking in naomi.zip for that file. But doing the above works. At least in my test when launched directly from Demul. Even in 2018 (Demul's latest release), that file was never in there. Though the compatibility list does indicate it takes a "Cust" (Custom?) BIOS. Maybe the above 'fix' is what that means. Of course, this will screw things up when you go to update your MAME ROM set. The "fix" for the 'fix': Copy the modified naomi.zip into your /Demul/roms/ folder and then add that path to Roms and Bioses Path in Demul itself.

The 'missing' file can be found in hotd2.zip and hod2bios.zip. Make sure Demul has access to hod2bios.zip (as in, make sure that file is in the same folder as hotd2.zip).

To best help, you should tell us the actual paths you had in there. I presume those are "example paths" and I'm surprised it let you [attempt to] launch the game using that relative path. It should have said [something like] "ROM file not found". Assuming the absolute path is E:\Emulators\emu\game.int, the relative path should be ..\Emulators\emu\game.int (also assuming LaunchBox is in E:\LaunchBox\) Can you share screenshots your version of the 3 I show above?

Edit emulator - NO boxes checked (except in Associated Platforms - Default Emulator). -f1 for fullscreen. Edit game - point to the .int file

The "best way" is in the eye of the beholder. Since LaunchBox doesn't ever touch any emulator settings or configurations (beyond you asking LB to install or remove them), as long as it knows where the main executable is located [and it's told the proper command-line parameters to use], it should be fairly infallible. It does offer the /Emulators/ subfolder. Consider it an effort to "keep things together". It can also aide in keeping your LaunchBox setup portable in that you only need to move that one folder (/LaunchBox/) when moving it to a new location. Caveat: Not all emulators are innately portable. Most times this can be resolved by adding a file to the emulators main folder (e.g. an empty 'portable.txt' file). Emulators that you allow LaunchBox to install for you will be made portable. Similarly, ROM locations can be placed wherever you want them to be. The /Games/ subfolder is a good location, but not a requirement. However, do note that placing your ROMs in the respective Platforms' folder under Games has the benefit of, when you add more games to that folder, LaunchBox has the ability to automatically add them into you LaunchBox collection (platform and emulator pending). That, is the end goal. LB knowing where these are located. That's a lot of corruption going on. My 1st thought would be to check your drive. Make sure it's healthy and error free. Placing the emulators within the LaunchBox folder structure won't alleviate any corruption. A potentially faulty drive aside, this is typically caused by not properly shutting down LaunchBox. Note, when you close LaunchBox (e.g. click the X in the upper right corner), the UI will close virtually immediately. However, it will still run in the background shortly while saving data. If you turn your PC off immediately after exiting LaunchBox, or worse, turn your PC off without exiting LaunchBox, the data will not get saved. Potentially causing you LaunchBox issues.

You could try this and see if it sheds any light...

Give this a read. Hopefully something in there will resolve the issue. Plugin Access Denied Error - LaunchBox

The default location change in version 13.21 with the advent of Media Packs. You can find more information about them here: LaunchBox Media Pack Feature – Version 13.21 - LaunchBox

The intent of the plugin is to bulk change game titles to that of a different Region. The issue with renaming the media is, say you went from NA to JP, your JP titles will be displaying the [e.g.] NA Box-Front. Assuming one's available, [I would think] you'd want to have the actual JP Box-Front displayed. This was, to a degree, thought about. And for the above reasoning, it was quickly forgotten about. Well, ignored. If there's a common scenario (vs. something niche) I'm missing where this would be viable without causing other issues (e.g. image location based on Region [and rename AND having to move them, then having an NA image in a JP folder...]), please let me know. State your case. Give an example or 2 of use-case. Behind the scenes, there's also some logistics of image file locations and folder placement. Relocating the images from one region folder and then move them to the new regions folder? Keep them in that folder and hope LB still looks there [now, with the new filename]. Not sure. TBH, sound like a pain.

With the advent of the new Media Packs introduced in v13.21, the embedded image in [new] Custom Badges are not getting extracted. Manually adding the image file you used into the Nostalgic Platform Badges folder and naming it after the plugins’ Unique Id will allow the badge to show. There is a Bug Report submitted (is not publicly visible yet), so the developers are aware.

You're welcome. 😎 Yeah, for something like that (see it for each game, on-the-fly), you're probably stuck with MAME or one of it's derivatives (i.e. MAMEui). If you're super ambitious, you might be able to create a Theme, that calls a plugin (similar to, but not this one) to grab the history info, and then squeeze that into the panel on the right side of the screen. But that'd be kind of a pain. But I'm sure it could be done. But you know, eventually will have to play these games too.

Thanks. To answer your question, you could try the frontend called LaunchBox and then install this plugin to get what you're after. But you may want to install a different plugin instead (see below) that give s you 3 viewers in one. It lets you view game specific commands from MAME's command.dat, the specific games history using MAMEs History.xml (just like this plugin) and/or initialization procedures of games emulated by MAME that require some setup which reads from MAMEs gameinit.dll.

Anything's possible. To test, you could try removing the contents of your emulators \UserData\ folder. Then copy the contents of your \AppData\Roaming\BigPEmu\ folder into it. Then use the %romfile% -localdata parameter(s). If that works, you can remove the /AppData/Roaming/BigPEmu/ folder.

If you disabled Confirm, it's not even sending Escape once. Well, it is actually sending it. It's just that RA is not receiving it. There's some fancy shmancy things you can do to make it work that way. But since we're just trying to close the emulator, let's just cut to the chase. Which is what you did in your last post. But I think (not totally sure), the 2nd Return might be 'causing issues'. The Q hotkey is redundant to pressing Escape. But if you'd rather press Q than Escape, then go ahead and keep it in there. Lastly, when testing, be sure to wait the w h o l e 5 minutes (300,000ms) plus 6 seconds +/- for the initial 'check'. #Persistent SetTimer, Check, 6000 return Check: IfGreater, A_Timeidle, 300000 WinClose, ahk_exe {{{StartupEXE}}} ;optional $Q::WinClose, ahk_exe {{{StartupEXE}}} This worked for me. (5 minutes was a long arse time to wait for a test. But I waited. ) But fortunately/unfortunately, this is the exact same thing as the OP. Except with a different wait/idle time, using WinClose (which is preferred over Process, Close) and formatting out the WinClose line (which functionally, doesn't make a difference [similar to my 'Q' hotkey]). That said, not sure what else to tell ya.

I suppose I could have looked to see that you posted in the LaunchBox Games Database section. But then again, people occasionally post "whatever, wherever" too. To answer your question (as intended), no. Not in a manner innate to LaunchBox at least. I suppose you could create a plugin that would parse your local database file (in general, a copy of the online Games Database) and have it cross your given platform (or e v e r y t h i n g) for missing games. Or a facsimile there-of (like adding genre filters).

I've never tested it, but looking at it, it should. As for running Arcade games using RetroArch vs. stand-alone MAME, that's a different thorn. To explain what the script is doing, it's checking every 6 seconds. During "the check", if there's been no keyboard presses or mouse movement for a cumulative of 2 minutes, it will (should) close the app. So if you touch the mouse at all (or press a key), A_TimeIdle resets to 0. To verify the script at least started, below #Persistent, you can add a line MsgBox, script started. (Though you might not be able to see the message box behind the Loading Screen. And... it might pause the script until you click OK.)