-
Posts
4,332 -
Joined
-
Last visited
-
Days Won
34
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by JoeViking245
-
How to choose the core during a Retroarch import process
JoeViking245 replied to legolas119's topic in Noobs
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
-
Launchbox Question about Emulators/Directories
JoeViking245 replied to KevlarMike's topic in Collections and Builds
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. -
1st time using launchBox, MAME will not run, only show contents of zip files.
JoeViking245 replied to tk007b's topic in Noobs
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.
-
Custom Badges
JoeViking245 replied to jayjay's topic in Third-Party Applications and Plugins (Development and Beta Testing)
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. -
MAME History.xml Viewer
JoeViking245 replied to JoeViking245's topic in Third-Party Applications and Plugins (Released)
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. -
MAME History.xml Viewer
JoeViking245 replied to JoeViking245's topic in Third-Party Applications and Plugins (Released)
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.)
-
Is there any way? Sure! If I'm understanding correctly, when you say "filter the platform games list", I'm assuming you're doing this one platform at a time. vs. meaning all games in your collection. And for that platform, you've created 2 "collections". And by "collections", I presume you mean Playlists. (mere semantics, but it's important). Example [of my understanding]: Platform = Arcade Playlist-1 = "Games that are a lot of fun" Playlist-2 = "Games that are no fun" One way to "filter" these is: Select your Playlist-1 (to see games you have in there so far) Select one of the games and edit it Add a new Custom Field, call it "Lots of Fun" (or whatever you want) Set the value to "true" Save and close the Edit Game window Select all game in that playlist (click one and press Ctrl+A) Press Ctrl+E to start the Bulk Edit Wizard For Field, select Custom Field: Lots of Fun Enter "true" for the value Continue through the prompts to execute, save and close Select your Playlist-2 Do the same as above, changing "Lots of Fun" to "No fun" Now.... Create a new Playlist In the Auto-Populate tab, check the box Set the following Field = Platform, Comparison = Is Equal To, Value = Arcade Field = Lots of Fun, Comparision = Is Empty Field = No Fun, Comparision = Is Empty Click OK to save and close This new Playlist will now contain any game in your Arcade platform that is not in either of those 2 playlists.
-
As shown above. %romfile% -localdata
-
After adding the parameter, may need to re-setup the emulator (BIOS location etc.).
-
The -localdata parameter makes it so the emulator is portable. It creates a folder in the same location as the emulator to store data. Otherwise (aka without the parameter), all the data is stored in the AppData folder (under C:/users/) making it not portable.
-
When you make the copy and then edit to remove the blur, I'd be curious to hear how you like the outcome after using it a while. It seems to me that if both the background and the logo were both at full visibility (for lack of better words), they could [to a degree] cancel each other out (with like-colors blending into each other) making the logo hard to see. I suppose that would vary from game-to-game, depending on the actual images used together. Then again, it could be that I'm just not seeing it correctly in my head (and don't have a marquee to do any real testing). And it might look pretty dang amazing.
-
LaunchBox doesn't sell hard drives. You need to contact your vendor regarding how to install games on their drive.