Jump to content
LaunchBox Community Forums

ckp

Members
  • Posts

    1,686
  • Joined

  • Last visited

Posts posted by ckp

  1. Do you have PCSX2 emulator added to LB? Is it named "PCSX2"?

    Or maybe you changed something, like the path to your PCSX2 emulator? If you open your Sony Playstation 2.xml file, you will see the path that  is expected, to find pcsx2 inis folder, as well as pcsx2.exe, for games you have had the pcsx2 plugin set custom game configs for. 

  2. you can rename to anything, like prepend __ to the first part of the file name. 

    then when you launch it will start with default settings and it will create those files new. your games will still be there. worse case is you go into the options menu and change the settings how you like and hopefully don't get the one that causes this. you can always then delete the newly created settings.xml file and rename your back to use it along with the problem.

  3. in your configured (not new install) install, you could try renaming your Launchbox\Data\settings.xml and starting up LB so the setting isnt there. Or rename  bigboxsettings.xml if BB is the problem. make sure LB/BB are closed before renaming the xml file.

  4. looks like a bug to me. maybe you can try the last release before 8.0? unless @Jason Carr can give you something to try to stop the crash.

    i'm guessing if you did a brand new 8.0 install to a new folder, you might not get that problem, at least not until you do whatever it is that is causing it.

  5. i've also only seen that problem in RA mame. maybe they can help you on the RA forums or discord? when i asked them about it a while back, they were not helpful, but maybe i just got unlucky. i ran into a couple other issues too using RA mame that were no issue in stand alone.

    i think you're better off just using stand alone mame, but i do understand your motivation to just use RA.

  6. just as a test, does it work well on your AMD laptop if you install a brand new clean LB on the internal drive and import a couple platforms and wait for it to finish caching images?

    then again, maybe AMD 2.4Ghz isn't enough, but I honestly don't know on that one.

  7. I tried netplay in the latest Beta. First problem was I had a netplay password set for my RA, so the LB netplay wasn't working because it just uses a blank password I guess and has no option to use a password. So, I had to clear my RA password to get it to work with LB.

    Other thing I would mention is that it might be nice if LB kept a history (drop list?) of who you joined to, so it's easier to reconnect to people, especially when they use IPs instead of dns names for their netplay hosting.

    My initial thought was that there would be some place I could see active netplay hosts and just choose one. Maybe in the future.

    So, all in all it worked and made things easier, but there still existed all the horrors of RA netplay like have the exact everything everywhere and proper network/firewall settings on both sides for things to work. Not at all LB fault.

  8. some of the larger seagates beat western digital in reliability as shown by Backblaze drive comparison statistic you can google on. the models you get matters. i have several seagates and haven't had any issues.

    7200rpm is always better, but may not be worth the extra price tag for usb drive emulation stuff. the 7200 gives you a faster seek time, so even over usb it will be a good step up over 5400.  that said, LB with roms, media, and emulators all running from my external usb 3 5400 drive runs very well.

  9. I didn't realize your performance issues were only with the MAME platform. Something must really be causing LB/BB issues there then. Just removing and reimporting the games won't help if it's at all related to any of you custom metadata and/or image files.

    As a test you might trying simply installing LB to a brand new folder and importing MAME to it "normally". If that doesn't cause any performance issues, and I don't think it will, then at least you have an option.

    Also, leaving LB run overnight doesn't help it cache. It only caches when scrolling through the games, and a little time after, but not hours.

  10. From what I've found, you need to delete all but one box art of the same kind if you want to force just one specific one to show. I think it's supposed to show the art with highest region priority so maybe that is another way to deal with it. For me, I just make sure I have only one front box for each game.

  11. I didn't read the entire post, but LB/BB will seem slow when it's caching the image art. In LB you must actually scroll through EVERYTHING manually to get it all cached. For BB there is a setting to force the cache. In both cases it takes time, but once it's done, performance should be fine. Can it auto cache automatically for everything until done -> no it doesn't. Do I wish it would -> yes, i do, but it doesn't. It used to a very long time ago when I first started using LB, but since certain performance improvements were made, you must manually scroll.

    If you want to know if LB is still caching files, you can open up task manager, click the resource monitor, then watch the disk usage WRITES for processes launchbox.exe and bigbox.exe. If it shows it's doing writes to Launchbox\images\cache then it is still caching.

    It can take time to force all the image caching, but once done, I've found things work well.

×
×
  • Create New...