Levant_vt

The computer is functioning normally, but the simulator has completely stopped responding. This screenshot was taken at 19:53 UTC, but the upper-center DU still shows 13:29 UTC.

Since version 1.0.9, the simulator begins to freeze after a certain period when instrument displays (DUs) are popped out into separate windows. ・I have been leaving the FO-side DU and the lower-center DU popped out in separate windows. ・So far, all freezes have occurred right before step climbs. ・In Task Manager, Flightsimulator.exe is shown as “Not Responding.” ・Once I close the popped-out DU windows, the simulator immediately becomes responsive again. All functions, including autopilot and camera controls, return to normal, but the simulation time resumes from the moment of the freeze. ・I have already updated from version 1.0.9 to 1.0.10. Environment: Windows 11 Home, Ryzen 5 7600, RTX 4060, 16GB RAM MSFS2020 Route tested: EDDF–TLPL

I was able to resolve the issue on my own. It turns out I had misunderstood the system behavior. Normally, I select the STAR and approach while still at the gate. At this point, the ILS frequency and identifier for the departure runway are displayed in the LS section of the NAVAIDS page and in the lower left of the PFD during taxi and takeoff. I mistakenly believed that it was not possible to overwrite this information with the GLS or SLS identifier and channel for the arrival runway before takeoff using the F-PLN and NAVAIDS pages, and therefore assumed that the frequency could not be changed for the entire flight. However, immediately after takeoff, the PFD and LS section of the NAVAIDS page correctly switch to display the GLS or SLS identifier and channel for the selected approach. In conclusion, it is by design that the GLS or SLS identifier and channel do not appear on the PFD and NAVAIDS page before departure. This was simply my misunderstanding. This message was originally written by a non-native English speaker and translated into English using ChatGPT.

On the NAVAIDS page under the LS section, when manually entering the approach identifier into the IDENT field or the channel number into the FREQ/CHAN field for GLS and SLS approaches, an error message saying “NAVAID NOT IN DATABASE” appears and the input is rejected. Additionally, even when selecting GLS or SLS approaches in the F-PLN page, the LS page does not auto-populate the corresponding data as it does for ILS approaches. I have already tried unlinking and relinking Navigraph, clearing the WASM folder, and uninstalling and reinstalling the add-on, but none of these steps resolved the issue. This behavior is observed on both the A350-900 and A350-1000. Tested combinations: RJTT GLS Rwy 34R A34E-23129 KSFO GLS Rwy 19R G19B-21859 RJCH RNP-Z Rwy 12 M12A-83680 RJFK RNP Rwy 34 M34A-75684 KSFO RNAV-Y Rwy 19R W19B-53533 Simulator: FS2020 Navdata Method: Navigraph AIRAC Cycle: 2504 r1 System Specs: CPU: Ryzen 5 7600 GPU: RTX 4060 RAM: 16GB Please note that this report was originally written by a non-native English speaker and translated into English using ChatGPT.