Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Retro808

  1. Just edit a game and see. Right click a game and edit. Check the path there and check to make sure it is using the correct emulator. Also go to >Tools>Manage Emulators and confirm the emulator of choice is pointed to the correct path just to be sure.
  2. 1st and always most important question: Do your games work directly in Retroarch (without Launchbox)? If they do then we know the disconnect is in Launchbox somewhere.
  3. Drag and Drop still works. Just do not select the option to import as Rom. Use the "None of the Above" option.
  4. Works fine. Make sure you set a key for Channel Select and Enter in the game controls. Those are needed to select and start games in Playchoice-10 roms.
  5. Make sure you have the box checked for "Use file name only..." in the details tab of the edit emulator screen for Final Burn Alpha setup in Launchbox. Just tested removing that check and it gives that error you mentioned.
  6. There have been a few threads about this. Are you on Windows 7 or 10? A couple things could be the issue. Users have either needed a .Net Framework update (Win 7 mostly) and others have seen 3rd party software such as antivirus or things like Riva Tuner/MSI Afterburner causing issue with Launchbox not opening.
  7. @Geminii23 Yeah, I would recommend not piecemeal roms. Will it work? Yes. Can it cause more issues than needed? Yes. You can easily find yourself hunting down random file after random file and nowadays getting roms from random sites means easily getting something in a file you may not want. Just look at the fact that trying to update you already are having issue. PD and the Archive work well. PD requires you to sign up and maintain a good upload-to-download ratio, but the good thing is the Mame sets usually do not count against it. Archive is just download and go. Recommendation get a full set and be done with hunting and searching.
  8. We cannot link to sites but can recommend places like Pleasure Dome (there are some rules you need to follow to download from their site) and the Archive contains relatively new romsets. It is best to use a romset that matches the mame version, but as long as they are close you will typically be ok. I am using .209 romset with the current Mame version.
  9. Newer Mame version will need the updated qsound file which contains that file. It is qsound_hle.zip. If you have a new full romset that file should be in there. If you are using roms pieced together than that would be your biggest issue.
  10. Make sure the logos are named exactly as the PS1 and PS2 platforms are named in your Launchbox platform list and that they are located in the correct folder. Example: (If you named it Sony Playstation2) Folder and file name would be: \Launchbox\Images\Platforms\Sony Playstation 2\Clear Logo\Sony Playstation 2.png If those are correct and images still do not show. Go into BigBox and in the settings menu go to Options>Image Cache and then choose Refresh All Images. Your image cache may just need updating.
  11. Edited: Looks like Neil has you covered on RA. Doubt it is a bug. It works fine on all my cabinets with RA FBA core. Nothing changed in 10.1 that should have broke the emulator. Even in the standalone FBA it works fine still. These are the same settings from last year I had that.
  12. Always test your games first directly in the emulator before you import anything into Launchbox. That way you eliminate it either being a rom issue or an emulator one. Even if you are using an older romset and older emulator version it can still work in Launchbox. Using updated versions is always best. The roms you have now do they run directly in the emulator you are using? For Launchbox you have to make sure the emulator is setup correctly and the games run in them. Launchbox does not do any of that.
  13. You downloaded Mame Rom's but didnt work.....Did not work how? In Launchbox? In Mame? You have to be a bit more specific than this.
  14. This has happened before and I believe Jason fixed. So looks like it is not working again. We will let him know.
  15. I have not added to FBA but have added to many other platforms without issue. Did you check the path to confirm it is correct? Do the roms run ok directly in the emulator?
  16. Easy to do just replace "SelectedGame.Rating" with "SelectedGame.StarRating" in line 131 of the Default.xaml. Also update line 125 to read "Star Rating:" if you want. Or just drop this Default.xaml in the theme folder. This one has those lines changed if you don't want to mess with it.
  17. What resolution and DPI scaling are you using? @BBG Try the new version I just loaded. Small fix to text code I hope will fix the issue. Still let me know the information above.
  18. .208 should not have had a problem with that code. It would have been an issue for a version way older than that (I think version below .175 or something like that). I still have .206 running on a machine with no issue. I do not use RocketLauncher so that might be something to consider. So there may be a different conflict with Rocket Launcher. That command line allows the new Pause screen options to work. Without it the Pause screen still shows, the options just do not work (save state, load state, etc...).
  19. What version is your Mame? If it is an old version the "-keyboardprovider dinput" command line would be the issue. Edit: Looks like Jason has you covered.
  20. In the edit emulator screen in Launchbox what tab do you have the AHK script in?
  21. Do you have your Mame setup in Launchbox in a way you can also run it without Rocket Launcher to rule out some type of conflict with RL? What other types of software run in this cabinet while Launchbox/BigBox runs?
  22. Well if you were on a version before 9.2 then one thing that will cause issues with Rocketlauncher are the new Startup screens that were implemented in 9.2. Startups within Launchbox and Startups from Rocket Launcher will not work together. You will have to turn off one of them. Not saying that is what is causing this issue, just letting you know it is something known to not work together. There has been a recent Windows 10 update that mixed with things like Riva Tuner/MSI Afterburner and even virus protection like Kaspersky has caused issues with the recent Launchbox updates. If you are using any of those turn them off and test some games. Are you on Win7 or Win10? I do not use RL so cannot really comment much more on troubleshooting with it. Just giving some heads up on issues we have recently seen.
  23. Yeah Riva Tuner has been know for quite a while now to cause issues every now and then. We will usually recommend adding an exception to it for Launchbox and BigBox exe's.
  24. Do you have the keyboard or controller automation buttons/keys mapped in Launchbox for what you want to hit to exit a game? What tab do you have the AHK script in? The running tab is where is primarily goes. That is the AHK that will always be available while in an emulator. The Exit tab is for exiting a game while you are in the Pause Menu. So you can have it in both. I would change the script though to the one below. The original is a hard closing of the emulator. The one below will shut it down properly and not risk losing a save state. $Esc:: { WinClose, ahk_exe pcsx2.exe }
  • Create New...