frank_m

That's completely nonsense. The 576x are running better than 572, have a look in the MS forum.

Just deactivate the Autopilot, then everything works.

I have absolutely no clue what you are talking about. Which toolbar?

Due to the serious security vulnerability in all drivers below 576.x, a downgrade is no alternative.

Same happened today at EDDM for me.

I have also a quest3, a 7900x and a 4080. 30 FPS are always possible, 36 is somtimes hard in VR on complex airports. Im using high settings with DLSS4. It is crucial to keep the VRAM usage under the limit. Nothing else kills the FPS like full VRAM. Therefore I'm using the low-res textures.

Sorry for the late reply. A typical manifest.json of an addon: { "dependencies": [], "content_type": "SCENERY", "title": "SimDocks_EDHI", "manufacturer": "", "creator": "Manfred Siedler", "package_version": "0.1.0", "minimum_game_version": "1.38.2", "package_order_hint": "", "release_notes": { "neutral": { "LastUpdate": "", "OlderHistory": "" } } } You see the "package_order_hint" line? I have added one to each manifest.json in my community folder. Instead of "" you can use e.g. "CUSTOM_AIRPORT" or others, see chapter package_order_hint here: https://docs.flightsimulator.com/msfs2024/html/2_DevMode/Project_Editor/The_Project_Inspector.htm That solved for me all problems with Navigraph data in the MSFS 2024. I have no issues with STARs, SIDs or ILS at any airport and with any plane.

That is not necessary. Just request refuelling and boarding in GSX, then Fuel, Passengers and Cargo is added without any further action.

In case you are using Navigraph Navdata in MSFS2024, ALL your add-ons in your community folder need an appropriate "package_order_hint" entry in the manifest.json. See corresponding threads in the Navigraph Forum. Symptoms are missing SIDs, STARs or ILS is not working, in particular if a scenery add-on misses this entry. I have added this entry to all my add-ons, and since then it works perfect.

In principle it works via SimConnect. It is not 100% reliable.

Today, I have tested the COM1 and COM2 frequency tuning using a Python script via SimConnect. While it worked for inibuilds A320 or A330 flawlessly, for the A350 around 50% of the frequency changes failed. I used the Events "COM_STBY_RADIO_SET" and "COM_RADIO_FRACT_INC_CARRY" in order to set the radio frequency. There is no error message or similar, it just fails.

For me it was sufficient to enter a Hoppie code. Since then ATIS/METAR is working, depending on the Airport.

SU1 Beta installed?

Most likely the plane was installed in the wrong community folder. You should double check.

The same applies to Sayintention.AI.