FloatingPoint

Yes, this was my first successful task before opening this post. I understood sometimes it's not easy to get both (effect + animation), but thanks to your hints I understood a lot more about how things work in the sim and already mapped multiple sliders and knob on my H125 helicopter perfectly! Thank you!

In the meantime, I tried on other knobs (B:NAVCOM_COM1_Volume_Set for example) and the system you suggested works like a charm. It doesn't work on the two knobs on top (VOL and DIM) for some reason, no matter which Axis min and Axis max I use. Example of working knob: Another question I have is: I noticed I can't access any information with CTRL+G in the Behavior panel for some items (the altimeter QNH setting knob for example on this specific plane). Is there any other way to access and work with those "ghost" variables? Thanks

OK, thanks, are you referring to this section?

Thanks a lot for the hint! I tried, and the result is it increases by 4-5 units when the value is 1 (or more) and decreases by 4-5 units when it's 0. It doesn't transfer the assigned value to the knob directly. Video showing the behavior: https://www.postfrontal.com/FS2020/dimmer.mp4 Any other idea? :)

As a further reference, this is ChatGPT's analysis of the script: Script Breakdown: 1. `50 (>O:Knob_Position)`: - This appears to set the value `50` to the variable or local variable `O:Knob_Position`. - The `>` symbol typically suggests an assignment, directing the value on its left to the variable or function on its right. - `O:` is a prefix which often indicates a local or custom variable, in this case, `Knob_Position`. This variable likely represents the position or value of a specific knob in the simulator. 2. `(O:Knob_Position) 0.9000000 *`: - This retrieves the value of `O:Knob_Position` and multiplies it by `0.9000000`. - The result is a value that's 90% of the original `O:Knob_Position`. 3. `10.00000 +`: - This takes the previously calculated value and adds `10` to it. 4. `(>K:LIGHT_POTENTIOMETER_4_SET)`: - The calculated value from the previous steps is then assigned to the function or event `K:LIGHT_POTENTIOMETER_4_SET`. - The `K:` prefix often represents a predefined event or function within the simulator. In this case, it appears to be related to setting the value of a light potentiometer, possibly the fourth one if there are multiple. Summary: The script seems to be adjusting the value of a light potentiometer in the simulator based on the position of a knob. Specifically: 1. The knob's position is set to 50. 2. This position is then scaled down to 90% of its value. 3. 10 units are added to the scaled value. 4. The final calculated value is used to set the position or intensity of a light potentiometer in the simulator. The exact physical or visual outcome would depend on how the simulator interprets and applies the `K:LIGHT_POTENTIOMETER_4_SET` event, but it's clear that the script is designed to adjust lighting based on a knob's position, with some scaling and offset applied.

Correction, it's >O:Knob_Position, not >0:Knob_Position (it's a component variable I suppose): 50 (>O:Knob_Position) (O:Knob_Position) 0.9000000 * 10.00000 + (>K:LIGHT_POTENTIOMETER_4_SET) I know I could use (>B:NAVCOM_Dimming_Inc) e (>B:NAVCOM_Dimming_Dec) to move the knob and dim the lights at the same time, but I couldn't find a way to make them work with a MIDI potentiometer keeping the position of the knob coherent with the position of the MIDI pot. The scope of this exercise is to use the pot as an axis, not as a button. Thanks

Hello everybody, I am a new AxisAndOhs customer (I bought the software on JustFlight a couple days ago) trying to get a hold on scripting and assignments. I read many posts here and found some (outated) tutorial on YT, but I am still missing some points. As a first "easy" experiment I am trying to use a MIDI controller (a non-infinite rotary with 0-100 movement from a KONTROL Z1) to control the radio light dimming knob on the C152 (please see attachment, it's the upper knob in the middle of the screenshot). I was able to get the radio lights dimming correctly with the movement of the MIDI pot with the script you see in the screenshot, and now I am trying to understand how to setup the script for the knob animation. I see a piece of code in the Behavior Dev mode window which I believe is what makes it move, but I am not sure how to "translate" it to make it work with AAO: 50 (>0:Knob_Position) (0:Knob_Position) 0.9000000 * 10.00000 + (>K:LIGHT_POTENTIOMETER_4_SET) Any help would be appreciated! :) Thank you!