FslabsA321 bind key.

[martynahubert]

Hello.

I have set specific keys for landing light, beacon, taxi and so on which works with PMDG and Fenix but not with FsLabs

Any idea how solve it?

[John Dowson]

The FSLabs uses custom controls via the Rotor Brake control for the lights - you can see this if you set logging for Events, open the logging console and flip the switches in the VC.
I provided information on how to set-up the lights in this thread: 

You can use the attached macro file which has macros for the Nose, Strobe and Beacon lights: FSLA321.mcro

For any other lights/switches, try logging the event(s) used and either assign directly (if only one event) or add another macro to that file to send multiple events.

John

[martynahubert]

Rotor brake?

any quick and simple tutorial?

because even I don't know what's this?

[John Dowson]

36 minutes ago, martynahubert said:

Rotor brake?

The Rotor Brake control is normally only used in helicopters. As it is not used in aircraft, some aircraft developers use this for their custom controls, with the parameter indicating the function.

37 minutes ago, martynahubert said:

any quick and simple tutorial?

No, sorry. There is a FAQ entry on how this is used in PMDG aircraft here: 

 

However, that is NOT applicable to the FSLabs,, and FSLabs don't provide an SDK as PMDG provide,

Basically I found these using FSUIPC's logging facilities, which you can use in many (not all!) cases to determine how to control a switch. I showed how I found these in that previous post I referenced, so take a look at that,

However, things are a lot more complicated in MSFS2020/2024. Every aircraft seems to use different methods - some custom controls (via Rotor Brake or other means), some Input Events, sometimes  Lvars/Hvars/Bvars. These things are very dependent on the aircraft developers.

With FSUIPC, I try to provide access to these different methods, and can advise on how to look into the different methods of how to assign a particular button using the features I provide. For most aircraft, presets tend to be the easiest way, and the MobiFlight HubHop site (https://hubhop.mobiflight.com/presets/), which is a community-driven effort led by MobiFlight) would be the starting point. However, there seems to be nothing there at the moment for the FSLabs aircraft.

As the FSLabs seem to use custom controls via the Rotor Brake control, you can use FSUIPC's logging facilities to determine what is needed to control any particular switch. Set logging for Events (Log->Events), open the logging console (Log->Open Console), and then see what is logged when you flip the switch in the Virtual Cockpit using the mouse. Then either assign to that (if one event is logged), or create a macro entry if multiple events are logged. Thats the basics, but it can get more complicated.

John 

[martynahubert]

You explained it to me briefly, I now know more or less what it is all about.

I made one button for RWY light but for landing light,  it doesn't work yet.

Anyway thanks for help.

[martynahubert]

and I've noticed something.

If I set one button for example RWY lights it works but if I set another button for landing lights, from list I have to set again ROTOR BRAKE and I'll enter new parameter, RWY lights stop the working or I'm doing something wrong.

 

Which key is for pop up Fsuipc?