These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
[Solved] Send to FS as Normal Axis Questions
For a profile specific single engine prop aircraft I want to send the Throttle, Prop, and Mixture axes to FS2024 using "Send to FS as Normal Axis".
1. When I do this, under the axes assignment drop down, I no longer see "simple" options such as throttle, prop and mixture like I do when using "Send Direct to FSUIPC Calibration". But rather I see options like throttle set, mixture set, etc. So what are the proper selections?
2. When using "Send to FS as Normal Axis", in the FSUIPC7 ini file, what should the axis entry look like? For example, if I were to select "Send Direct to FSUIPC Calibration" for the throttle axis, I would see something like this in the ini file
TX,256,D,4,0,0,0 -{ DIRECT: Throttle }-
If I had selected "Send to FS as Normal Axis" instead, how would that entry look?
Thanks,
Al
H Al,
the 'proper' selection depends on the aircraft. See the the FSUIPC User guide section ' DETAILS OF MSFS’s AXIS CONTROLS' for further details.
As for your second question, if its not direct then its a standard control and the format is as described in the Advanced User guide.
John
Hi John,
I finally realized what I really needed to do was convert the throttle axis range of -16384 to +16384 to just 0 to +16384. I used the technique from the Advanced User's manual of multiplying by 0.5 and adding +8192.
TX,256,D,4,0,0,0,*0.5,+8192 -{ DIRECT: Throttle }-
Thanks for the help!
Al
Ok - but to convert the range -16384 to +16384 to the range 0 to +16384, you need to add 16384 and then half, not 8192...
Posted by: @fsuipcOk - but to convert the range -16384 to +16384 to the range 0 to +16384, you need to add 16384 and then half, not 8192...
Hi John,
Either way works mathematically. It's just a matter of the number of bits available to represent the largest number.
Adding 16384 to the range -16384 to +16384 converts the range to 0 to +32768, and then multiplying by 0.5 yields the range 0 to +16384.
Mulltiplying first by 0.5 converts the range -16384 to +16384 to -8192 to +8192, and then adding +8192 yields the range 0 to +16384. This latter order of multiplying first and then adding limits the max value during the calculation to +16384.
Page 41 of the FSUIPC7 Guide for Advanced Users says " If both parameters are given, the multiplication must come first, and is performed first. The resulting value is constrained to be in the range -16384 to +16383 ..."
I assume this has to do with the number of bits available for number representation.
Al
Yes, I forgot that the multiplier comes first when using axis scaling!
Also, as the scaling is done before calibration, doesn't the calibration then re-calibrate this to the full range?
Not sure about this but worth checking...