iniSteven

So what I'm asking is did the plane fly within RNP .3nm or did it deviate too far? For clarity the radius of that curve is approx .1nm, so again it depends on what exactly is in the database the aircraft is reading from, but for that specific leg it's within the approach specifications. Did you actually fly the approach?

I'd be curious what the leg is coded as in the Navigraph database, as what is depicted on the chart is not always what actually gets exported into the database - I will take a look. Regarding the actual approach, did the aircraft fly the procedure within acceptable limits?

Hi, this is correct - these gates are a hastily constructed concourse meant to replace Terminal 2; which was demolished last year to make room for the construction of the new Terminal 1.

Most likely you had the aircraft selected on the free flight screen when trying to update. It would be nice if the sim could give a warning notifying this when you try to install, but naturally it can't update an aircraft that's currently loaded!

You do not need to switch cockpit interactions to legacy, I use lock mode and am able to push and pull knobs without issue. You just need keys bound to COCKPIT INTERACTION - SECONDARY and TERTIARY ACTION. -Steven

As per the real aircraft, the IAS and MACH modes on the MCP are Pitch modes - they will pitch the aircraft to hold a selected IAS or MACH speed while the throttles are operated manually to adjust climb/descent rate. Again as per the real aircraft, AT mode can only hold an IAS dialed into the window, and TM mode can only hold the Mach value calculated by the PMS. If you want to hold a specific mach value, you have to do it via entering the corresponding IAS in AT mode.

Mach is a pitch mode, not an autothrottle mode. You can only hold a mach speed in cruise with the autothrottle by using "TM" mode through the PMS. The standard AT mode can only hold an indicated airspeed.

Hi Florian, the lights are all working on our end (and various screenshots posted on our discord also confirm that this is not a universal issue) so this is most likely caused by a conflicting addon on your end. I would start by loading the A350 with a clean community folder and seeing if the issue persists.

Hi, in my testing on a 5080 VRAM usage at detailed sceneries was around 12-13gb. What are you seeing on your system?

Please don't report bugs that occur when loading an autosave from a previous version. As the previous version had an error causing DES mode to activate prematurely, it's likely the descent flag had already been triggered and this was baked into the save. We did multiple full flights in 1.2.4 testing both the cruise step descent behavior and the final descent behavior.

Hi, this is what I have from art: We have confirmed the wing livery model provided in our paintkit is working as intended. Please make sure you are using the livery template project provided in the paintkit as it already contains the necessary models to create a livery. Open the xml inside the project with the latest version of the sdk and follow the instructions inside the readme to make your livery. If you are unsure on how to use this template project please refer to the sdk documentation. There is no need to use a model from one of our custom liveries Please make sure as well that your "A343_WINGREG_ALBD.PNG" is a transparent png file and not an opaque one

Having this many simconnect events (one for each pixel the mouse moves) is going to be a huge problem. Simconnect has trouble handling even double-click events like the Autopilot Disconnect, so I doubt this would even work. Plus, having this many events would significantly increase the chances of Simconnect crashing/hanging entirely.

The OIS is a JS gauge - all the rest are core avionics and are part of the WASM package.

It's not possible at this time. Popped out WASM gauges cannot receive mouse click or scroll events, so it is impossible to make them clickable.

It means that it's not something we even can plan because it's not a decision we can make.