ark1320 Posted January 26, 2023 Report Posted January 26, 2023 Hi John, In the past I've always used a single throttle axis to control both engines of an aircraft. I now am trying to assign a separate axis to each engine of the C414, and in this case the throttles do not have a reverse range. The assignments are profile specific. The calibration looks like this: and the entry in the FSUJIPC.ini file under the profile specific JoystickCalibration section looks like this: Throttle1=-16380,-512,512,16380/32 Throttle2=-16384,-512,512,16209/32 Does this look correct? If so, I don't understand why when a throttle is all the way back, there is 0 OUT for -16384 IN. Is that just the consequence of No reverse zone? And where did the +-512 come from in the ini file entries? I expected the FSUIPC7.ini entry to look similar to what I get when I use a single axis for both engines, e.g. I expected Throttle1=-16384,16383 and Throttle2=-16384,16383 . However, this dual axis setup does seem to work as far as the operation of the throttles in the sim is concerned! So it seems there is something fundamental I don't understand. Thanks, Al
John Dowson Posted January 26, 2023 Report Posted January 26, 2023 2 hours ago, ark1320 said: the entry in the FSUJIPC.ini file under the profile specific JoystickCalibration section looks like this: Throttle1=-16380,-512,512,16380/32 Throttle2=-16384,-512,512,16209/32 Does this look correct? Yes. 2 hours ago, ark1320 said: If so, I don't understand why when a throttle is all the way back, there is 0 OUT for -16384 IN. Is that just the consequence of No reverse zone? It is a consequence of the throttle axis that you have assigned to, which accepts that value range. This is what calibration does - calibrates your devices axis range to that accepted by the axis you have assigned to: 2 hours ago, ark1320 said: However, this dual axis setup does seem to work as far as the operation of the throttles in the sim is concerned! So it seems there is something fundamental I don't understand. So what is your 'axis calibration issue' then? If it is just a question, please say that it is a question in the topic title, not issue. I wouldn't worry about this. I don't fully understand all aspects of the calibration, and a lot of the stuff is there for historic purposes and for support of older controls, some of which probably aren't that relevant to MSFS. John
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now