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
Much appreciated on your reply. Unfortunately this is all way above my pay grade. I am just going to bow out and await SWS to correct their mistake since it worked before their update. If they don't it will just be a hangar icon. 🤣
Again, thank you for the efforts and I am sorry for wasting your time on this. Please close this thread.
Its not that difficult - if you follow my instructions and show me the results I'm sure we can sort this out...
I have also seen this on the SWS discord support:
the (L:1:RUDDERInput, Number) will not move my pedals but (L:RUDDERINPUT, Number) will.
So maybe try that instead, i.e. try with
//SWS/Kodiak 100/Controls My SWS Kodiak 100 Rudder Set#$Param 163.84 / (>L:RUDDERINPUT)
Also a good idea to test the value range for that lvar: move the rudder (with the mouse) fully in one direction, then list the lvars (Log->List Lvars) and note the value of L:RUDDERINPUT, then deflect the rudder fully in the other direction and list the lvars again - this will give you the full lvar range so that we can calibrate your axis correctly to control the lvar. You can also try setting values to that lvar using the Add-ons->WASM->Set Lvar... menu item which will confirm if this lvar works and you can also test the range of values.
Posted by: @pivot2163Again, thank you for the efforts and I am sorry for wasting your time on this.
No time wasted. I can close this thread, but I think you should at least try a few things first. Its not that difficult and sorting out such issues gives you valuable insight into how to set-up more complicate assignments in FSUIPC (i.e. those not using standard controls or existing presets).
Regards,
John
Will give it a shot John. One thing though, I don't have a WASM->Debug in the log menu list to capture the info as indicated in the previous response. On another note, I didn't even know you COULD move the rudder with the mouse. (hahaha)
Will report back.
Posted by: @pivot2163I don't have a WASM->Debug in the log menu list to capture the info as indicated in the previous response.
Sorry, my mistake - its WAPI->Debug (WAPI is the WASM API). I will correct my previous message.
Posted by: @pivot2163On another note, I didn't even know you COULD move the rudder with the mouse. (hahaha)
If there is a control for it in the virtual cockpit (VC), then you should be able to operate it using the mouse, just like everything else. There may also be default key assignments to control the rudder (you need to check what these are) which you could use instead...
Also, as you are using MSFS2024, it may be worth checking for Input Events. Try listing the Input Events and see if any look like they are for the rudder. You can also set logging for Input Events when you move the rudder in the VC and this would log any changes to a rudder input event.
If there is an input event for the rudder, this can be controlled in several ways which I can also help with...