Cockpit freeze when selecting ILS approach into SPJC

[WernerAir]

I would like to report a WASM crash that leads to the whole cockpit freezing - no control elements can be manipulated any more, although the simulator continues and the aircraft remains in flight. Control over the cockpit elements returns only after going to the main menu and spawning a new flight. Similar reports have been made by others concerning other airports, but I have now stumbled upon this when trying to fly to SPJC.

How to reproduce: Spawn anywhere and plan a flight to SPJC. Then, in the FMS, select arrival for SPJC and choose any one of the ILS approaches. Freezing is immediate and won't allow you even to choose a STAR. If you choose one of the RNAV approaches instead, everything works fine.

This problem affects the A320neoV2, the A321LR, and the A330-200. I have also tested the A310-300 and the A350, but they are not affected (it seems that the FMS / Navdata works differently on these aircraft.

• Aircraft: A321LR (but happens also on A320neo and A330
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: not necessary - happens whenever you load an ILS approach into SPJC, even if you are in the air at the time
• WASM Error 1: WASM: Error during FMGS_gauge_update execution. Error code : 0xc000001d
• WASM Error 2: WASM: Module vfs://microsoft-aircraft-a321/SimObjects/Airplanes/microsoft-a321/attachments/inibuilds/Function_Interior/panel/inibuilds-A321.wasm is now dirty
• Specs: AMD Ryzen 7 9800X3D; NVIDIA GeForce RTX 5070 Ti; 32 GB RAM
• Autosave File:  none available

I am using the Low-End PC SPJC scenery V2 for MSFS2024, but I don't think the issue has anything to do with the scenery as I am sometimes even thousands of miles away when this happens.

I'm looking forward to any insight you might give me as to why this happens or how to prevent it...

Cheers!

Edited Saturday at 09:01 PM by WernerAir
Typos