Hi eveyone.

Someone here in the forum managed to assign the autopilot FLC button to WT CJ4 plane?

I'm mapping the autopilot at Behringer X-Touch Mini and I am not able to assign the FLC button.

I tried with "watch simulator events". It shows "AP_FLIGHT_LEVEL_CHANGE_ON" and "AP_FLIGHT_LEVEL_CHANGE_OFF" every time a press FLC button at the cockpit, but neither of those two mappings work.

If I assign "AP_FLIGHT_LEVEL_CHANGE", it doesn't appear to control the FLC button since "AP_SPD_VAR_SET" is shown at "watch simulator events" when I press the assigned button at X-Touch Mini (even though the mapping is "AP_FLIGHT_LEVEL_CHANGE").

I would appreciate any help if it exists.

Thank you in advance.

1 (>H:WT_CJ4_AP_FLC_PRESSED) (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET)

This is what the behavior code does (and you can see why the event observer shows the AP_SPD_VAR_SET - it happens every time, but it is not the cause, just one of the results). Create an RPN script with this code and assign that to your button.

The state of the FLC should be in

(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool)

 

Edited August 29, 20223 yr by Lorby_SI
Error in script code

On 8/29/2022 at 6:53 PM, Lorby_SI said:

1 (>H:WT_CJ4_AP_FLC_PRESSED) (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET)

This is what the behavior code does (and you can see why the event observer shows the AP_SPD_VAR_SET - it happens every time, but it is not the cause, just one of the results). Create an RPN script with this code and assign that to your button.

The state of the FLC should be in

(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool)

 

Thank you very much for your help. I will need to learn something about scripting to be able to apply what you propose.

Thanks!

 

 

47 minutes ago, barbaryto said:

Thank you very much for your help. I will need to learn something about scripting to be able to apply what you propose.

Thanks!

 

 

Not really.

1. Go to "Scripting -> RPN Scripts Editor"
2. Select a script group on the left that makes sense (or create a new one with the "Manage Script Groups" button). When in doubt, just use the group "Scripts"....
3. Enter a "Script Title" of your choice at the top.
4. Make sure that your group is selected in the "Script group" box
5. Copy & Paste the code above into the big white editor box
6. Press "Save as New"

Now you can select this script in the Event selection list that you get on the Button assignment dialog for the key down/key up items.

 

 

 

Edited August 30, 20223 yr by Lorby_SI

17 hours ago, Lorby_SI said:

Not really.

1. Go to "Scripting -> RPN Scripts Editor"
2. Select a script group on the left that makes sense (or create a new one with the "Manage Script Groups" button). When in doubt, just use the group "Scripts"....
3. Enter a "Script Title" of your choice at the top.
4. Make sure that your group is selected in the "Script group" box
5. Copy & Paste the code above into the big white editor box
6. Press "Save as New"

Now you can select this script in the Event selection list that you get on the Button assignment dialog for the key down/key up items.

 

 

 

It worked!

Thank you for your valuable and always willing support!

I only have one button configuration left to complete the AP: VS button. I tried with every "VS" option in the Event selection list, and "AP_PANEL_VS_HOLD" is the one with the most similar behavior although it does not have exactly the same behavior.

I noticed that each time the VS button is pressed (in the cockpit), it alternates between 0 (>K:AP_PANEL_VS_HOLD) and 1 (>K:AP_PANEL_VS_HOLD) in the Receiving Events from simulator window.

Edited August 31, 20223 yr by barbaryto

Working Title CJ4 - Guides

-> Sim Variables -> H-Events -> AP Mode triggers

IMHO the first step should be to ask/google the developer who made the plane. He is the only one who knows for sure how things are supposed to work - because he made them. Next visit should be to flightsim.to, to check if somebody made an AAO template or a collection of scripts for that plane. Even StreamDeck or X-Touch packages can help, because the scripts are usually delivered separately and you can just import them. Also, you can take a look into the MSFS developer mode, behavior debug. There you can dive into the components of the model and find out what button is connected to which events or other triggers. Finally, you can take a look into the behavior files of the plane using Notepad++ and analyze the components there.

But pestering the aircraft developer is the preferred option I think. Maybe one day they will all add a short description of their custom input events, so customers who want to use external controls may find them more easily. Just like WT are doing on their website. I don't like the idea that we, the end users, are forced to poke around in actual Behavior coding to find out what makes an aircraft "tick"...

Edited August 31, 20223 yr by Lorby_SI