I am completing a new FSX build & have encountered a strange problem with the Saitek yoke. OS is Win 7 64 bit professional & I have updated to the latest 64 bit drivers from the Saitek site. I use FSUIPC4 and had tuned the axis controls to work very well with GA planes in FSX. Using FSUIPC4 I was very happy with how precise I could set the yoke to be very sensitive. My yoke is plugged into a powered USB hub. The problem I had was often when starting the computer the yoke would not initialize at all unless I unplugged & re-plugged the yoke into the hub. But it worked just fine.
To solve the startup issue, I plugged the yoke directly into the computer USB port. This lost the FSUIPC4 settings & I had to set that up again. Then I noticed that I was seeing a "dead zone" between the 11 & 12 o'clock position on the aileron axis. After searching the forums, I found a suggestion from Saitek that a certain registry entry needed to be deleted and the yoke re-calibrated. This made the dead zone go away, UNTIL FSX was run a second time. This behavior is also confirmed in the driver calibration screen, the dead zone can be clearly seen on the Saitek calibration screen.
Plugging the yoke back into the USB hub seems to fix the dead zone problem.
In talking with Saitek tech support, they are convinced that this is a hardware malfunction that needs repaired. But to me this sounds like software.
Has anyone else encountered anything like this?