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] AAO Rudder Variable conversion to FSUIPC
I recently updated my SWS Kodiak 100 for MSFS2024 and it killed the FSUIPC Rudder Axis. The below discord was from an SWS member who stated a work around for the AAO's software. Would anyone know how to utilize the below commands in FSUIPC ?
L:1:RUDDERInputwith values from -100 (left) to +100 (right).
Posted by: @pivot2163"The rudder rigging has changed completely since last version, that's why it isn't working for you. Try feeding"L:1:RUDDERInputwith values from -100 (left) to +100 (right).
Thats a scoped lvar. To control this on an axis, create a preset - e.g. add the following to your myEvents.txt file (create this file in your FSUIPC7 installation folder if you do not yet have one):
//SWS/Kodiak 100/Controls My SWS Kodiak 100 Rudder Set#$Param 163.84 / (>L:1:RUDDERInput)
and then you can assign your axis to that preset (you can reload presets from the File drop-down menu once you have added this). That preset / calc code assumes an axis range of -16384 to +16384, so dividing the range by 163.84 should give you the -100to +100 range required. However, note two things:
1. if your axis range is different (i.e. not -16384 to +16384) then you need to adjust the calibration in the calc. code RPN
2. Even though an lvar (or scoped lvar) may have a range of -100 to +100, sometimes (i.e. for some lvars) when setting the value you need to use the range -1 to +1, or even 0-1. You can only see this via testing - you can use the Add-ons->WASM->Execute Calculator code menu option to try setting this scoped lvar to different values to check this.
Let me know if this works or you have any other issues.
Very much appreciated your reply. Will attempt this and see what happens. Will report back on success or failure..
This didn't seem to have any effect with the rudder axis. the below is what I copied to my "myEvents.txt", maybe it got messed up. My Axis is the -16384 / 16384 (Saitek Pro Rudder).
//SWS/Kodiak 100/Controls
My SWS Kodiak 100 Rudder Set# $Param 163.84 / ( >L:1:RUDDERInput)
FSUIPC finds it as "Set Preset to FS"
"My SWS Kodiak 100 Rudder Set"
Selecting as Rudder "send to FSUIPC Calibration" finds the axis in both sim and calibration pages but the sim auto re-centers the rudder immediately after deflection.
As I said, please test that lvar first to confirm it is working as expected. To do this, use the Add-ons->WASM->Execute Calculator code menu option to try setting this scoped lvar to different values, e.g.
-100 (>L:1:RUDDERInput) 0 (>L:1:RUDDERInput) 100 (>L:1:RUDDERInput) 1 (>L:1:RUDDERInput) 0.5 (>L:1:RUDDERInput) -1 (>L:1:RUDDERInput)
try each of those and check if you see any rudder movement, and determine the range of values that need to be set. Also, set logging for WAPI->Debug, and check your FSUIPC7.log file for errors.
This will tell you if you can use that (scoped) lvar to control the rudder or not. If you do see movement, then we can check your axis settings to the preset afterwards. If the calc code is going through to the WASM but the rudder is not moving, then you need to find another method of control - check for any rudder-related input events or standard lvars.
P.S. Sorry for the delay - was away on the 18th and missed this post yesterday..