Jump to content
LaunchBox Community Forums

darrenmarchand

Members
  • Posts

    75
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

darrenmarchand's Achievements

16-Bit Artificial Intelligence

16-Bit Artificial Intelligence (4/7)

3

Reputation

  1. I just started having this issue. My computer was in sleep mode, I didn’t close LaunchBox, my power went out. When I rebooted and tried to open LaunchBox, it went all wonky. The Home Screen kept changing, the mouse starting drifting and a volume bar appeared at the bottom of the screen. I then found that multiple instances of Launhbox kept opening. The only way to get out was to reboot. I’m running 13.21 with windows 11. I checked to make sure no controllers or keyboard buttons were stuck. I launched 2 other instances of LaunchBox without issue. I tried launching a backup. I tried back dating to 13.20. It’s still doing the same thing. I’m stuck.
  2. I started getting this right after I upgraded to 13.21. I installed a theme for the first time and I thought it was that for reason, so I went back to the default theme, but the low ram error came up again.
  3. Figured it out: run (type emulator location) "savestates\BLUS30528\used_BLUS30528_1_0.SAVESTAT"
  4. Hi everyone. I'm trying to launch a savestate in LB from RPCS3. I know I need an ahk script, but I can't seem to figure out how to create one that'll launch the savestate file. Any help?
  5. Oh. I didn't rename default.cfg the first time around. I have default.cfg AND zerodelay_x2 in the ctrl folder. With mame.ini pointing to zerodelay_x2. So I'll rename default.cfg and have mame.ini point to that now.
  6. Oh sorry. I may not have typed that correctly. I meant after changing those 2 lines in zerodelay_x2 , do I copy and paste those changes into default.cfg? For the second part, I don't follow. Yes, I have "core input options ctrlr zerodelay_cfg. Isn't that what I'm supposed to have? Then after setting the controllers in Mame I copy default.cfg to the ctrlr folder. After that, I shouldn't need to make anymore changes to the general controls, right?
  7. Thanks. Do i need to re-copy those 2 lines after making the changes to default.cfg?
  8. just fyi. I did redo the default.cfg and copied it again to the ctrlr folder. i also changed the contoller numbers to 1,2,3,4 as you mentioned earlier. i haven't rebooted the PC or unplugged any contollers again. dmList.txt
  9. So. its messed up again! i shut the PC down and unplugged the usb hub where all the joysticks are connected, and when i booted up and started Mame, it rearranged the sticks and buttons. I had shut the PC down a few days ago and nothing changed then. Is it because i unplugged this time?
  10. i had been doing that too. it won't work. Windows still eventually changes it.
  11. I've tested it with all 4 contollers and it al seems to be working with the settings i have. I may be able to leave it as is. It could mess up when i introduce the wheel, but i guess for now, its functioning properly. I'm going to turn the pc off a couple times to be sure Mame isnt losing the setup. thx for all the help
  12. ok. So it should look like this? I only focused on the joysticks for now. I'll have a look at the steering wheel and see how that works. I'm not sure Windows changes its ID. My gun is a Sinden which acts as a mouse, so i don't think it gets affected. default.cfg
  13. let me know if anything looks wrong. not sure if I missed brackets or quotation marks,etc.
  14. Sorry. Should all 3 joysticks say "joycode 1"? Or is it ok for them to say joycode 1, 2, 3 etc? Or does that matter?
×
×
  • Create New...