I haven't been able to find any information on this...

 

I am using a CH Products pro Throttle and the when configured, it, of course, controls the throttle position... and takes precedence over any other form of throttle control including the default FSX keyboard throttle commands F1, F2, F3 and F4... pressing those keys will cause a momentary jitter in the throttle lever in the VC, but it appears that the CH Throttle is being read in real time and will always snap back to where ever it is set even when you hold down the keys on the keyboard...

 

THe trouble this is causing me is that on planes like the JS4100, you can't start the engines with FS2Crew unless the throttles are in a position that you can ONLY put them in using the keyboard controls (It is a position aft of the lowest setting with the CH controller) and it will not stay in that position because of it being overriden where it detects the CH Throttle is set....

 

Have I misconfigured the controller? I get the impression that people with throttle levers are still able to control the throttles with their keyboards for things like reverse thrust, etc...

 

Thanks for help in advance!

This topic looks like it should be in the Turboprop forum.

 

I have the CH throttles and have them set so when I pull them all the way back it triggers F2 and moves the throttles into reverse. Im assuming your trying to get the prop locks (i cant remember the right name) disengaged here. You can also move the throttles back by grabbing them with the mouse. I do that on shutdown.

This topic looks like it should be in the Turboprop forum.

 

I have the CH throttles and have them set so when I pull them all the way back it triggers F2 and moves the throttles into reverse. Im assuming your trying to get the prop locks (i cant remember the right name) disengaged here. You can also move the throttles back by grabbing them with the mouse. I do that on shutdown.

 

Hi Tom!

 

I solved my problem! I just bought and registered FSUIPC and the throttle filtering and calibration took care of everything! :)

 

It turns out that what was happening is that the throttle sends spurious input that I think is "noise"... if you use the keyboard and everything is working well with no noise the keyboard commands override the throttle lever input... but everytime the throttle sent "noise" it moved the VC throttles a little and so the computer thought I was trying to do a throttle lever input from the CH Throttle and broke out of keyboard setting...

 

Once the noise was squelched, the throttle lever no longer prematurely aborted the keystrokes and now everything works PERFECTLY! Thank you FSUIPC! :)