Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ohs and Axis in FSLabs A321N for MSFS (HONEYCOMB BRAVO)

Featured Replies

Hello, I'm figuring out on how I can program the AUTOPILOT PANELS in the bravo quadrant hardware in MSFS but it seems FSLabs has its own LVARS integrated in their system because Ohs and Axis cannot detect it. Is there any other ways to configure or program the AutoPilot Panel in Bravo? Much appreciated if someone can help and guide me for the steps. Thank you!

  • Commercial Member

FSLabs uses ROTOR_BRAKE codes, same principle that PMDG have (but with different numerical codes of course). I'm not sure if there is an online resource that lists them.

The two ways to get to thouse are either
- the MSFS developer mode (activate devel mode, open Tools->Behaviors, click back into the sim window, hover the mouse over the control you are interested in and press Ctrl-G. Examine the components called "...MouseRect..." or "...Interaction..." or similar)
or
- looking at the behavior code directly in the XML files of the model (unless they are encrypted or streamed). I don't have the new A321. but in the standard FSL 321, the files for the internal of the VC are for example here: \Community\fsl-a32x\SimObjects\Airplanes\FSLabs A321 CFM\Model\FSLA32X_Interior_FSL.xml

1 hour ago, ItsMeJDs said:

MSFS but it seems FSLabs has its own LVARS integrated in their system

Just for the record: that is not what LVars are for. If you are looking for the "standard/official/default" way of handling external input, that would be the MSFS Input Events (IEs in AAO) and their bindings, the BVars. I don't think that FSLabs are using those, but an increasing number of developers adhere to this default and implement them. IEs are individual to each aircraft, and you can only see the IEs for a particular aircraft when AAO is connected to the sim and you are sitting in the cockpit. In AAO you will find them on the normal event selection treelist in a separate tab called "MSFS IEs".

spacer.png

Edited by Lorby_SI

LORBY-SI

  • Author

Hello thank u for response to be honest I'm new in programming the bravo quadrant thats why a bit confusing to me for the first can i contact you in discord so that u can help me? Really much appreciated.

  • Commercial Member
15 minutes ago, ItsMeJDs said:

i contact you in discord so that u can help me?

Sorry, but I don't provide that kind of support. That would be financial suicide (LWR Inc. gets about $10 from each license sale, but an hour of my time costs $150)

In my experience, making a config for the Bravo will take about two hours if you use one of the templates that I already made for other aircraft (they are on flightsim.to), and replace the various events and variables in it. 

 

Edited by Lorby_SI

LORBY-SI

  • Commercial Member
9 hours ago, ItsMeJDs said:

Here's What i Found but i don't know how to start

IMG: https://imgur.com/a/yqLVLuz

The start would be to download one of the templates that I made (preferably an Airbus), apply it to the FSL, and then start changing the assignments to what the FSL needs.

But beware, the FSL planes were apparently not made with external controls in mind. I started work on a template for the standard FSL 321 that I have, and this is turning into a nightmare. The buttons weren't much of a problem, but it seems to be next to impossible to configure the lights and LEDs properly. The plane doesn't use the SDK simulator variables to report AP state etc. and not all of the buttons seem to have emissive properties (Master Caution for example). 
I am really struggling with this, a fully working template seems to be impossible to make.

But you can have my template if you want - you will probably have to change all the ROTOR_BRAKE codes (but it is also possible that FSL kept them all the same)

Edited by Lorby_SI

LORBY-SI

  • Author

Hello thank u again for response i would be happy u can let me try your template i just want my autopilot panel to work but unfornately i do not have knowledge on configuring this at the momment i spent 5 hrs looking for it. And I see the ROTOR BRAKE Code inside the FSL A321N SimObjects Model and FSLA32X_Interior_FSL.xml file but i cannot make it work. Much Appreciated if u can let me try the template.

  • Commercial Member
3 hours ago, ItsMeJDs said:

but i cannot make it work

On the button assignment dialog in AAO, select the "ROTOR_BRAKE" simulator event for Key Down. Doubleclick into the little numerical box to the right of the event (event value, where it says 46007 in my screenshot) and enter the 7xxxx number that you got from the XML. Press the button on the Bravo that you want to assign this to. Save.

Be mindful that FSL makes you do maths before you get to the actual code. Sometimes they add 1,2,3 or 4 to the base value to simulate the various mouse actions (LeftSingle = left mouse button down, etc.). And again sometimes they subtract a random value from the base for no reason that I can understand.

spacer.png

Edited by Lorby_SI

LORBY-SI

  • Author

Thank you so much sir! AutoPilot now works!

  • Author

My LED Lights now working i just link the PMDG Profile u created Gear Down Indicator are working and also Parking Brakes and Master Caution but some of the button like HDG REV ALT IAS are in light mode and also the Autopilot Button

  • Commercial Member
2 hours ago, ItsMeJDs said:

My LED Lights now working

My FSL Template contains an autoscript for the LEDs, it should be working for the AP, Gear, Master Warning and Caution (AP lights are on in selected mode and off in managed mode). But my Template is not for the Neo, maybe the variables are different with that one.

PMDG cannot work at all from my point of view. They have custom variables of their own.

Edited by Lorby_SI

LORBY-SI

  • 6 months later...
  • Author

Hello since the FSLABS PW1100 released i tried the profile from the A321N previously but it seems its not working? Any other profiles for the PW variant? Much appreciated 

Thank you!

I have found out that in FS2024 the profiles are not working.

Edited by ItsMeJDs

  • Commercial Member
2 hours ago, ItsMeJDs said:

Hello since the FSLABS PW1100 released i tried the profile from the A321N previously but it seems its not working? Any other profiles for the PW variant? Much appreciated 

Thank you!

I have found out that in FS2024 the profiles are not working.

That is of course always possible and not unexpected.

I'm really sorry, but I am not doing any development work at this time or in the forseeable future.

But these templates are open source. Since the "framework" is there with the old template (=scripts and buttons), anybody who is familiar with the MSFS developer mode is welcome to alter the templates to taste and publish them with their own name attached. I don't mind, I don't need to be mentioned or quoted.

Edited by Lorby_SI

LORBY-SI

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.