Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Issues with 2 Zero Delay encoders - Windows 10  (Read 1348 times)

0 Members and 1 Guest are viewing this topic.

Nickb23

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 7
  • Last login:December 13, 2020, 02:39:21 pm
  • I want to build my own arcade controls!
Issues with 2 Zero Delay encoders - Windows 10
« on: December 13, 2020, 02:39:21 pm »
Hey guys,
I have almost completed my 24" Cabinet running launchbox on a Windows 10 desktop. I have 2 Zero Delay Encoders running standard stick with buttons.
Even though windows calls them the same name, the different emulators see them as separate controllers. I have set what is called Joy1 as player 1, and Joy2 as player 2.
The issue I am having is that after a reboot, Windows flips the controllers around, so that Joy2 is now Player1 and visa versa.

Has anyone had this issue, and any way I can force Joy1 to be player1 and Joy2 to be player2?

Thanks.

meyer980

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 385
  • Last login:March 29, 2024, 04:00:11 pm
  • Building fun things for fun
    • sergiostuff.com/2020/04/15/felix-son-arcade-game/
    • Sergio Stuff
Re: Issues with 2 Zero Delay encoders - Windows 10
« Reply #1 on: December 13, 2020, 09:28:05 pm »
Are your encoders plugged into a USB hub by chance? I know using one can often affect the controller boot order - and if I remember correctly it's less often a problem for USB ports built into the motherboard.

I've seen lots of people post about this problem in other places, too, so I'm guessing there are solutions but a lot of searching only came up with this work-around for MAME: https://www.reddit.com/r/cade/comments/cpzq3x/joystick_assignment_in_windows_10_always_changing/