Jump to content
LaunchBox Community Forums

Lordmonkus

Members
  • Posts

    11,556
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Lordmonkus

  1. Ok so it's definitely a setting in Retroarch. I would suggest asking on the Retroarch forums.
  2. It's definitely a setting issue, either in Retroarch or your display. What core are you using ?
  3. You may need to enable the mouse in Mame, either in the UI or the mame.ini.
  4. For problematic emulators you can use a AutoHotKey script which gets put in the AHK Script tab of the Edit Emulator window in Launchbox.
  5. You can also save per core configs which will auto load with the core.
  6. Those are playlists which if you want can be removed safely without affecting your actual games in Launchbox. If you want to remove them you can either right click the playlist and delete it or you can close Launchbox, go to the \data\playlists\ folder of your Launchbox folder and deleting them. If you wish to rearrange the playlists you can right click and edit the playlist and then input a "Sort Title" which is the name that Launchbox will use to sort alphabetically.
  7. I don't think there were any real changes from 187 to 188.
  8. Yeah, that's a tough one. I have seen people asking about that over on the RA forums they basically said to download the source code and compile your own.
  9. On a budget choose higher resolution and low input latency. Just keep in mind the "response time" you will see up front when looking at monitors is not "input latency", that is the time for a pixel to go from grey to white and back to grey again. While a low "response time" is good to reduce ghosting it is my no means an indicator of input latency. If you have an AMD graphics card that supports Freesync then you may want to look into them since they aren't as expensive as G-Sync. G-Sync is expensive and while I cannot recommend one to everyone especially if budget is a concern, I can wholeheartedly recommend one if you have the money and willing to spend on one. I have a G-Sync display and it really is a pleasure to game on. I would suggest looking at BenQ gaming monitors though I cannot say for certain how well anything over 60 Hz is going to work with emulation with V-Sync on and those displays typically nowadays being 120+ Hz refresh rates.
  10. Yes, Project 64 does this but you need the bios and tell PJ64 where the bios file is in the options menu.
  11. If you didn't change them they shouldn't have changed. Not sure why Esc is not bringing you back to BigBox unless it's one of the emulators that has troubles with that. If you do have some emulator that has a problem with it you can add an AHK script to your edit emulator window to force it. You can find some AHK scripts for this here:
  12. You can just copy your whole Launchbox folder. If you have your emulators installed into a sub folder of your Launchbox install folder this will be easier. However it is not necessary if just for backup purposes and you copy it back to your systems hard drive as long as your emulators and roms have not changed location.
  13. At minimum you will want a good gaming monitor with low input lag, BenQ makes some great ones. If you like CRT shader effects in your emulator then you will want 1440p or 4K because of the pixel density. It really makes those effects look that much better and scaling up 240p games fit much better with integer scaling for proper pixel geometry. Finally if you are willing and able to drop the money on the higher end G-Sync and Freesync are both very good for emulation. With these monitors you can disable V-Sync which is a source of input lag without having screen tearing. Mame benefits greatly from these display types because it lets your monitor match the refresh rate of the game without affecting the games speed. If you use a normal monitor with main and you enable V-Sync many arcade games will run faster than they were intended. This isn't quite as big of a deal for console games since those were meant to run at 60 Hz anyways but the reduced input lag of V-Sync off still helps though.
  14. Did you change your keyboard binds ? Also it could be possible your BigBox is losing focus which makes it not accept inputs, try click it with the mouse and see that fixes it.
  15. Cool, and if you aren't used to setting up the command line version of Mame I will point you to a guide I wrote up a little while back that should get you up and running with it.
  16. Unfortunately I cannot give you an exact name or provide links due to copyright reasons. I will just say though if you google dome of pleasure you will find a site that has up to date Mame sets freely available. You will however have to register and go through a couple of minor hoops and use torrent.
  17. It's not useless, we just can't have people uploading copyrighted files, that would get Jason into legal issues.
  18. I suggest you try the Retroarch forums then.
  19. But is your associated platform for the system pointing to the core ? You say that it's showing PCE-CD core is opened tells me it's not. Also running stuff through the Mame/Mess core in Retroarch is a supreme pain in the ass.
  20. I am going to make a suggestion right now and while it probably isn't the most appealing at first glance I believe it really is the best in the long run. I would suggest obtaining an up to date rom set and the command line version of Mame to match the set. If that is not an option due to internet bandwidth caps or something I fully understand.
  21. Since you said previously that your rom set was the 152 set you will probably want to use the Mame 2014 core which is based off the 159 build of Mame.
  22. Do you have the core you want to load the roms with in the associated platforms list for that platform ?
  23. Use your real keyboard to go to the buttons you want to map to the controller and press enter on the keyboard, then the button the controller you want to map to it. I had to do that with my X-Arcade Tankstick which is detected as a keyboard.
×
×
  • Create New...