Forgive me if this has been addressed, but...

Of the joy.button[x] built-ins, only button 0 seems to return 0/1. The rest appear to return 0/something else. I came across this when trying to do switches in a simple joystick testing utility, where case 1 would only work for joy.button[0].

Also, this is negligible, but on my non-analog gamepad, the center position returns -1 instead of 0 for the joy.anologx and joy.analogy built-ins.

One other largely irrelevant question: Does V3 check for joysticks only when it initializes? When I unplug/plug my USB gamepad in when my program is running, the program doesn't notice it's abscence/arrival in terms of the joy.active built-in.

BTW, the joystick testing utility is all done and running smoothly, but I'd appreciate if someone with multiple joysticks could test it for me to make sure it works all cool-like. E-mail me (or just say so here) if you want the packfile for any reason.

Thanks in advance.

The values are whatever directx returns. I don't know offhand what they are.

Verge only checks for joysticks at startup, yes.

As for analog positions returning -1 ... well, they range from -1000 to +1000, and the word analog is key here. Even on digital pads, you should not expect it to return exactly 0 or +- 1000. You should consider 10-15% to be a dead zone in most cases, eg, any value less than abs(100) should be considered 0. I believe the up/left/down/right builtins use a 15% deadzone. But the analog values are raw feeds (just scaled to +- 1000), so its up to the VERGE programmer to use the values appropriately.

Righty, understood.

Quote:Originally posted by mcgrue

I have multiple joysticks installed, btw... two gamepads and a wingman I (sadly) haven't used in years due to a lack of good space flight sims.
The space flight sim: Frontier - First Encounters. Still without equal after nine years and downloadable for free nowadays too. Anyone who's not played it, play it!

It's more about trading, but that's even MORE boring.