Odd "drift" problem on Pitch axis...

[Knite]

I wouldn't normally post this as a tech support issue, as "drift" can readily be resolved by changing deadband, except... I don't think I'm having an input problem here, but something in the software...

Explanation :
Joystick - Saitek X52.

Game registers all 3 primary axii (yaw, pitch, roll) at (32767) when centered. HOWEVER, the PITCH, even while registering dead center (32767) shows as a "nose up" signal in the advanced settings, as well as when I try to use field guns, so it drifts, and when flying can add a mild "nose bounce". I go back into configuration, and the joystick shows 32767, like expected, but the drift continues. I check the other 2 axis, and I do not get the same issue.

I've added some screenshots to show what I mean visually. I set deadband on all 3 all the way up to show the difference between the "raw" and "scaled" settings. Shouldn't these two lines be directly next to each other for pitch just like for roll and yaw?

[Delirium]

If calibrating in windows and AH doesn't work, you probably have a bad pot. I'm guessing it is more of a calibration issue since the huge dead band you set would remove the off center pot. If you had a CH stick, I would recommend you check the trim wheels on it...

Sorry I can't help you more, Knite.

[SPKmes]

I get this problem at times. I just re-calibrate in AH and it seems to fix it.

[Scratchman]

I too get this drift from time to time, and coincidentally happens when there are a lot of people online at the time, which would make no sense. I have all CH products and a quick recalibration fixes it. However with the X52, I have read in other posts that other users experience this same problem. A solution was offered at the time that other X-52 users said worked for them, so I offer here for you. They suggested that you use a powered USB hub for your devices, that this seemed to alleviate their problems. Hope it works for you, there nothing more frustrating to have this happen while engaged with an eager enemy ready to flame your 6. 

[hyster]

on my X52 the the cables come out slightly causing me problems. the more i move the base of the stick or throttle the more it happens. i got into the habit of pushing them in every flight or when i notice problems.

[Knite]

I appreciate the advice, and I'll give it a try.
I never calibrate in AH as it always seems to make things go goofy (although I suspect that's because I have a habit to not always remember what registers as an "axis" and screw things up that way. haha. I do have a powered hub, as I bought one specifically for my X52 =)

My biggest worry on this problem is, if you look at each axis, they ALL register the exact same measurement with no "potentiometer bounce" at 32767... why would the game interpret 32767 (which would be dead center... as it's 1/2 of 65535) differently for one of the 3 axis?

[SPKmes]

you can calibrate all axis seperately however just >options>controls>calibrate joystick. will do the trick.

Make sure you run through all though. The stick,throttle,rudder. Anything that uses sliders/pots.
ultimately what you are doing in advanced is only affecting the responsiveness of your gear.

another thing I find help full sometimes is to pull the plug on the joystick for a few seconds. It usually sets properly but sometimes I need to calibrate.

[Ratpack1]

The X52 is a hog when it comes to juice. A powered USB Hub will greatly help. You will find tons of posts on this.

[morfiend]

I could be wrong but I beleive the only pot the X52 has is the twist rudder! I understood the other 3 axii{learn something new every day...lol} are controled by HID,which almost never fail.

If it was my stick I'd delete the saitek software and use AHII's map controls to setup my stick!

  BTW I have a 4 year old X52 and the only problem I've ever had was the rudder axis spiking,that was resolved with a set of pedals and locking the twist action.

 

[bustr]

If you have downloaded Saiteks latest drivers and software from the web sight and installed those. You can tell by the new directOutput manger and service that gets installed. Open your MS Media Player and see if their is now a Saitek plugin. If there is a plugin. Disable it. And disable the directoutput service. That will cause axis and button problems like you have described.