Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    2,902
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by JoeViking245

  1. I'm guessing when you run it from the command prompt, your full command line has "the/full/path/to/the/romname.zip" at the end? (vs. just romname itself with no path and no quotes) Even if my assumption is wrong, try editing the Default Command-Line Parameters for Emerson Arcadia 2001 and add -rompath %romlocation% Also, you should be able to remove "-cart". So you'd have: arcadia -nowindow -skip_gameinfo -rompath %romlocation%
  2. Can you provide a screenshot of the Details screen for you MAME emulator please. Tools, Manage, Emulators, select you MAME emulator (I trust there's only one listed). Make sure you're pointing to the correct mame.exe if you happen to multiple installs (it happens, on purpose and by accident ).
  3. Thanks! Glad you're liking it. There's currently no option to automatically go to the next game when an error occurs. My thinking is: if there's an error converting, it's most likely you're using an older/outdated version of chdman.exe. (Other issues are possible, but this seems to be to most common one.) So you get the popup message and [optionally] attempt the next game. After seeing 2 or 3 of these error messages in a row, rather than attempting to convert [and failing?] the next 120 games, you can quit scanning and resolve the issue causing conversions to fail.
  4. Oh ya, and if you want to use LaunchBox's Pause menu... well, you won't be able to. But beyond that, happy gaming.
  5. This thread was originally talking about RetroArch, but sounds like you might be referring to standalone MAME. If that's the case, edit your MAME emulator in LaunchBox and remove from the default command-line "-keyboardprovider dinput".
  6. The LaunchBox Development Team will most likely have this issue resolved with their next beta release.
  7. I wish it were that simple. This erratic behavior can be reproduced without the (or any) plugin(s) being present. (Only tested with version 12.11) Exit LaunchBox Delete any and all plugins in the Plugins folder. Start LaunchBox Go to Tools, Manage, Platforms Click Add Click the dropdown for Scrape As (everything looks OK) Click Cancel. Click Close. Go to Tools, Manage, Platforms, Click Add Click the dropdown for Scrape As Scroll down past the blanks until you start seeing the list of Default available Platforms
  8. This Special Edition version adds a change to renaming "PC Engine" to "NEC TurboGrafx-16" when updating. If you have a Platform for NEC TurboGrafx-16, NEC TurboGrafx-CD or PC Engine SuperGrafx (or any variant of these 3), after you have all your metadata and media for that Platform, set that Platform to Scrape As "NEC TurboGrafx-16". This will ensure the Retro Achievement badges appear in your Platform. RetroAchBadge v2.2.1SE.zip Download and install this version the same way as How to install the plugin: listed at the top of this page.
  9. Because Retro Achievements combined PC-Engine, TurboGrafx-16 and TurboGrafx-CD games all into one category/console/platform. There are 86 games listed in that 'console' (PC-Engine) spread amongst those 3 listed. Some of those 86 also happen to fit into 2 different ones. i.e. "Alien Crush" achievements are in both TG-16 and PCE. I haven't decided on whether to change "PC Engine" to "NEC TurboGrafx-16", "NEC TurboGrafx-CD" or "PC Engine SuperGrafx". Though I think "NEC TurboGrafx-16" may be the logical choice. For now, you can edit AllGames.xml and rename "PC Engine" (approx. line #2307) to "NEC TurboGrafx-16" and save it. And as long as Scrape As is set to "NEC TurboGrafx-16" for your given Platform, the badges will appear.
  10. It will show that error when chdman fails to convert the file. This is where plan "B" comes into play... Open the Windows Command Prompt to where your cue/bin files are located and run the command "d:\Mame\chdman.exe" createcd -i "filename.cue" -o "filename.chd" Change (inside, and keeping the quotes) the full path to where your chdman.exe file is located. also change (again... inside, and keeping the quotes) "filename" (2 locations) of the cue file you're converting. i.e. "d:\Mame\chdman.exe" createcd -i "Lunar-Silver Star Story Complete (Disc 1).cue" -o "Lunar-Silver Star Story Complete (Disc 1).chd" If (when?) it fails here, it should give an indication as to why. You didn't by chance simply rename your m3u to cue? That won't work unfortunately. You need to have all the different discs imported into LaunchBox and pointing to their respective game_name (Disc #).cue files.
  11. That's odd that it removed the other 2 added games when adding these 2. And more confusing when you added the other 2 back in, these 2 stayed. I'm calling it a Win! 😁 Oops. fixed. This may fix some other little oddities as well. RetroachievementBadges (v2.1.4).zip Nice discovery on the Aero Fighters 2 and seeing the achievements in LB! Since (it looks like) it wants the Neo-Geo AES port to be able to gain achievements, you may need to add "aes" to the command line for that game. i.e. "mame.exe aes sonicwi2".
  12. Your 'shorter' title is also listed (in AllGames) under Nintendo Family Computer which is the console name it will look for first. If it doesn't find the games' Title there, it will then look under the scrape-as console name. (just an FYI) Between then and now, I was doing some code cleanup and don't think I really changed anything when I had a thought. (ya, crazy. I know!) I created a new Platform called Nintendo Family Computer (a novel idea) and added Akumajou Special: Boku Dracula-kun / Kid Dracula to it. And the badge appeared. I then renamed it to Akumajou Special: Boku Dracula-kun and there was (as expected) no badge. Right clicked, added the badge, and it showed. Ran the updater, the badge was still there. Same thing with DQ6. So either I did change/fix something, or "you got issues". Try this. RetroachievementBadges (v2.1.3).zip If it's still not working, edit the game(s) and check the Title. Maybe there's a leading or trailing space, or one of the characters is an atypical ascii character (even though it may look OK)... Actually, better yet, if to the right of the Title there's a LB DB ID#, click the red X and then Search for metadata and select the game that appears. Click OK. If no LBDB ID#, Search for metadata, select game and click OK. BTW (at least on mine), no Retro Achievements show in LB for the game Akumajou Special: Boku Dracula-kun. Also, I did end up playing it for about 15 minutes to "see what it's all about". It kind of fits in line with my style of old-school Nintendo games.
  13. To clarify, for Nintendo Family Computer and Super Famicon, most of the games having achievements show a badge.?. The 2 games mentioned for these consoles don't show a badge. Which makes sense because they are named differently from what R-Achievements names them. But an issue remains (at least with these 2) that if you right-click and click to add a badge, it doesn't appear? I see the games are getting added to the Added.xml. Are they showing up in AllGames.xml? (pro-tip: When viewing AllGames.xml in Notepad++, press ALT+2 to collapse it just the consoles. Then you can click the + next to the console you actually want to see the games for.) Actually, can you share your AllGames and Added xml files? (just drag & drop the file onto your reply) I'm at least glad to hear most all of the other idiosyncrasies are getting ironed out.
  14. I'm pretty sure I fixed it "this time". 🤞 This was mainly an issue with Titles that had an ampersand in them. ("Dragon Quest I & II") Another issue I saw a couple times in the vids had to do with capitalization. (Jeanne d'Arc vs. Jeanne D'Arc) These 2 issues should be fixed as well. With these last 2 fixes, can you see how it looks without using the Added.xml file? Before updating with this version, delete, move or rename Added.xml. Run the updater, then see how your badge collection looks. RetroachievementBadges (v2.1.2).zip Second verse, same as the first. (download, unblock, unzip, replace the 1 file, run the updater...) Let me know how it goes. 😎
  15. Edit your emulator for your BuildGDX. (Tools, Manage, Emulators). Under Default Command-Line Parameters:, (based on the information you provided) put -path %romfile%, -silent Leave all check boxes un-checked. I presume you already have given the emulator a name, pointed to the Application Path and selected a Platform under Associated Platforms. I've never heard of nor used BuildGDX, but I'm skeptical about the , (comma) in the command line you show. (You don't typically see those) So if the above Command-Line isn't working, try it without the comma. -path %romfile% -silent
  16. Thanks for the screen shots. The CUE file appears fine. Please Edit your game Lunar-Silver Star Story Complete. Based on the output display, I'm guessing you have (Disc 1) as the main game and (Disc 2) is an Additional App. Go to the Launching section and share a screenshot of the 1st field, ROM File. My guess is that it's not point to "Lunar-Silver Star Story Complete (Disc 1).cue". Now go to the Additional Apps section and edit the one for Disc 2. (assuming it's an Additional App) Check the Application Path. Is it pointing to "Lunar-Silver Star Story Complete (Disc 2).cue"? If my guess is correct, they both do not point to file_name.cue. (quite possibly they point to .chd? [which doesn't exist]). If that's the case, change the file extensions [back] to .cue, save and run the plugin again. If that's not the case and/or it doesn't resolve the issue, we'll look at Plan "B".
  17. I was able to download them and am viewing them now. Thanks again. I'll do some checking.
  18. These should still work fine. 1 CUE per disc. So your imported games would be something like (4 separate games in LaunchBox) This_is_a_game_(disc_1).cue This_is_a_game_(disc_2).cue This_is_a_game_(disc_3).cue This_is_a_game_(disc_4).cue And then in your folder you'd also have something like This_is_a_game_(disc_1).bin This_is_a_game_(disc_2).bin This_is_a_game_(disc_3).bin This_is_a_game_(disc_4).bin For the multi-disc games, you say you see in the output window that is says "Checking main game This_is_a_game_(disc_1)". Then right after that, does it say "Converting Complete"? Or does it go right to saying "Checking Additional Apps...."? If it doesn't show "Converting Complete" or "Error Converting", then that particular game ("This_is_a_game" in this example) isn't pointing to a CUE file. Double check that the games path is pointing to a .cue file. If you had created a .m3u for these multi discs, that won't work for converting. Are you using the most recent version of chdman.exe?
  19. @MD-Geist Thanks for letting me know!! Sony PSP ("PlayStation Portable") was not on the list of 'Platform names to fix' (just like Sega Dreamcast wasn't). It has now been added. When updating, added Platforms ("Nintendo Family Computer" etc.) were not being added back into AllGames.xml from Added.xml. Only games that fell under an existing Retro Achievements console/platform ("fixed" or not) were added. This has been fixed which should in-turn fix doubling up game entries in Added.xml (since you won't have to add them again after updating ). I still haven't done anything with TurboGrafx issue. And there's a real strong chance I won't because of how R-Achievements has grouped console variants. But this revision should fix the issue with manually added games for consoles not specifically on the list. This zip ONLY contains one of the files for the plugin. Download, UnBlock, and replace the file in your /Plugins/RetroAchBadge/ folder with the one in the zip. Keep all other files in the folder. Run the Badge Updater from the Tools menu. Since your Added.xml is small, either delete it and start over, or just delete the duplicated games from the xml and save. You could even do nothing, but those duplicates will always be there. It won't hurt anything. Just looks ugly. RetroachievementBadges (v2.1.1).zip
  20. It shouldn't be skipping any games without giving you the popup error message. Since you are seeing the message [on some of them] tells me you have the latest version (v1.02, released Saturday). Which is good. Are the games that are not converting and not showing the error message 'main' games? Or games that are Additional Apps to a main game? And are all these games [and Additional Apps] all pointing to a .cue file in their application path [path to the ROM file]? How it works The plugin looks at each game and its Additional Apps (if any) in your selected Platform, at the games path to the ROM. If the ROM file in that path has a file extension of .cue, it sends it to chdman to convert it (the .bin file(s) that particular .cue file references) to a CHD. After conversion is 'completed' (chdman exits its process), the plugin checks to see if the [created] CHD file exists. If the CHD file doesn't exist, something went wrong with the conversion and you get the [generic] error message. I've only heard of one instance where conversions were failing. The fix was update the version of chdman being used.
  21. It won't modify any existing files other than move or delete (if you select one of those options).
  22. Glad to hear you got it working! Myself, I only have one controller to test with. But with yours, if one fails to load, I wouldn't think it would make them both not work. But I've been wrong many times before. Try making sure you have the controller that's assigned to player one (they won't be interchangeable because of the controller specific ID's) plugged in (give it a sec to fully register) before starting MAME. I assume when you changed the mapdevice to JOYCODE_1 and JOYCODE_2 respectively, all the stick and button reassignments were changed to 1 & 2 as well. Also try to keep where you plug then in relatively consistent. They shouldn't need to be exact, but don't try using them both in a USB hub and then later, just one in a USB port right at the computer.
  23. The error looks like it's in the cue file. Which would also lead me to believe that if you tried to run the game via the cue file, it won't. But it may also be that the older chdman.exe you're using is 'the one with issues'. Maybe try - downloading the latest MAME release and extract it to a temp folder and then attempt the command line test again pointing to the 'new' chdman.exe. If that doesn't work, you may need to try to find different cue files (or different cue/bin roms?).?.?.? I just uploaded an updated cue2chd v1.02 that will now (actually) catch the error 'the chd file was not created'. It will also not move the files if/when this error is reached. It still won't tell you why something messed up, but you'll at least know something went wrong.
×
×
  • Create New...