I forgot I'd left the diagnostics turned back on for that version. *grin* Good thing, though.
Not 0-15? Weeeirrrd. 0/1 is probably the left stick; the right stick seems to vary a lot between controllers - on my Logitech Dual Action it's 2/3, on my XBox360 controller it's 5/4. The Logitech does similar d-pad nonsense on axis 9, while the XB360's d-pad shows up as buttons. (I don't show the buttons in this, but I had another joystick tester that did.)
Are you seeing the instructional text at the top of the joystick config screen? It should be saying 'Circle the movement joystick a few times, then release it and hit button 0', then a similar message for the aiming stick, then tell you to test the display and use button 2 to accept, button 3 to try again.
Could be some video display issues between my laptop screen and your machine, in other words. I should probably just publish windowed builds until I get that abstracted as well.
Re: Crash trace
Date: 2006-11-02 06:00 am (UTC)Not 0-15? Weeeirrrd. 0/1 is probably the left stick; the right stick seems to vary a lot between controllers - on my Logitech Dual Action it's 2/3, on my XBox360 controller it's 5/4. The Logitech does similar d-pad nonsense on axis 9, while the XB360's d-pad shows up as buttons. (I don't show the buttons in this, but I had another joystick tester that did.)
Are you seeing the instructional text at the top of the joystick config screen? It should be saying 'Circle the movement joystick a few times, then release it and hit button 0', then a similar message for the aiming stick, then tell you to test the display and use button 2 to accept, button 3 to try again.
Could be some video display issues between my laptop screen and your machine, in other words. I should probably just publish windowed builds until I get that abstracted as well.