Hi folks, just in the process of getting my setup the way I want it. I very much like using my Nexus 4 as a poor man's EDTracker!
I've inherited a Microsoft Sidewinder Force Feedback 2 (last used for several playthroughs of Freespace 1/2 - good times), but now that I'm paying more attention to these things, I'm noticing a small but still quite significant deadzone in the stick in the pitch axis (up/down). These things use optical sensors, so I figured that in theory there should be no deadzone at all. However, I did manage to find someone suggesting that this is firmware-encoded (sorry, can't post links yet).
I'm running Windows 8.1x64, so the MS Sidewinder utility software obviously doesn't work anymore, and you only get access to basic settings in Windows. simFFB doesn't seem to offer much in the way of control there. It seems that some people claim there is zero deadzone in *their* MSSWFFB2, so I'm now starting to wonder if this is an age/batch thing - mine is the "old" grey-triggered model, not the newer one with a red trigger, so I wonder if that has anything to do with it. The roll axis (left/right) has a deadzone small enough that it doesn't matter, but rather curiously nose down (forward) has a larger deadzone than nose up (back). The deadzone almost coincides with the region where obvious force-feedback auto-centering does not function, but not quite. I suspect part of the asymmetry is due to the way the joystick is centered without the force feedback. If you compare this to the power cord unplugged though, the motors are definitely doing something in the middle, but it is definitely very subtle. I wonder if its possible to tweak something internally to adjust this, but my google-fu fails me.
All the deadzones in ED are set to 0. Its not huge, but it is making me consistently overcompensate when trying to make small corrections in dogfights. I haven't touched any of the joystick settings in ED yet - any suggestions on the best place to start to try to work around this issue? Does the T16000m have less of a deadzone? Do I even want zero deadzone?
Thanks!
I've inherited a Microsoft Sidewinder Force Feedback 2 (last used for several playthroughs of Freespace 1/2 - good times), but now that I'm paying more attention to these things, I'm noticing a small but still quite significant deadzone in the stick in the pitch axis (up/down). These things use optical sensors, so I figured that in theory there should be no deadzone at all. However, I did manage to find someone suggesting that this is firmware-encoded (sorry, can't post links yet).
I'm running Windows 8.1x64, so the MS Sidewinder utility software obviously doesn't work anymore, and you only get access to basic settings in Windows. simFFB doesn't seem to offer much in the way of control there. It seems that some people claim there is zero deadzone in *their* MSSWFFB2, so I'm now starting to wonder if this is an age/batch thing - mine is the "old" grey-triggered model, not the newer one with a red trigger, so I wonder if that has anything to do with it. The roll axis (left/right) has a deadzone small enough that it doesn't matter, but rather curiously nose down (forward) has a larger deadzone than nose up (back). The deadzone almost coincides with the region where obvious force-feedback auto-centering does not function, but not quite. I suspect part of the asymmetry is due to the way the joystick is centered without the force feedback. If you compare this to the power cord unplugged though, the motors are definitely doing something in the middle, but it is definitely very subtle. I wonder if its possible to tweak something internally to adjust this, but my google-fu fails me.
All the deadzones in ED are set to 0. Its not huge, but it is making me consistently overcompensate when trying to make small corrections in dogfights. I haven't touched any of the joystick settings in ED yet - any suggestions on the best place to start to try to work around this issue? Does the T16000m have less of a deadzone? Do I even want zero deadzone?
Thanks!