I am experiencing a fully repeatable simulator freeze (not a crash to desktop) when flying into the Washington DC area, specifically during the River Visual approach into KDCA.
The simulator becomes completely unresponsive (image and audio freeze), requiring a force close. This occurs consistently at the same geographic location during the approach.
Reproducibility:
100% reproducible
Steps to Reproduce:
-
Fly toward KDCA using real-world routing (e.g., from cruise, not preloaded nearby)
-
Use the River Visual approach
-
Descend into the DC area following the Potomac River
-
At low altitude near central DC landmarks, the simulator freezes consistently at the same point
Observed Behavior:
-
Full simulator freeze (not CTD)
-
No error message
-
Requires force termination
-
Occurs at the same location every time
Expected Behavior:
- Stable approach and landing into KDCA without freezing
System Specifications:
-
CPU: AMD Ryzen 7 7800X3D
-
GPU: NVIDIA RTX 5070 Ti (16GB VRAM)
-
RAM: 32GB DDR5-6000
-
Storage: 2TB NVMe Gen4 SSD
Simulator / Environment:
-
Microsoft Flight Simulator 2020
-
Real-time weather enabled
-
Aircraft: Fenix A320
-
High/Ultra settings
-
No performance issues elsewhere (large hubs such as KCLT, KMIA run normally)
Installed Content in Affected Area:
-
KDCA payware scenery
-
Washington DC landmarks add-on (City Update from Asobo)
-
World Update USA installed (photogrammetry active)
Additional Notes:
-
Issue began after first flight into the area without preloading
-
Now consistently reproducible in the same location
-
Does not appear to be a general performance limitation
-
Appears tied specifically to scenery loading or streaming in the DC region
Request:
I am looking to determine if this is:
-
A known issue with Washington DC photogrammetry
-
A conflict between World Update USA and third-party landmark scenery
-
A streaming or scenery tile-related problem
If others have experienced similar freezes specifically in the DC/KDCA area, I would appreciate confirmation and any targeted solutions.
Thank you.