Joystick doesn't respond properly

DasSmiter · Post by **DasSmiter** » Fri Nov 20, 2009 6:53 pm

AFAIK there weren't any changes to the deadzone settings in R5. There were also no js specific changes made.

This is why I believe that it's a problem on your end. Try using the quadratic option (x^2 movement instead of x movement per second on reticule) as this should allow you to have finer control near the deadzone.

Also I believe I read a page once on that stick that said they tend to degrade rather harshly over time, so if you've had it for a long time that may be it.

Adept · Post by **Adept** » Fri Nov 20, 2009 8:02 pm

DasSmiter wrote:QUOTE (DasSmiter @ Nov 20 2009, 08:53 PM) AFAIK there weren't any changes to the deadzone settings in R5. There were also no js specific changes made.

Yo Smiter, R5 added the "smallest" deadzone. For some reason "none" seems to have been dropped in the last minute.

Wasp, at least Logitech Force 3D pro lets me adjust deadzones and sensitivity as I wish. Cheap stick too.

DasSmiter · Post by **DasSmiter** » Sat Nov 21, 2009 8:33 pm

The values weren't changed according to Imago, so that's what I'm working from

The none option crashes the game (a deadzone of 0 kills it) so the "smallest" setting replaced it by setting the deadzone at .04

I'm fairly certain that the small deadzone setting = the old normal, although once again I haven't looked at the numbers.

Any word on the issue wasp?

Broodwich · Post by **Broodwich** » Sat Nov 21, 2009 9:11 pm

try turning vsync off if it is on, before you mentioned it felt different, not that your response lagged. I had the same prob and me and imago resolved it by doing this.

Wasp · Post by **Wasp** » Sun Nov 22, 2009 1:04 pm

I'll try your suggestion Brood.

I spoke with Storm and his X52 (which he uses with the 3D Pro) no longer works at all after R5, so he's unable to verify what I'm experiencing. Firestorm also reports his X52 is down.

I'm curious if this is a directx thing or a R5 thing or as brood is leaning to; a graphics related anomaly.

Considering the amount of feedback coming into the helpline, I can only assume it's R5 and/or DirectX.

Update:

No go on the V-Sync idea. Still get the same results only with tearing

Imago, can you confirm that there weren't changes to the input code and that the deadzones are unchanged? I don't want to spend too much time chasing my own tail around.

Imago · Post by **Imago** » Mon Nov 23, 2009 11:04 am

QUOTE confirm that there weren't changes to the input code and that the deadzones are unchanged[/quote]
I can't. Both were changed: DirectInput interface was upgraded to version 8 and a "Small" deadzone was added.

Wasp · Post by **Wasp** » Mon Nov 23, 2009 1:01 pm

Will this be fixed?