JoshF

Impossible to say for sure without some kind of screenshot of what was happening in the aircraft, but most likely your flight directors were off

Hi, is there any reason you're using SPAD.Next over the default WinWing software to configure your FCU? The A320neo V2 should be supported natively when using their software.

A lot of them are the same with regards to the FCU especially. If there are any you're needing for A300 let me know. I will be putting a list together for A300 but I can't give a timeline as I am currently very busy on other projects. Moving forward, I hope to have lists ready to go for aircraft launches

L:INI_ap1_on || L:INI_ap2_on

Hi, Not an exhaustive list of course, but here's the first draft, let me know if there's anything missing from here that you would like to see added 🙂 neo LVARs.xlsx

Yes I am working my way through the aircraft compiling the list 🙂 Unfortunately the server issues the other day and other work I have has pushed publishing it back slightly, but once it is done once; a lot of it will be easily convertible for our entire fleet and will be published earlier going forwards

Hi, like I say here: There's well over 1000 (upon inspection putting the list together, its actually closer to 3000) LVARs in use in the Airbus code base, its not a case of just dumping a list of all of them, L:INI_POTENTIOMETER_18 for example wouldn't be of that much use. I concede putting the list together has taken longer than planned but I aim to have it up and published within the next couple days

Hi Mark, which ones are you looking for? There's technically well over 1000 so if you give me a list of the ones you'd like I can provide them

Sure, Speed: - pull: L:INI_FCU_SELECTED_SPEED_BUTTON - push: L:INI_FCU_MANAGED_SPEED_BUTTON Alt: - pull: L:INI_ALTITUDE_PULL_COMMAND - push: L:INI_ALTITUDE_PUSH_COMMAND Heading: - pull: L:INI_FCU_SELECTED_HEADING_BUTTON - push: L:INI_FCU_SYNC_HEADING_BUTTON V/S: - pull: L:AP9_BUTTON

@B320Max8 hi, is this still an issue?

@Philipp20 @aviator64 Hi, can I ask which B Events are you trying to use that are now not working? I can provide you with the relevant L Vars instead 🙂

Thanks both! Going by what Jorg said yesterday it will indeed not make a beta flighting; but its not long now until SU15 full release where we can all enjoy the neo V2 🙂

Additionally all here please confirm which axis binding you're using in the sim? Regular Throttle Axis, or Throttle Axis (0-100%)?

How is your Bravo set up? I'm using one and haven't seen this

Hi are you on Steam or MS Store?

Hi all, thanks for bringing this to our attention, it should be resolved now

Hi, is this still an issue?

Hi all, we've had reports this should be fixed in SU12 and A310 V 1.1.9, please try again and let us know

Hi all, we have reports that the uplink via Simbrief/ACARS issue has been fixed with SU12 and V 1.1.9 of the A310, please try it again and let us know

Just to confirm, this is with WU12 installed and with Asobo's NZQN uninstalled?

Thanks, we'll take a look

Hi, we have this logged internally but for now, this is not something we can fix as the default pilot and passenger models do not disappear in the default aircraft either. Once this changes in the core of the sim, it should automatically apply to the Taifun too.

Hi folks, thanks for getting in touch. This kind of thing is quite nuanced to balance as we're dealing with a myriad of variables here; Simbrief's data and calculations, our data and calculations; winds in the sim maybe not matching the predicted as closely as expected; cost indexes; procedural approaches adding more burn; the A310's notoriously problematic VNAV (IRL). The data we have provided for the profile is the same as that in our manual, which is what we use for our calculations in the sim. Having just performed a flight, I landed with 800 kg less than planned on Simbrief; however this is including what appeared to be several wind shifts at cruise in the sim, and following the full procedural approach to the ILS, which is not factored into Simbrief's calculations.

Hi, the solution for this is as follows: Go to your Community folder -> inibuilds-aiport-heathrow-egll -> Scenery -> airport-egll-london -> egll-modellib. In there you'll probably see three folders, one named texture, one named texture.HD and one named texture.SD. It seems that the download has downloaded the SD textures twice. You may safely remove the folder named texture, then re-name either one to just texture (i.e., texture.HD to texture). Reload the iniManager and your options should be back to normal. Please let me know if this works for you Edit: We aim to have this fixed within the next day or two so this won't be necessary; but this is the immediate fix

Hi, do you have the "Use SU10 Navdata" option set in your GSX settings? I believe it's in the FSDT Installer, under configuration options for GSX Pro