After moving my arcade and once on an windows update, windows reordered my controllers. I’ve used devreorder but I cannot control which of the attachments mgalaxy uses for its menus etc. It decided ‘no joystick’ but is probably selecting my guns ?. If there a way to stipulate them?
Also anyway to slow down the scraper as it’s going so quick it’s maxing out the threads?
Fixing the controllers for mgalaxy
I can't reproduce what you're talking about.Also anyway to slow down the scraper as it’s going so quick it’s maxing out the threads?
In my experience, the only reason the scrape might stop after a few games is if you haven't registered on the screenscraper site...and/or if you haven't entered your login details in Runway!
I think that you might disconnect them all, then start mGalaxy and connect them in the order you want mGalaxy to use them !?After moving my arcade and once on an windows update, windows reordered my controllers. I’ve used devreorder but I cannot control which of the attachments mgalaxy uses for its menus etc. It decided ‘no joystick’ but is probably selecting my guns ?. If there a way to stipulate them?
Thanks for coming back to me. As far as the joysticks are concerned i have two arcade stick, one steering wheel, two light guns and a ps3 controller attached. On reboot today it recognises one arcade stick. the other is no joystick. I think you are right and ill just have to turn the others off, load mgalaxy then switch them on. Was just hoping there was an xml setting which can control it like in mame.
As for screenscraper. I have a free account logged in and large systems dont seem to fall over. However, my C64 collection does.
As for screenscraper. I have a free account logged in and large systems dont seem to fall over. However, my C64 collection does.
That's done and will be present in the next mGalaxy release.
Now you can map all available controllers (whereas before this was limited to the first two.... and could create a problem if Windows decided that the desired controller was in the third position, for example)
Now you can map all available controllers (whereas before this was limited to the first two.... and could create a problem if Windows decided that the desired controller was in the third position, for example)