.png.d63b88dc3d5c6db8803dfbd996ce65fc.png)
JoeViking245
-
Posts
5,223 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by JoeViking245
-
-
-
1
-
1
-
-
3 hours ago, Gygoracdes said:
Nobody here on the forum has this thing... I'm guessing
?
What the actual control panel is, is only necessary to know if can be set to keyboard, x-input and/or d-input mode. Well, the number of players and buttons helps too. Beyond that, the panel name, brand or cost is insignificant.
3 hours ago, Gygoracdes said:What exactly needs to be added to this post to make it helpful
If someone were to have a cab that has 2 players, each having a joy and 6-buttons, and have successfully set it up to use with RetroArch (various platforms), Dolphin, Xemu and the sort, sharing which mode they used, and the mappings made is what would make it helpful.
-
31 minutes ago, Gygoracdes said:
Nice gadget ...
but over $500, almost $600!
I'd rather stick with my simple PS2 controller.
Not very helpful. But point taken.
Granted, it does take away from the joy of having a cab, certain emulated systems just "need" to be played with a controller.
-
10 minutes ago, gudwls5022 said:
So, at this point, is there no option to import all files, including those that don't match the database in the specified folder?
I don't believe any platform imports games based solely on the LaunchBox Games Database. Pretty sure they're imported based on the games filename. And in some (most? all?) cases, the file extension as well.
The Arcade platform (or Scrape-As Arcade) is unique to most all other platforms. It imports games base on the filename and extension also, but then looks them up (cross-checks) them against the MAME.xml file (located in the Metadata folder). This file is created by running mame.exe -listxml, as mentioned earlier. This will produce a "list" of all Arcade machines [available to MAME]. The 2 you mentioned were removed by MAME at the request of the games' developers. Note: not all games in the "list" are playable in MAME.
For the MAME derivatives, e.g. HBMAME, they generally use the same set of ROMs and are able to emulate some games MAME can't. And they may also add in those 2 in question (and others?).
I'm not sure if these other Arcade emulators have an available -listxml parameter or at the least, a definitive list of the ROMs (along with the machines game Title) they can emulate. If they do, you might want to put in a feature request to include a custom importing feature for games using those specific emulator(s). (Top of this page, under Help & Support)
-
8 hours ago, gudwls5022 said:
If I'm mistaken or there's a better way, please let me know.
I believe those 2 Cave games were removed from Official MAME, so the ROMs aren't found when running mame.exe -listxml. Which is what LaunchBox uses to cross-check MAME (Arcade) ROMs/games.
When in your FBNeo platform (that's set to scrape-as Arcade), you can press Ctrl+N to manually add them. Fill in the games Title and press Enter (to search the database), they'll be found. Then in the Launching section Browse to your ROM(s). Just be sure to spell DoDonPachi SaiDaiOuJou correctly.
-
1 minute ago, ViperJPB said:
Thx will check that out. No idea why the .238 wouldn’t work for me. Tried a few more. Same issue. Then just copied my old ones over those and they started working again.
Without knowing the specifics on the error(s) (not sure if the error said which exact files were missing), is there a possibility the version of mame.exe you're testing with is not 0.238? Maybe you have different installs and accidentally started testing with an older version of the executable.
Although, looking through the revision releases for the ROM and the CHD, nothing appears to have changed with the 4 total files (3 in the zip and the CHD) in a long time. At least their SHA hashes haven't changed. Not sure if that's an actual indication of anything or not. If my thinking on that is correct, using mame.exe v0.278 with ROM v0.280 and CHD v0.282 should work.
Which leads me to think your CHD's may be screwy. As in, maybe something happened during download. And 'the old ones' you used that did work are "not screwy". (technical term.
)
If you're so inclined, you could cross check the SHA1 hashes of your files against what's shown on Arcade Database.
Or.... just use the older ones and start playing these games.
-
Just tried all 3 and they worked here (0.283 non-merged ROMs and 0.282 merged CHDs). Well Gaunt Legends (1.6) would load and accept coins. But pressing player 1 start wouldn't do anything. But was able to load and start v1.2 (gauntleg12) (which the CHD is [already] in with the /gauntleg/ folder).
As for getting a complete set for the CHD's... some food for thought: (this was as of 0.266 as I'm too lazy to update it. 😊)
There were 640 CHDs, including clones. 351 of those are parents. If those 351, 57 were considered "working". I'd recommend cherry-picking which ones you decide to get.
A great resource for determining which games are considered working is the Arcade Database.
e.g. gaultleg
-
Well, that's good to hear you got it working and sad to hear "the source" file didn't work. The only golden source I know of is PD. The 'archive' source is too volatile.
Which game were you trying? The ROM filename. Call it morbid curiosity, but would like to test it also.
Speaking of "tests", I completely forgot about this little plugin. If all went well, it would have mentioned either an issue with the ROM and or CHD not being accessible to MAME or the files missing (and I believe would also say exactly which files were missing). Maybe if more issues arise.
-
53 minutes ago, ViperJPB said:
Just wasn’t sure if I was chasing my tail and needed to match a merged to merged CHD set or a non-merged to non-merged CHD set?
Ah ya, forgot to comment about that. If you find a non-merged CHD set, I wouldn't trust it.
From a "reliable" source, they are Merged.
Check your mame.ini file for proper formatting of the rompath line. Should be something like:
rompath "roms;D:\My Games\MAME NonMerged;D:\My Games\MAME CHDs"Quotes at the beginning and end, only. ; (semicolon) separating each path. Paths can be relative to your MAME folder. e.g. "roms" is a folder under the MAME root folder.
And since you've done this and it's working directly in MAME, make sure you DON'T have -rompath %romlocation% in the command-line parameters.
-
1
-
-
1 hour ago, ViperJPB said:
All works fine but I can’t get any of the CHD games to run. Does the CHD set need to be unmerged to match the unmerged roms, as my current CHD set is merged? Should I change to a merged set to match the merged CHD set?
Where are your CHD folders located? (semi-rhetorical)
This depends on how you tell MAME where your 'regular' ROMs are located.
- You set the rompath(s) via the MAME UI (or manually edited mame.ini)
- You have -rompath %romlocation% in you default command-line parameters (in LaunchBox - Edit - Emulator)
if (1), you need to also add the path to your CHDs folder.
If (2), your CHD folders need to be in the same folder as your non merged ROM set.
e.g.
- D:\My Games\MAME NonMerged\asteroid.zip
- D:\My Games\MAME NonMerged\dkong.zip
- D:\My Games\MAME NonMerged\gauntleg.zip
- D:\My Games\MAME NonMerged\gauntleg\gauntleg.chd
1 & 2 are non-CHD games. 3 is the ROM for Gauntlet Legends and 4 is the CHD folder\file for it.
-
1
-
58 minutes ago, boy said:
what's the problem?
Assuming the games run in Demul standalone, check all 3 boxes.
-
43 minutes ago, Pixelfetish said:
What helped was to untick "remove qoutes" and "remove file extension and folder path"....and unticking the unzip rom.
Why is that?If you let MAME know where the ROMs are, it only needs the filename (without extension). e.g. gradius (vs. gradius.zip)
That said, you have either
- manually set the ROM paths in MAME itself (told it where they're located),
- you placed them in its /roms/ folder (default location for where it looks)
-
or... in the Details section of your MAME emulator (in LaunchBox), the Default Command-line Parameters has the variable -rompath %romlocation% in it.
- %romlocation% is a LaunchBox variable in which it replaces that with the full path to the ROM with quotes "C:\Path\To\Rom"
- e.g. "X:\_RomArchive\__zipped sets\_Mame Roms\MAME 0.283 ROMs (non-merged)"
50 minutes ago, Pixelfetish said:but not to unzip the rom? I take a guess and it is not related to mame but LB unzipping the rom beforehand, which is not working.
NEVER unzip MAME ROMs. That's just how MAME (and any emulator using MAME ROMs [e.g. SuperModel3]) works.
51 minutes ago, Pixelfetish said:but why is this feature an option anyway?
Some emulators need to have the ROMs unzipped to be able to emulate them. 90%+ of the cores in RetroArch for example.
-
1 hour ago, Pixelfetish said:
Every attempt to start via Play in LB fails.
In LaunchBox, edit your MAME emulator and uncheck Extract ROM in both
- the main Details section
- the Associated Platforms section
If there's still issues, share a screenshot of both those sections so we can have a better look.
-
4 hours ago, AdamL said:
How does LaunchBox know whether or not the rom name is part of the set?
Depends on the platform. MAME (and a couple others) aside, ROMs are typically named after the games Title. For MAME (Arcade), LaunchBox will parse the xml result from mame.exe -listsml to "convert" the ROM name to the games' Title.
I didn't realize Daphne had its own set of ROMs. I've only ever used Hypseus Singe for LD games, which uses MAME ROMs (and can be scraped as Arcade). You can watch a tutorial here.
Provided Daphne has an accessible means of "translating" ROM name to game Titles (e.g. the -listxml parameter or a definitive source), you might want to put in a feature request (top of this page under Help & Support) to add it as a Scrape-As value.
-
4 hours ago, SiriusVI said:
Well, anyway, I'm just glad I won't have to start from scratch. On the other hand, now I have to manually edit all of my over 400 existing platforms and delete the <Installed>false</Installed>. That will take some time, too.
At this point, it seems you should be able to go into the All platform,
select all games, press Ctrl+E to start the bulk edit wizard, set Installed to the white filled box.
vs. or
Get it done in virtually no time.
-
9 minutes ago, AdamL said:
It did. I removed it, and it makes the path relative — so all is working now.
Where does the %romlocation% get defined?
It's a built-in LaunchBox variable. LaunchBox inserts (replaces it with) the full path to the ROM with quotes. e.g. "C:\Path\To\Rom"
Here, MAME sees it as the parameter -rompath "C:\Path\To\Rom"
Which makes it real nice, so you don't have to set any of the ROM paths in MAME itself.
-
18 minutes ago, AdamL said:
Is there a way to just add lair.zip to the list of roms that Launchbox will take?
Thanks!
Is it a MAME ROM? When I looked, "lair" doesn't exist. But "dlair" does. (Maybe 'lair' is an old ROM name???)
-
18 minutes ago, AdamL said:
How do I change the rompath?
Depends on how you have MAME setup.
Where are (were?) the ROMs located? Did they get moved also?
When you edit your MAME emulator (in LaunchBox), does the Default Command-line Parameters have -rompath %romlocation% in it?
-
Actually that probably won't work. Would it cause major heartache to rename the ROM to dlair.zip? (Since "lair" doesn't exist in MAME)
Worse case, you can press Ctrl+N and add the game manually.
-
56 minutes ago, AdamL said:
My guess is that Launchbox is checking a database or spreadsheet somewhere and if it doesn't find the rom listed, it doesn't import it.
Tell LaunchBox that the Daphne emulator is using MAME ROMs and see if that works to import it. a.k.a. Check the box.
-
1 hour ago, AdamL said:
I want to move the whole MAME folder inside the Emulators folder
Then do it.
- D:\My Emulators\MAME\
- D:\LaunchBox\Emualtors\MAME\
Then in LaunchBox, edit your MAME emulator (Tools - Manage Emulators) and change the Application Path for mame.exe to the new location. (Best to use the Browse button rather than manually typing it.)
Actually, COPY it first [change the app path] and test it before deleting it from the original location. It should work fine. Consider it cheap insurance.
This should work as well for other emulators. But always do the copy/test thing first.
-
1 hour ago, SiriusVI said:
reverted back by launchbox after a restart
If you don't have any backups, how? (Rhetorical. Read on...)
Disable cloud syncing???? (grasping at straws)
Your "old" one has <HasCloudSynced>true</HasCloudSynced> Whereas the new one is set to false.
Maybe not disable it in LB, per se. But edit the xml with a find <HasCloudSynced>true</HasCloudSynced> and replace with <HasCloudSynced>false</HasCloudSynced>
-
47 minutes ago, Jayinem said:
it instantly gives me the "Launchbox is already running" msg after choosing switch to desktop mode in Big Box.
When switching from one to the other, one closes, does its' save thing, then the other opens. Maybe you need to add a sleep timer in the "If it is not running" to check/double-check again to catch this scenario.
Try spelling it all out first (create a flowchart of sorts) accounting for all scenarios. Then write/adjust the code based on that.
-
If it is not running
- sleep 10 (or more?) seconds (it may be in the middle of switching to BB [or LB] via the app)
-
check [again] if LB OR BB is running
-
if one of them is, you probably 'switched'
- "Move along. Nothing to see/do here."
- otherwise try starting LB
-
if one of them is, you probably 'switched'
- etc.......
- etc.......
-
If it is not running
-
12 hours ago, Jayinem said:
I just realized something the script that forces Launchbox to stay open is causing the issue.
Woops!
Honestly, you'd be better to just add LaunchBox to your taskbar making it one click away rather than having this running and constantly checking. Would eliminate a lot (all?) of these issues.
But if you must.... just add another check inside of "If it is not running" to see if Big Box is running. Then process accordingly.
BTW, the Sleep timer you have, really should be closer to 1 or 2 (or more?) seconds vs. every 5 milliseconds. There's no reason to have it check if LB is running 200 time per second.
vs. 
or 
Good Tutorial On Button Mapping?
in Collections and Builds
Posted
Your panel can do keyboard, x-input and d-input mode. The encoder I have only has keyboard mode. I presume you'd use KB mode for MAME (but it can use x-input mode). It would be easiest to stick with just 1 mode for all emulators. Keyboard seem fairly universal.
That said, your panel most likely has a command line that can be sent (e.g. when starting a specific emulator) that can change modes on-the-fly. Or probably even a button-combo to change it.
Still thinking keyboard mode, your panel is most likely setup (universally) as:
For RetroArch, I believe most consoles it emulates should automatically get setup. (Again, thinking keyboard mode)
For others that typically use a controller, it can be done on a panel. But it's a little less intuitive. And you need to plan out what works for you.
Using Dolphin (Wii) as an example, for Mario Kart Wii, I set mine up like:
But I set that up a long time ago and have since got an Xbox 360 wireless controller. It seems to be the most universal for most all systems. You don't have to set it per game (but you can). However ["a long time ago"] that's what I did. But for just a couple of games.
The long and short of it is, you need to do it per emulator (RA aside). And assign them in a layout that's comfortable to you.