Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: Noelix on August 25, 2016, 05:08:00 pm
-
Hi all, I tried to find an answer on the board but came up short. If it's already been answered I apologize!
I'm running a Windows 7 build loading directly into Maximus Arcade. I have two wired XBOX 360 controllers that I treat as Player 1 and Player 2. The PC I'm using is completely dedicated to gaming for this, and I leave the controllers plugged in at all times. What I can't seem to figure out is why, at Windows boot, the two USB ports I'm using for the controllers get assigned to either Player 1 or Player 2 at random. The ports are not consistently assigned Player 1 or Player 2 roles. Is there any way to lock down which device boots up before the other (and therefore lock down which one is P1, and which one is P2)?
ASRock E350M1 AMD E-350 APU (1.6GHz, Dual-Core) AMD A50M Hudson M1 Mini ITX Motherboard/CPU Combo http://www.newegg.com/Product/Product.aspx?Item=N82E16813157228 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813157228)
Seagate Solid State Hybrid ST500LM000 500GB 64MB Cache 2.5" SATA 6.0Gb/s Laptop Thin Hard Drive -Bare Drive - OEM
Kingston HyperX 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model KHX1600C9D3K2/8GX
-
Strange. My controls are wired to hacked fight pads and I have no such issues. It's my understanding that software that detects them as xinput (xbox360 controller support) go by some type of internal ID than never changes. Older software that only uses dinput (standard gamepad) go by the order they were plugged in (as assigned by windows).
I had to figure out which one was first under xinput, the replug them in that order so that dinput was the same.
My cab is still running vista though, so could be a Windows 7 thing.
If you're using a hub, that can screw things up.
-
It's either setting P1 or P2 at the bios level or at Windows boot. My gut tells me Windows boot. The lights around the Xbox "X" logo flash until Windows boots and then will lock on to the P1, P2 light indicators (one on each controller randomly assigned). This is before Maximus Arcade fires up or any emulators. I'm not using a hub but I am running a cable from the motherboard connectors to the front of the case, same as you would in any standard case.
-
I'm not sure if this will help but you may check out drventure's controller remap utility: http://forum.arcadecontrols.com/index.php/topic,108767.0.html (http://forum.arcadecontrols.com/index.php/topic,108767.0.html)
-
I'm not sure if this will help but you may check out drventure's controller remap utility: http://forum.arcadecontrols.com/index.php/topic,108767.0.html (http://forum.arcadecontrols.com/index.php/topic,108767.0.html)
Unfortunately no, that's only a workaround for MAME. I'm surprised I'm the first person to have had this issue honestly. For everyone else it just "works"?
-
Are they genuine Microsoft controllers?
I've got some generic Wii controllers that will blue screen windows when I pair the second one because they both have the same internal ID # (because they are THAT generic).
If they are 3rd party, there could be something similar at play.
From some googling: Mazza1 1 point 1 year ago
To change it to player 2 I unplugged it and plugged it back in while holding the home button. This works to change the player number but only changes it to player 2/3/4 but skips 1
So maybe try that with the one you want to be player 2 and see if it sticks after rebooting. :-\