Jump to content
LaunchBox Community Forums

Lordmonkus

Members
  • Posts

    11,556
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Lordmonkus

  1. Brad has done videos covering updating to newer builds and copying over settings, I just simply start from scratch since it only takes me a few minutes to set everything up again. On my 1.3.6 stable install I simply enabled the per core config and then for each core I setup a shader and it's good to go so I am not sure why that is not working for you.
  2. If you are using the stable 1.3.6 build you should enable "per core configs" but if you are using one of the newer nightly builds you can load a game with the core you want and adjust settings and then in the quick menu core settings you can save the config for that core or even for that specific game if you choose.
  3. Retroarch is a bit more work to get up and running compared to some stand alone emulators but the extra effort is really worth it because it brings some really good features. It's cores are updated much more often than stand alone emulators, has great shaders to customize how your games look and it handles v-sync, audio sync and input lag extremely well and that's just for starters. Anyways here's a link to a guide I did to help get you started with it:
  4. We can't tell you where to get roms unfortunately but the 180 rom set will be just fine. I also highly recommend using Retroarch for the Genesis Plus GX core over Fusion Fusion is a fine emulator but has not been updated in a long time and has issues with Windows 10.
  5. That's strange, it only does this for me the first time I load a game and then doesn't do that after.
  6. You should only have to do it once per game, it's just a limitation of the core itself right now. The stand alone version does not have this if you want to use it but lose out on the Retroarch features.
  7. Hmm, Mame can be particularly annoying but if you are using the same Mame in LB and they work in Mame itself they should work in LB. All I can really say at this moment is double check the actual .zip rom file LB is pointing at and make sure it is the exact same file in MameUI.
  8. Well without knowing exactly what the problem is, check the games that don't work for what emulator they are trying to load with. That would be my first thing to check. Also are the games cd based or cartridge based ?
  9. Very nice tutorial, I added a link to this in the Guides & Tutorials sticky post found here: If you make any more send me a mail with a link and I will add it as well.
  10. Ignore the zip file in the folder.
  11. The approach that Archive.org is taking is pretty much "let's upload everything we can and take it down if asked to" kind of thing. In one of the Jason Scott videos he talks about it and basically only Nintendo and a couple of other companies have bothered to contact him to take anything down.
  12. Yeah ParraLLEl turned into more of a proof of concept than anything and has the most room for future growth. From what I read over on their forums when asked about it the devs said they ran into some roadblocks with it.
  13. It's probably a good idea to do it once you plug your tank stick in since it auto sets it all for you.
  14. Is there no "Default Game Options" in the Options drop down menu ? I haven't used a MameUI build in so long and I forget what it has and doesn't have.
  15. Use notepad++ to edit the Data\Platforms\Arcade.xml file to change the path of your roms. Notepad++ has a find and replace all tool so you would find D:\path\to\roms and replace it with C:\path\to\roms or whatever fits your circumstance.
  16. Look for this section in your mame.ini # # CORE PERFORMANCE OPTIONS # autoframeskip 0 frameskip 0 seconds_to_run 0 throttle 1 sleep 0 speed 1.0 refreshspeed 0 Edit for wrong copy paste job: # # CORE MISC OPTIONS # drc 1 drc_use_c 0 drc_log_uml 0 drc_log_native 0 bios unibios32 cheat 0 skip_gameinfo 1 uifont default ui cabinet ramsize confirm_quit 0 ui_mouse 1 autoboot_command autoboot_delay 0 autoboot_script console 0 plugins 1 plugin noplugin language English
  17. You could even disable that screen in the mame.ini file if you wanted to but yeah that command line parameter will do the same thing.
  18. You could go back to Retroarch if you like and you would not have to remove anything related to Mame in your Launchbox setup. You can just leave it there for easy swapping back and forth if you want to, I have mine set up this way. Though I still prefer stand alone Mame for various reasons but the newer git builds of the Mame 181 core in Retroarch are looking to be fairly decent and much better than the "stable" Mame cores.
  19. That's just the game into screen, that is not the full nag screen disable.
  20. FPS hacks for N64 games generally break the game but it does depend on the game. Ocarina of Time for example is locked at 20 fps and any hacks to make it run at 60 or even 30 breaks the game entirely. As for the ParaLLEl core is concerned, don't even waste your time with it for now, it needs a lot more work to become usable. Try out the GLupeN64 core, I have been having a lot of success with it but you will most likely have to download a nightly build to get it working.
  21. @chewzThere is nothing preventing 3rd party users from developing some sort of app that can be used in / with Launchbox to replicate this Kodi plugin though. Or at least I would think it would be ok.
  22. Yes, Zelda was one that just worked right away with out mucking about.
×
×
  • Create New...