Jump to content
LaunchBox Community Forums

neil9000

Members
  • Posts

    12,647
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by neil9000

  1. neil9000

    LB controller

    Launchbox is designed for mouse and keyboard use, Bigbox is the controller interface. Launchbox i think does support controllers in the free version, but as i said its it no way designed for that. The controllers need to be setup in every different emulator you use, Launchbox has no control over that.
  2. neil9000

    LB controller

    Launchbox or Bigbox? As for using it with retroarch, people use what they like.
  3. Correct, i would also advise that you copy your Launchbox/Data folder somewhere else first, just in case. You can just copy it back after if anything goes wrong. However i have updated my MAME set every month since the new full set importer was added and i just run the importer again.
  4. It should be as simple as going to tools/import/full mame set importer, and following the wizard, it will ask for your mame rom folder location. Uncheck all the media downloads also as you will already have 99% of it.
  5. @Mr. RetroLust You will need to show both, like this.
  6. Meh, the arcades round here were shit until street fighter 2 came out.
  7. OK good to know, i saw the igame and plugin reference so jumped there.
  8. Ah, fair enough then, i have little experience with it as i found controller companion to be so much more user friendly, but i also dont use dosbox so this specific issue has never arisen for me personally.
  9. OK ill tag @Jason Carr here and see if it makes any sense to him.
  10. You can do the same with controller companion also. I think the issue he is having is he wants specific controller profiles for different dosbox games, but these programs just see the dosbox.exe, so he cant have different ones for different games in dosbox.
  11. Yes, but if its still the same emulator entry as your dreamcast then that will no longer work, they need to be separate entrys like i showed in my images.
  12. You can not have the same demul instance for dreamcast and arcade as they need slightly different settings in launchbox. Just create a second demul emulator pointing to the same .exe. This is my DC. And this is my Arcade.
  13. The thing with MAME is that you dont really want vsync on at all. A lot of arcade games run at some weird framerates, you will often see framerates like 55, 58, even 61, 62 etc. The point is there was no standard and as they were on CRT's it didnt really matter what the exact framerate was as they still worked fine on a CRT. The issue now is we are all using flatscreens which have specific framerates like 24, 30, 60 etc and anything that deviates from those will tear. The problem is though if you turn vsync on those games will lock to a 60 refresh and if say a game originally ran at 55 it will be sped up to 60 to match the refresh of the screen, so some games will run faster than they should which obviously isnt correct. I personally leave vsync off and let the games tear if they need to in order to keep the original game speed correct. Hope that helps somewhat.
  14. This does sometimes happen with a new release. We run the .exe through various online antivirus databases in order to keep things like this to a minimum though. Until the update has been installed onto systems and is known to be safe though we cant do anything about over zealous antivirus solutions. I personally just use the windows defender built in AV and i have never had that delete a Launchbox.exe.
  15. The fade has separate settings in both Bigbox and Launchbox, are you adjusting it in one but then launching from the other maybe?
  16. The official 9.2 is now out, download it from here. https://www.launchbox-app.com/download
  17. That error looks like a directx issue as it is referencing d3d9.dll, i would try repairing directx. https://www.microsoft.com/en-us/download/details.aspx?id=35 Also if you look in your Launchbox/Updates folder you should have the old installers, just install one directly over the top of your current install. I would try the directx first though as i think that is the issue here.
  18. If you do not have the option to unblock then it already is. Usually if you unzip themes with 7zip it automatically unblocks the .dll's.
  19. Yeah as @Suhrvivor said thats down to your image priority settings in Launchbox. These startup themes are meant to be used instead of RocketLauncher, not along side it. That will cause conflicts. Make sure you have fanart selected in the Background priority settings, and also that you do not have Fade set to 100% as that will result in a black screen also.
  20. I'm also dumb as a bag of bricks, but even I noticed words and terms in the xaml, so very very slightly edited the default and released my own.
  21. All themes can be edited in xaml.
  22. The latest version is around 280mb, you are not adding all the versions together are you? And there are no videos included.
×
×
  • Create New...