April 29Apr 29 Hi, i'm currently in the process of binding alle the buttons and levers of the Inibuilds YS-11. there i stumble around a O: Variable for the Throttle Friction Lock. How can i assign this in axis and ohs? I tried to replicate the Script from the Behavour dialog, but this is not working :(
April 30Apr 30 Commercial Member O: and I: variables cannot be accessed from the outside. They are specific to the compontent that they are attached to (=there can be dozens of identical O: variables with the same name in the cockpit for the different buttons/knobs/levers). Asobo says that this shall be possible in the next SU of MSFS 2024. It kinda works in the Beta too, but not always. I have a bug report still open on the developer forum about that. LORBY-SI
May 3May 3 Author okay thanks for the explaination Do you have an idea why the command for "VS UP and Down via Autopilot" getting stuck after 4 clicks and then i have to wait until i can turn it further? The command is: 1·(>B:AUTOPILOT_VerticalSpeed_INC) and 1·(>B:AUTOPILOT_VerticalSpeed_Dec) I also tried to use them with , number behind it. but it did not change anything. Seems like B Variable on a Rotary are very bad and get stuck. Have the same problem for the CRS 1 Selector Command 1·(>B:AIRLINER_CPT_KNOB_R1_Indicator_Set_Dec,·number) Edit: So i figured out that the "getting Stuck after a few turns" only happens with the Honeycomb Bravo Right Rotary, when i use the command 1·(>B:AIRLINER_CPT_KNOB_R1_Indicator_Set_Dec,·number) with the Midi Controller, its turning fast and fine all the time. Any idea why this might be happening? Edited May 3May 3 by Bam2000
May 3May 3 Commercial Member 5 hours ago, Bam2000 said: I also tried to use them with , number behind it. BVars don't have a unit. 5 hours ago, Bam2000 said: Any idea why this might be happening? Not really. Why not use the same BVar for both assignments? LORBY-SI
May 4May 4 Author 23 hours ago, Lorby_SI said: BVars don't have a unit. Not really. Why not use the same BVar for both assignments? i dont use both at the same time, it was just an example that the other BVar also does the same when put on the Honeycomb Bravo. i now decided to give up on the Honeycomb Bravo autopilot and use my Midi Controller for the setup, there it is working fine
May 4May 4 Commercial Member 4 hours ago, Bam2000 said: i dont use both at the same time, it was just an example that the other BVar also does the same when put on the Honeycomb Bravo. i now decided to give up on the Honeycomb Bravo autopilot and use my Midi Controller for the setup, there it is working fine I still don't understand. The problem could very well be related to the BVar itself, not the hardware. You have to compare apples to apples, not oranges to potatoes. I have a Bravo too and made a couple of templates for it in the past, I never noticed such behavior. So the quetion is, if the same BVar for the same aircraft behaves differently on the Bravo and the MIDI device. For example, maybe the Honeycomb knob is sending the BVars too fast for the aircraft to process them. Can you try using the IE instead? For every BVar there should be one. What aircraft is this? Still the YS 11? Edited May 4May 4 by Lorby_SI LORBY-SI
May 4May 4 Commercial Member On 5/3/2026 at 10:06 AM, Bam2000 said: Do you have an idea why the command for "VS UP and Down via Autopilot" getting stuck after 4 clicks and then i have to wait until i can turn it further? The command is: 1·(>B:AUTOPILOT_VerticalSpeed_INC) and 1·(>B:AUTOPILOT_VerticalSpeed_Dec) Using the rotary encoder on my Bravo and after buying the YS-11, I tried both the BVar and its' parent, the IE. The IE seems to work smoother, but I can't see anything inherently wrong with either of them. When assigning the IE, use value 1 for Inc and -1 for dec. IEs can be assigned directly to a button, no scripts required. You will find them on the normal event selection dialog, in the tab "MSFS IEs". To set the value to be sent by this event (1, -1), you use the little numerical box to the right of the Key Down. Edited May 4May 4 by Lorby_SI LORBY-SI
May 4May 4 Commercial Member On 4/29/2026 at 9:56 PM, Bam2000 said: O: Variable O-Variables seem to work now (=in the new implementation of MSFS 2024 SimConnect using the upcoming version 4.57 of AAO). I was able to assign an axis to the throttle friction lock lever using this variable: (O:YS11_SYSTEMS_BEHAVIORS:MISC:INOP_SWITCHES:THROTTLE_FRICTION_LOCK:THROTTLE_Friction_Lock, Number) with Axis Min = 0, Axis Max = 100 OVars are not working in every plane though. Edited May 4May 4 by Lorby_SI LORBY-SI
Create an account or sign in to comment