-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reoder not Working in MAME #28
Comments
What kind of controller do you have assigned to players 1 and 2? Does it work better if you order the controllers using their GUID instead of their name? (Assuming you're not already using their GUIDs.) |
They are all zero delay encoders which windows labels "generic". I am using the name and the GUID below. Player 3,4,5 are the same controller types with zero delay encoders and they remain in the same order and have been since I installed it. I just can't figure out why it won' work with player 1 and 2. |
You should only use the name or the GUID, not both. What happens if you just use the GUID? |
I just tried that and the results were the same. Player 1 is joy13 (I don't even have that many devices connected) and player 2 is joy14 |
Would you copy / paste your devorder.ini file into a comment here so I can look at it? |
; devreorder settings [order] {ef997f40-6422-11e8-8001-444553540000} ; In this section write the names or GUIDs of your controllers [hidden] ; In this section, write the names or GUIDs of controllers [visible] [ignored processes] |
I had to do a restart and they are now joy1 and 2, but that happens sometimes and after a few launches they change again. Its like the reorder for those 2 won't stick |
Just as I suspected player 1 and 2 have reordered for no reason. The computer has been on, without any restarts and randomly they are now joy 13 and 14. |
MAME will only keep the order on player 3, 4, 5 generic controllers and my other devices are ordered fine. Player 1 and 2 sometimes are 1 and 2 but they change almost every time I launch. Sometimes they are 12, and 13 and other 14 and 15.
The text was updated successfully, but these errors were encountered: