frank_m

Can't confirm. I'm using the A350 in SU3 without any issues. As well in VR as in Desktop mode. Of course, I deleted WASM cache after each SU3 update.

That's intended. If your system is not powerful enough to simulate all systems at 4x or 8x, it will step back to 2x. The SIM rate control in the simulator is causing trouble. Use the OIS control to set the SIM rate. Switch off time compression, and you are on 1x.

I took a closer look in the files, and you messed up several things. In particular the \inibuilds-aircraft-a350\SimObjects\Airplanes\A350\presets\inibuilds\A350-900\config\attached_objects.cfg seems to be the file from the no-cabin version, not the right one. In \inibuilds-aircraft-a350\SimObjects\Airplanes\A350\attachments\inibuilds\Function_Interior_A359_Pilot\navigation_graph\navigation_graph_pilot.cfg the position of the pilot makes no sense, it seems to be the one from the A35K.

Ok, I found it. Its the ADS-B Setting on the SURV page, which is switched off by default.

I have described it here:

I have landed the A350 1.0.10 in EDDB and EDDF, ILS worked as usual. Do you have Navigraph data installed also in the Simulator? Did you fix the package_order_hint problem for all of your add-ons? It is a known bug in Navigraph, that ILS is not working on many airports, if package_order_hint is not set for ALL add-ons properly.

Hello, Traffic is shown in the ND, but not with the ID even if it is activated. I think, I saw this already in 1.0.8: Intended bevavior (Screenshot from older version):

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.