[Joystick bindings not working]

I found that the engine fuel switches are not SET ENGINE x VALVE like in most other addon aircraft for MSFS, but "SET ENGINE MASTER x".

[Sujet : SimBrief + A310 show me "Pending"]

14 hours ago, Noble41 said:

To the Author - Simbrief is a paid service.  Simbrief released a new update, at least for my version as it now reads the A310.  I hope this helps. 

I thought simBrief is free to use? At least I do not pay a single Cent to use it.

[[Suggestion] Nosewheel steering on a separate axis]

Okay, I tried again. I re-assigned my axis on the joystick and now it does work indeed. Case closed.

[Nosewheel steering problem]

I think the clue is that the slightest move of the rudder axis will reset the NWS-axis. Will test this later on.

[Joystick bindings not working]

I had looked for aircraft specific variables for all those lights, but no luck. I don't mind creating a joystick profile specifically for the A310.

[[Suggestion] Nosewheel steering on a separate axis]

8 hours ago, lowpolybutt said:

In the EFB, nosewheel steering should be OFF, and an axis should be to Nosewheel Steering in your MSFS controls settings

Yes, I have that and it does work perfectly on all other aircraft in MSFS, except for the A310. I use a Logitech Wingman Extreme 3D and I have defined its throttle-axis as NWS. Other people who I know do have the same problem. I think this function needs some review. I can test again later today, need to leave home shortly.

[Joystick bindings not working]

Dear team,

I am using a Honeycomb Alpha yoke and the standard bindings for lights like BCN, STROBE, NAV, LANDING, TAXI etc. do not work. Is there a solution for this?

[[Suggestion] Mass&Balance pull from simBrief]

PS: I would also favour a possibility to not only use sliders to set the number of passengers, cargo and fuel, but also make those input fields available to type these values via keyboard. Especially the fuel figure can be quite hard to set to the required amount.

[[Suggestion] Nosewheel steering on a separate axis]

Dear team,

on the Asobo/MS forums I already read your reply to this topic. Despite the reasoning that you implemented it this way to ensure compatibility with Xbox users of the A310, I would like to suggest to have NWS available as well on a separate axis. There is quite a number of virtual pilots who have a separate controller/axis dedicated to this function and really would like to use it with the A310. Hopefully this is worth considering the effort to implement this feature.

[[Suggestion] Mass&Balance pull from simBrief]

Dear team,

thanks for this nice aircraft.

Are there any plans to have the Mass&Balance page on the EFB populated by the data that users can pull from simBrief? I really do enjoy this function on the FBW Airbus and I think it would be a great feature to improve the usability and logics of this aircraft.

[A3ST BelugaST CSL setup with swift pilot client]

Hi all!

For those using swift pilot client, here's the configuration that you'll need to use so swift can actually render the A3ST BelugaST CSL that the iniBuilds team has provided.

 

Introduction: for swift it is recommended to install all CSL sets somewhere inside X-Plane's folder, but independent from any other pilot client plugin - this way nothing will touch your CSL sets when you update, move or delete such pilot client plugin. The swift team recommends creating a CSL subfolder in /X-Plane 11/Custom Data/, but it is completely up to you where you choose to install those sets to. As mentioned before, the only condition is: CSL sets have to be placed somewhere inside the X-Plane folder! More information about this on our page: Recommended Installation Practices

 

You have 2 ways to integrate the BelugaST CSL into your model set:

1. Standalone: for the time being, this is our preferred method of installing the BelugaST CSL set for us with swift. If you do not have a separate CSL folder like "Other" or "Miscellaneous", then create it in your main CSL folder => /X-Plane 11/Custom Data/CSL/Other .
   Extract the A3ST-folder from iniS_Beluga_Bluebell_Model_Matching_2.zip into this directory. Go into this directory, open xsb_aircraft.txt with a text editor (e.g. Notepad). Replace its entire content with the following:

   EXPORT_NAME __A3ST
   
   OBJ8_AIRCRAFT A3ST_AIB
   OBJ8 SOLID YES __A3ST\A3ST_AIB.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   
   OBJ8_AIRCRAFT A3ST_AIB2
   OBJ8 SOLID YES __A3ST\A3ST_AIB2.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA2
   
   OBJ8_AIRCRAFT A3ST_AIB3
   OBJ8 SOLID YES __A3ST\A3ST_AIB3.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA3
   
   OBJ8_AIRCRAFT A3ST_AIB4
   OBJ8 SOLID YES __A3ST\A3ST_AIB4.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA4
   
   OBJ8_AIRCRAFT A3ST_AIB5
   OBJ8 SOLID YES __A3ST\A3ST_AIB5.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA5

   Save the file, close it. Continue with the steps at the end of this post (after bullet point 2).
   
   
    
2. Integrate into Bluebell: you can also add the BelugaST CSL to your existing Bluebell set, however you may lose them with the next update of Bluebell, except if iniBuilds would like to officially add them to BB, contact has been made. Until then, we recommend the standalone solution as explained in bullet point 1.
   
   If you still want to integrate the BelugaST CSL into Bluebell, this is how it's done: extract the A3ST-folder from iniS_Beluga_Bluebell_Model_Matching_2.zip into /X-Plane 11/Custom Data/CSL/BB/BB_Airbus . Enter the A3ST-folder and delete xsb_aircraft.txt. Go to the /BB_Airbus/ directory and open xsb_aircraft.txt with a text editor (e.g. Notepad). Under title "EXPORT_NAME __Bluebell_Airbus" create an empty line and paste the following text:

   OBJ8_AIRCRAFT A3ST_AIB
   OBJ8 SOLID YES __Bluebell_Airbus/A3ST/A3ST_AIB.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   
   OBJ8_AIRCRAFT A3ST_AIB2
   OBJ8 SOLID YES __Bluebell_Airbus/A3ST/A3ST_AIB2.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA2
   
   OBJ8_AIRCRAFT A3ST_AIB3
   OBJ8 SOLID YES __Bluebell_Airbus/A3ST/A3ST_AIB3.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA3
   
   OBJ8_AIRCRAFT A3ST_AIB4
   OBJ8 SOLID YES __Bluebell_Airbus/A3ST/A3ST_AIB4.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA4
   
   OBJ8_AIRCRAFT A3ST_AIB5
   OBJ8 SOLID YES __Bluebell_Airbus/A3ST/A3ST_AIB5.obj
   VERT_OFFSET 2.8
   AIRLINE A3ST BGA
   LIVERY A3ST BGA BGA5

   Make sure that there is an empty line between the last line of "Beluga number 5" and the next aircraft definition. Save the file, close it. Continue with the steps below.

Now that you have finished editing xsb_aircraft.txt, you can proceed with adding models to your Active Model Set in swift. If you are not familiar with how it's done, follow this:

• start "swiftData" app (Mapping Editor), go to the "Stored own models XPlane" tab and select "force reload XPlane"

• when it's finished, press CTRL-F to access the filter window. Type "A3ST" in the box "Airline ICAO" and hit OK button

• select the Beluga models that you wish to add to your Active Model Set and press ALT-A (this will add them)

• go to "Active Model Set XPlane" tab and select "Save XPlane"

• start X-Plane and swiftGUI and enjoy the BelugaST! 🙂

 

Thanks a lot to my great colleague "Birdy" who tweaked xsb_aircraft.txt to make it work 100% fine, you are the boss! Thanks for the iniBuilds team for creating the BelugaST CSL, hopefully we will be able to add it to the official Bluebell set soon!