iniSteven

Hi, if you're having a crash every time you load the aircraft then it is most likely an issue with the stability of your computer. Have you overclocked your computer at all? Are you running any other addons alongside the simulator? Other users have reported that reducing the speed of their RAM (either turning off EXPO/XMP or reducing the timings of their memory) has had a large effect on the stability of their sim. In the future, if you have a crash and you please follow the steps outlined here (especially with regards to the logging variables and they help immensely in tracking down the causes of crashes) The A350 is a complex aircraft and it is asking a lot of the simulator, unfortunately it is simply the nature of the plane that it is sensitive particularly to the stability of the memory on your PC - that said, it is one of the most flown aircraft in the simulator and so we know that it can be stable but there are a lot of variables that are beyond our control.

Hi, the update is in testing but we don't have any ETA to share at this time :)

I have loaded the A350-900 default cabin config at least a dozen times in the last week and not had this phenomenon. Can you confirm you don't have any light enhancement packages installed and that the aircraft is otherwise behaving as expected?

These artifacts are outside the boundaries of the edited terrain - just artifacts in the default photogrammetry and water mask

Hi, the different types of grass is actually accurate as some of the grass at EGLC is actually Astroturf - see the image here: As for the "why" the grass is modelled the way it is, it's because we've modelled the entire airport, including the base terrain and taxiways as a 3d object. MSFS's default terrain editing tools leave a lot to be desired, especially in areas with photogrammetry like London. In order to get around this, we've essentially placed a 'cap' on top of the terrain via a 3d model which allows much more fine adjustment of the elevation of the airport, smooth taxiways and runways, etc. The only downside is that 3d objects cannot use the same grass rendering technique as the terrain, so we've had to work around this ourselves.

You've enabled CFD visualization - you can turn it off from Settings -> Flight Interface -> Aerodynamic Visualizations

You need to restart the flight to reset these switches. I just want to clarify that just as in real life, these switches are irreversible, once they are pressed, they cannot be unpressed! In reality, it requires maintenance personnel to reset the hydraulic isolation valves on the ground manually. The pilot cannot, on the ground or in the air, reset these switches themselves.

Hi, the landing telemetry simply takes the vertical speed sim variable at the moment of touchdown - IAS, TAS, and G/S have no impact on the recorded vertical speed. Secondly, it should be expected that you will have a higher landing rate at high density altitudes. Because you are moving faster over the ground, you will also need to descend at a higher V/S in order to maintain the same geometric descent. Best, Steven

As I said, it's been noted and passed along...

You do not need to listen to the tones as an airbus pilot wether automatically or manually tuned, to be clear. Even in a Cessna with a modern GPS the navaids are automatically identified and pilots do not legally need to listen to the tones when this occurs. I have noted that the tones are not audible through the radio so I will pass that along.

Hi, we did make changes to the runways for the FS2024 version of the scenery and were able to get FSLTL to use the full length of the runway. BATC seemed to be dependent on other factors, but beyond our ability to control. Best, Steven

Hi, in the A340 and A350 there is no need under normal operation to listen to nav radio morse tones in order to identify them. They are automatically identified by the aircraft - when the LS or VOR identifier is shown on the screen, the navaid has been tuned and identified by the avionics.

Hi Mikai, regarding the GPWS sounds, there are actually several different soundsets that are used depending on the airline and specific equipment installed. We have even heard a boeing style "TWENTY-FIVE hundred" call in some recordings. The current recording are the highest quality and cleanest samples we have from an actual aircraft, so for now they are what we will stick with. Best, Steven

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.