Hi,

I've been having some difficulty mapping in game buttons the the WinCtrl PAP3 autopilot panel. The dials and switches are not a problem but for some reason I can't get any of the buttons to work. They are big momentary push buttons (that come back out right away), here is a link if you are unfamiliar with the product: https://winctrl.com/view/goods-details.html?id=1065. I am in MSFS 2020 and I've been trying to map Flysimware Learjet 35 and the Contrail Falcon FA50 controls without any success. I've been reading the LVAR's from the sim and trying to map those. Also tried using IE Events but nothing happens. I tried assigning LVAR's to the button down and button up with values of 1 and 0, and I tried using just the button down with value 1. What am I doing wrong?

thanks.

Lior

19 hours ago, Damour33 said:

What am I doing wrong?

Is the button not picked up by AAO or are you asking about the correct assignments? Those assignments are different for almost every aircraft, and must be figured out individually. Ideally by using the MSFS developer mode, Tools->Behaviors. Then click back into the sim, hover the mouse over the VC control that you are interested in and press Ctrl+G. Now analyze the Interaction components that handle the mouse events - replicate the code as required in AAO.

For the Learjet, MSFS IEs or their BVars should work fine. Just checked the HDG button, no problem there 1·(>B:AUTOPILOT_Heading_Mode_Toggle)

Edited July 2Jul 2 by Lorby_SI

thanks, I've never done that before, I'll give it a try. I also noticed that some IE's only seem to change the button animation or only turn on but not off (I found the YD PRI 1 and 2 and YD ENG 1/2 - but they won't turn them back off). Will the Behaviors give me something different than the IE's?

thanks.

Lior

1 hour ago, Damour33 said:

Will the Behaviors give me something different than the IE's?

They are both assets of the behavior code.

IEs and BVars are related. The IE is the "parent", the BVars are its "bindings". BVars have the same name as the IE, with an added "do-word", like "_Inc", "_Dec", "_Toggle", "_Set". Those words are not set in stone, they can be anything =whatever the aircraft developer feels is appropriate - both IEs and BVars are not assets of the sim, they belong to the aircraft code. Which means that they can and will be different for each plane.

On the button assignment dialog, you can switch both the Key Down and Key Up boxes to "MAN", and enter any BVar that way (=manually)

Edited July 3Jul 3 by Lorby_SI