darrenmarchand

I've abandoned the joytokey solution. Started having issues. I'm back to trying to figure out what the issue is with Mame.

I think it needs to be programmed in to Joytokey, but I'm not sure as what.

I I'll double check when I get home, but I'm pretty sure it is set to mouse already. I think it had to be anyway when everything was working before in Mame. Thanks.

My issue is that I'm having a strange problem with Mame. Everything was working until I unplugged my computer to move it. I fully expected Windows to change my controller IDs and I'd have to set them in Mame again, however, when I tried to program any controls, it automatically populates every button on my arcade box for some weird reason and doesn't allow for any input. I think you actually responded when I first posted this back at the beginning of Sept. Anyway, that's why I had the idea to use Joytokey. I think it works like 99% well, but I can't get the spinner to function.

Hi, So I'm using Joytokey for Mame for reasons I won't explain here. Anyway, I can't figure out how to get the spinner to work. If I go into a Mame game that has Dial controls, it won't respond. The trackball does though. Shouldn't the mouse, spinner and trackball all be tied in? Mame sees a couple buttons as X and Z on the keyboard, but I noticed that increase and decrease under Dial controls are also X and Z. If I hit the buttons on my arcade box that relate to X and Z in Joytokey, they will act as Dial increase and decrease. Please keep in mind that I cannot change any controls within Mame because I'm having a different issue, which is why I resorted to Joytokey.

Hi. Any chance you figured out how to program in a spinner, like for Tron? My tracball works for it but not the spinner. i can't see where in joytokey it would go.

Well, it's happening again. The 2 unknown devices were there again, so I uninstalled them. The Mame problem persists. The 3 keyboards showed up again, I tried deleting 2 except this time, it did not solve the issue in mame. I have no idea what's going on. There's something Mame does not like with Windows 11, and I can't figure it out.

I sort of figured it out! It's working properly now and it was 1 of 2 things. I checked device manager and there were 2 unknown devices, so I disabled them. Also, there were 3 keyboards showing, so I disabled the 2 that I didn't recognize. Voila! I can program my controllers again. Not sure which one was the issue and I'm not going to mess around with it.

UPDATE - I have 3 joysticks. 2 generic and 1 Tron. Without doing any configuration, Mame is using the Tron stick and buttons (for some strange reason). If I unplug Tron, launch a game and hit Tab, the menu just keeps flickering and I can't get into it! So what the hell?

Hi guys, I have a homemade arcade stick setup with 3 joysticks and multiple buttons. Things were working fine but recently I had to move the computer and I powered off the usb hub that the controllers were plugged into. I was using the "read only" method in the .cfg folder so Mame remembered my controller setup. When I booted up and tried launching Mame, it crashed and I discovered that something in the .cfg folder was now causing the crash (so, something happened when I unplugged powered off the hub for the arcade stick). I deleted the folder and tried creating a new .cfg by launching a game and setting up the controls, but now I get this (see photo). As you can see, when I try to assign a joystick movement, it populates with a TON of buttons and won't let me enter any controllers. I had this problem once before and (stupid me) I didn't write down the solution. Please HELP! Fyi, the sticks and buttons are all detected in Windows 11, I'm getting no errors for the USB controllers in Device Manager and this was working just prior to shutting off the usb hub. A couple notes: -if i unplug my arcade box from the usb and try to launch mame, I get constant flickering and the menus jump -if I try to use my previous default.cfg from when everything was working, Mame crashes -I've tried using a different usb port and I get the same problem -I've tried a fresh install of Mame - same problem

Hi guys, I have a homemade arcade stick setup with 3 joysticks and multiple buttons. Things were working fine but recently I had to move the computer and I powered off the usb hub that the controllers were plugged into. I was using the "read only" method in the .cfg folder so Mame remembered my controller setup. When I booted up and tried launching Mame, it crashed and I discovered that something in the .cfg folder was now causing the crash (so, something happened when I unplugged powered off the hub for the arcade stick). I deleted the folder and tried creating a new .cfg by launching a game and setting up the controls, but now I get this (see photo). As you can see, when I try to assign a joystick movement, it populates with a TON of other buttons/controllers and won't let me enter any controllers. I had this problem once before and (stupid me) I didn't write down the solution. Please HELP! Fyi, the sticks and buttons are all detected in Windows 11, I'm getting no errors for the USB controllers in Device Manager and this was working just prior to shutting off the usb hub.

Looks like it's only the .hdf roms that are the problem. The .dim and .hdm seem to load properly. Really weird. Guess I'll be replacing some roms.

Has anyone solved this? It's happening for me with the Sharp X68000 games (retroarch). It keeps loading the last (Sharp) game I actually played when I click on any new one. Seems to only be the Sharp and no other platform. I even deleted the platform and rescanned. Even if I go to a different platform, play a game and come back to Sharp, it still loads the last Sharp game i played.

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.

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.