Giel Posted September 18 Report Posted September 18 Goodevening, Last week I bought the Pilatus PC-12 from Simworks, I'm using FSUIPC7 to bind my controls to my Honeycomb Alpha and Bravo hardware. Everything seems to work, except for the condition lever. When I link it straight in MSFS to the "condition lever axis", it works, however in FSUIPC I tried: Condition lever set Condition lever 1 set Axis condition lever Axis condition lever 1 set Presets Input events All with no effect. Since my files were too big to add, I've used a file exchange server. https://filetransfer.io/data-package/1r4xtPEC#link
John Dowson Posted September 19 Report Posted September 19 First, try to use logging to determine what the condition lever is using. If standard controls are not being used, then it is most likely an input event or an lvar. You said you have tries input events, but what exactly have you tried? Is there an input event available for the condition lever position, does it change value when you move the condition lever (use logging!)l and if so if you set the value of the input event does the condition lever move? If there are no input events, then there is probably an lvar. Try listing the available lvars and values (using Add-ons->WASM->List Lvars) to see if any look applicable. If so, determine the maximum/minimum values for the lvar and define your own preset. I have just explained how to do this (in another aircraft) in this post: I don't have the PC-12, so cannot look into this in any detail, But the procedure to determine how to assign to control something is the same in all aircraft - logging and trial and error... 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