IniSteve

Simply put, the reference aircraft we had access to had the gauges you see in sim.

Just to address the above. It will be best to approach this model with the understanding that its a bit of a "hybrid" of the L1011 variants. As mentioned in the preview videos and dev updates, we have taken liberties with certain features/traits of the Tristar to give options to a wide cross-section of users and allow it's many unique qualities to shine through. It should not be seen as a 1:1 rendition of any particular serial number. Knowing that we hope it will conjure up many great memories of your time with the aircraft even if a fastener or two is not oriented the correct way round 😉

Hi Nick, It should. I say should because we have checked the xbox package on PC and the missing textures are not present. The hope is there isn't a extraction era on the MP side again.

Hi Nick. Thanks for checking. The scenery team will look deeper into what is causing the error and if there is a way to mitigate it. I'll keep you updated when I have a conclusive answer.

Our newer bespoke products (A350/A340) are compatible with the current suite of WC products. We are also planning to add limited compatibility for FCU/MCDU with the A300 in a future update.

Hi. This should be resolved in the next update but I don't have a firm idea of when it will ship.

Comments like these are both unhelpful and untrue. We have explained on both this forum as well as our discord the challenge using hand controllers when it comes to multiple cursor overlays due to the way the SDK i sbuilt in the sim. Despite that you should be able to use a mouse without problems for interaction with the screens. (I use VR extensively with all our aircraft daily and don't run into this issue) As the sim and its SDK mature, we hope to revisit this and see if it can be refined. Once that happens, we'll provide an update.

Apologies for the confusion. We don't see the issue in the xbox package sent to MS when testing it on the pc but DO replicate the issue on the console so it's likely tied to something in the way files are unpackaged. A reinstall will often resolve this. if not, a method we recommend that may work (I will admit it's neither elegant or easy) is to remove ALL inibuilds sceneries and reinstall them one by one. This will ensure all the packages are properly loaded and synced with the texture library

This is a quirk of the controller and the sim. You can get around it by clicking the cog wheel next to the command line and manually assigning the axis.

Hi Nick. Thanks for the report. We'll investigate this as it's not happening on our end.

I am unable to repro this error. Can you confirm you're using the latest version of this livery?

To clarify, is your issue the Satcom antenna cover is displaying on the aircraft? There is an option in the EFB Aircraft page to show/hide.

Hi all. This was a bug that slipped through as a result of an FX modification. The good news is it has been identified and resolved and should be ingesting into the MP as you read this. Thanks.

Are you powering up the bus? On C&D spawn, turn on ESS BUSS to supply power to the batts and then start the APU. You should then be able to turn on the MFDs

Thanks for the report. This likely stems from an error in the map file on the core database that is being parsed to the display. Our terrain radar isn't dynamically scanning the earth in front of the aircraft.

Hi. A few replies in order - 1. This sounds like a config conflict. Do you have custom cameras setup or use Chaseplane? 2. The default cockpit camera is adjusted to account for the majority of monitor/POV setups, but some manual tuning (especially in VR) may be required to suit your specific use case. 3. You should be able to rotate or drag the MFD knobs CW (clockwise) as shown in the image below If this isn't occurring, you might want to reinstall the package as there is a chance something got corrupted.

I'll pass this on to the scenery team. Thanks for the insight

This should be resolved in the latest update from Feb 7th.

HI all. We are investigating this and will report back on what we suspect is the cause.

I'll pass this on to the art team and ask if they can provide some guidance.

Thanks. I will pass these recommendations to the art team and they can see if its possible once they have time.

Looking into the exact spot right now but another suggestion I can offer is to delete your associated navigraph tokens from their website? go here and delete anything that say OIS of inibuilds and relaunch the aircraft. That should allow you to log in again.

This is a new one. Have you tried a reinstall yet?

Is this a specific SID or just custom points out of EGFF?

Hi, this is due to the way LNAV calculations are factored with assumed speed at 250kias. It should settle into staright lines once you takeoff and are at slower speeds. Can you share the departure procedure so we can take a deeper look on our end?