CTD in cruise after upgrading to v1.0.8

[abrahamchan]

I keep getting CTDs during cruise after upgrading to v1.0.8. Looks like this is already reported by a number of other users.

Are there any ways to rollback to v.10.7 for now? I cannot complete a flight properly now...
 

[Eddie]

Hello,

Unfortunately no way to roll back, no. For testing purposes, can you please try using default sim navdata and see if you can reproduce these crashes? 

Thank you and apologies for the inconvenience! 

[abrahamchan]

I had a few flights with default sim navdata and so far hasn't had any in cruise CTDs

Is this the only way to solve this for v.1.0.8?

The catch is when i use default navdata, all the initial fixes for SIDs in my usual airport of choice (VHHH) become a few thousand NMs away. No such issue if Navigraph data is used.

Is this another bug with the aircraft or more to do with FS2024 itself? interestingly with this direction, I cannot depart from VHHH after all

[SUB750T]

You guys need to rollback Nvidia driver to 572.83 the 576.XXX is broken causing FS2024 to freeze despite what plane you use or SU2 or not.

Make sure to do clean install to have this fixed.

[frank_m]

That's completely nonsense. The 576x are running better than 572, have a look in the MS forum.

[CBH]

Yes, I encountered this situation too.

I had originally planned to fly two flights over the holiday, Auckland to Brisbane and Brisbane to Melbourne. But unfortunately, I had crash issues in both flights.I used Navigraph Navdata.

Of course, I found that in both cases, the crash occurred during the 2-3 hour flight.If my cruise time is less than 2 hours, the crash will not occur. For example, I had no problems flying from Sydney to Brisbane.

Finally, the crash issue broke my WASM and I had to delete the original WASM folder to get the flight working again.