IniSteve

Hi Jason, it appears you have a corrupted installation. Can you remove and reinstall the plane and check again? Also, delete any 3rd party cabin/art mods like HUES zCore if being used ans they could cause a model conflict if not updated properly.

Hi. Testing this right now and the auto switching is working well, but for clarity, BATC doesn't support time compression, which is why you'll see errors after a while.

Hi. We look at every project independently and will make the determination at the time so I wouldn't think of anything being a permanent decision unless specifically called out in an official update.

Hi. The clickspots are a known issue brought on by some sdk changes implemented in SU5. When we look at the interactions everything is as expected but it's not working properly in the sim so we are searching for a workaround.

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?