[SU6 / 1.8.14.0] Byte-for-byte reproducible CTD in CoherentUIGT when clicking Fly from the World Map

User Support Hub Install, Performance & Graphics
, ,
1

Hi all,

Hoping someone here has seen this one, because I have run out of ideas.

Symptom: Sim boots fine. World Map loads fine. Everything looks great. Then I click “Fly” and the process vanishes — no error dialog, no warning, just a clean and very efficient return to the desktop.

What changed on my end: Nothing. I flew this same setup for roughly a year without a single CTD. Then Sim Update 6 arrived on its own schedule, as updates do, and the streak ended that same evening. I appreciate the initiative — I would never have thought to test this configuration myself.

System

  • CPU: i5-13600KF
  • GPU: RTX 4070 SUPER (12GB)
  • RAM: 32GB
  • Build: 1.8.14.0 (Steam)
  • 3840x2160, DX12
  • TLOD 300 / OLOD 140
  • Developer Mode: on (yes — switching it off is next on my list)

What the crash reports say

Two separate dumps, two separate sessions, about 25 minutes apart. The callstacks are byte-for-byte identical — all 30 frames, down to the exact offsets:

10 = ["CoherentUIGT.pdb", ..., 559489]
11 = ["CoherentUIGT.pdb", ..., 560819]
12 = ["CoherentUIGT.pdb", ..., 544075]

Purpose is reported as CoherentGTImpl_Z, and the last recorded state is:

LastStates = " MainState:GAME SubState:GAME_WORLDMAP MainState:WORLDMAP SubState:WORLDMAP_HOMEPAGE"

So it dies in the UI layer, during the World Map to flight transition.

Between those two dumps I also happened to change GPU driver (591.44 to 610.88). The callstack did not move a single byte. Whatever this is, it is admirably stable — arguably the most consistently reproducible thing in my install right now.

Memory

This is the part I would genuinely like a second opinion on:

SystemMemory  = 32 GB
AllocatedMem  = 13.1 GB
PeakAllocMem  = 14.1 GB
PhysicalMem   =  7.8 GB
SwapFile      =  5.25 GB

5.25GB paged out to disk on a 32GB machine, while the sim is sitting still on a menu. I have 1365 registered packages so I accept a share of the blame here, but the resident/paged split still looks wrong to me.

Add-ons (yes, I have them)

175 community packages, all in the legacy FS2020 community folder — the FS2024 one reports 0/0. The publishing group line reads communityfolderfs20 = "165/175", so 10 of them are not loading at all. Which 10, the report declines to say. That is its own small adventure.

Four WASM modules are live at crash time:

  • fcr_embedded_system.wasm
  • fs2crew-data-proc.wasm
  • SS_WMKK_Airport_Driver.wasm
  • ImmersionModule.wasm (p42-imm-simfx)

Plus an external SimConnect client, MSFS2020MapEnhancement, which I am eyeing with some suspicion given exactly where the crash lands.

I am fully aware the answer may be “an add-on has not caught up with SU6 yet”, and if so, fair enough — that is how this works, and clean-folder testing is my next step. But an add-on taking the entire sim down during a UI transition without so much as a log line is the part I would like to see improved. One message naming the offending package would have saved me an evening. Several evenings, at the current rate.

Questions

1. Has anyone else landed in CoherentUIGT at WORLDMAP_HOMEPAGE since SU6?

2. Is there any way to get the sim to tell me which 10 of my 175 packages failed to load, short of bisecting them by hand?

3. Is that paging behaviour normal on a 32GB system with a large package count?

Happy to upload the full MSFSReport.txt files if that helps anyone.

Thanks — and for the record, I do like this sim. That is rather the problem.