2010-09-25, 22:19
grumbel Wrote:It works like this:
1) Xbox360 Wireless Receiver has four data outputs
2) Syncing the controller connects you to the output
3) xboxdrv --wid N connects to the N's data output
4) the first xboxdrv you start will create /dev/input/js0, the second js1, etc.
5) zsnes will use /dev/input/js0, js1, etc. in that order (I assume, haven't checked)
This basically boils down to:
* do not manually set the led with -l N, instead use "sleep 1" between xboxdrv starts and make sure that the proper Led lights up for the proper /dev/input/jsN device
* figure out what happens at 2), no idea if they get assigned to the next free data output or if they get tied to a specific data outputs when syncing, if its the first, switch them on in the correct order, if its the later, use the "sleep 1" thing
Grumbel,
I tried this on my end but I think I'm screwing it up (as a refresher, I am very green on linux) because only controller 1 works afterward. Do you mind helping me modify my current sh file? Here's what I have:
Code:
./xboxdrv-linux-0.4.8 --wid 0 -s -l 2 --dpad-as-button --deadzone 12000 --trigger-as-zaxis &
./xboxdrv-linux-0.4.8 --wid 1 -s -l 3 --dpad-as-button --deadzone 12000 --trigger-as-zaxis &
./xboxdrv-linux-0.4.8 --wid 2 -s -l 4 --dpad-as-button --deadzone 12000 --trigger-as-zaxis &
./xboxdrv-linux-0.4.8 --wid 3 -s -l 5 --dpad-as-button --deadzone 12000 --trigger-as-zaxis &