benlong

This problem continues to occur in version 1.1.8

Here is another example that is maybe a bit clearer: VEDVO was selected, then INSERT NEXT WPT, then "5" was entered. The expected behaviour is that a waypoint, along the track from VEDVO to SEGPO, 5NM from VEDVO, is created. This would be generated as something like "PD01". It worked perfectly in 1.1.6. However, as seen in this example, a PD waypoint is inserted before VEDVO [in the TMPY F-PLN], and although it is 5NM from VEDVO, it is 5NM from VEDVO on the track between RAMEN and VEDVO (the preceding waypoint). Hope this helps.

In ver. 1.1.6, PD [aka along-track] waypoints worked as expected as per A350 syntax, wherein typing a number (7 [or +7], -7) would place a user-created waypoint the specified distance from the selected waypoint, either ahead or behind the waypoint (on track) depending on where a positive or negative value is entered. In version 1.1.7, this function seems to have experienced a regression; wherein it no longer works at all. When creating a PD waypoint, a waypoint is created the specified distance from the selected waypoint, but is generated on the track from the preceding waypoint and is sequenced behind the specified waypoint. The attached video should clarify what I mean. When “7” is entered as the next waypoint from SIERA, a waypoint 7 nautical miles, on the track from SIERA, should be created. Instead, a waypoint 7 nautical miles is created from SIERA but on the track between the preceding waypoints, and is sequenced behind the selected waypoint where it is meant to go in front of. Again, this all worked perfectly in ver. 1.1.6, perhaps a fix could be included in the next hotfix 🙏 Microsoft_Flight_Simulator_2024_-_1.6.29.0_2025-11-23_22-12-32.mov

There seems to be a regression in the latest update as this is now broken and there’s now no way to do a PD waypoint at all. As with previous, you’re right, I wasn’t aware that the A350 is simply +/- then a number to generate a PD. Either way, it no longer works no matter what you try. Microsoft_Flight_Simulator_2024_-_1.6.29.0_2025-11-23_22-12-32.mov

See attached video. They used to work (albeit in negative form only, ie AKLON/-31). Using SU3, latest navdata, v1.1.5. Microsoft Flight Simulator 2024 - 1.5.27.0 2025-09-17 04-24-21 (1).mp4

I've managed to resolve this for now. I removed the SU2 beta, launched into the aircraft (with a fresh WASM folder) in SU1 which then had no issues, so I reinstalled the SU2 beta, and the issue has gone away. UPDATE: Now the aircraft has bricked again and the issue has returned no matter how many times I delete and reinstall the SU2 beta. I've had some friends report having the same issue. Looks like the aircraft is unusable at Nadi for now.

I'm not sure if this helps - this might be similar to the issue I was happening. The OIS remains functioning, so you can still import Simbrief and set payload. But of course as WASM has failed all other aircraft systems will not work. I tried clearing WASM, enabling autosave, then reloading and the same issue occurred. I even tried forcing an autosave folder into the Work folder but this did not help.

Hi, Aircraft: A350-900 Simulator: MSFS24 Navdata Method: Occurs with SIM DEFAULT and NAVIGRAPH OFP: N/A WASM Error: WASM: Varget of NONE in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0x00000004 Specs: AMD 5 5600X, Nvidia RTX 3060, 32GB DDR4 3600MHz RAM No autosave folder could be found in the Work folder. Details When spawning on any airport at Fiji, regardless of scenery installed, the above WASM issue occurs. If performance mode is ON, the NLG is invisible. If automatic cover removal is ON, the covers are not automatically removed. The aircraft does not work, screens do not turn on and GPU is unable to be used, regardless of how much time is elapsed. Actions taken without success: cleared community folder, cleared WASM folder (WASM issue reoccurs each time you try and respawn in and around NFFN), cleared scenery index, changed liveries, removed all liveries, reinstalled aircraft, disabled Oceania World Update, disabled photogrammetry, changed default panel state, turned performance mode back to ON, restarted flight, removed Navigraph and associated navdata, removed all GSX profiles. The aircraft has no issues at any other airport, that I have experienced. Interestingly, the issue occurs not just at NFFN (also occurs at other airports around Fiji) and happens irrespective of whether scenery is installed or if the World Update is used. Regards, Ben