Jump to content
The simFlight Network Forums

CH FIghterstick Y-axis issue


Recommended Posts

Peter, I'm having an odd issue with the elevator axis on my CH Products Fighterstick within FSX. This issue seems related to that of another user who posted this: http://forum.simflight.com/topic/73060-fsuipc-ch-products-or-p3d-problem/

My controller is plugged directly into a USB 2.0 port on my motherboard (no hubs involved) and is calibrated solely via FSUIPC....no other controller software is used. The issue is that in FSX, I'm experiencing sudden, unpredictable and uncommanded deflections of my elevator axis downward, even if I'm pulling the stick back. I've tested this with two different Fightersticks with the same result.

In the FSUIPC interface, when I use the Axis assignments page to designate the Y-axis of the stick, the raw data shows no issue with any uncommanded spikes, just a smooth sequence from one end of the data spectrum to the other. By the way, this is confirmed with CH Products' own Control Manager using its Test/Calibrate app while the stick is in Direct mode (no mapping involved). No issue is detected either way.

But when I use FSUIPC's joystick calibration page, I'm able to calibrate the y-axis (elevators) but in the raw data window, as I move the stick through its full y-axis range, I occasionally see in the raw data window the sudden shift into the high positive value range even when I'm pulling the stick back. Clearly, this accounts for the elevator issues I'm seeing during FSX flight.

Again, I've seen this with two different sticks, and I'm positive there's no axis conflicts or mechanical issues involved. What might account for the discrepancy between FSUIPC's assignment page and calibration page in terms of the raw values being detected from the controller?

Thanks for any insight you might be able to provide.

Link to comment
Share on other sites

My controller is plugged directly into a USB 2.0 port on my motherboard (no hubs involved) and is calibrated solely via FSUIPC....no other controller software is used.

And is it also assigned in FSUIPC, or in FS?

The issue is that in FSX, I'm experiencing sudden, unpredictable and uncommanded deflections of my elevator axis downward, even if I'm pulling the stick back. I've tested this with two different Fightersticks with the same result.

In the FSUIPC interface, when I use the Axis assignments page to designate the Y-axis of the stick, the raw data shows no issue with any uncommanded spikes, just a smooth sequence from one end of the data spectrum to the other. By the way, this is confirmed with CH Products' own Control Manager using its Test/Calibrate app while the stick is in Direct mode (no mapping involved). No issue is detected either way.

All that really does point very strongly to a conflict. Use the FSUIPC logging to see what is happening. Also try without the CH Control Manager. I have read of other conflicts with that -- and only with CH devices, incidentally.

But when I use FSUIPC's joystick calibration page, I'm able to calibrate the y-axis (elevators) but in the raw data window, as I move the stick through its full y-axis range, I occasionally see in the raw data window the sudden shift into the high positive value range even when I'm pulling the stick back. Clearly, this accounts for the elevator issues I'm seeing during FSX flight.

The calibration tab operates on the FS control, not on the raw data, so it would also be subject to any conflicting inputs which may occur.

Again, I've seen this with two different sticks, and I'm positive there's no axis conflicts or mechanical issues involved.

If you add in electrical issues too, I'm afraid I cannot see anything in your report which would possibly suggest anything other than one of those three causes.

If you want further advice please note that I ALWAYS need the actual FSUIPC version number. If you do some logging and want help interpreting it, by all means post it here. Also post the Assignments and Calibrations sections of your FSUIPC4 INI file so I can see which of the many ways of assigning and calibrating you are using. Additionally always conduct basic testing using a default aircraft, not an add-on, so that there's no confusion.

Regards

Pete

Link to comment
Share on other sites

Will do, and thanks, Pete. I'm using FSUIPC4, Version 4.856. All controllers are assigned and calibrated through FSUIPC.

UPDATE: Problem solved by purging Windows calibration data from the Windows registry using the Clear Calibration Utility from this link: http://www.wingmante...are/gadgets.htm

Edited by RudiJG1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.