please… your location description make a quick-test unenesarry hard. Can you post the Coords and a screenshot with the VFR map enabled ? So we can easy and simple jump to the position.
In case we can realy reproduce that too, and that not with the error-message “grammar…” , then it might give the developers an intressting hint for that topic “The memory could not be read.” where we searched soooo long a reproducable situation. All what we know about these error is, that it not depends on a specific geolocation ( we tested that so often ).
Hello.
I have the same CTD since yersterday.
One flight from to UTTT to VIDP => CTD near VIDP.
Two flights from VIDP to LTFM => CTD after 1/2 hour when near LAHORE.
I think it’s near Pakistan ?
I am not in SU 10.
(Sorry for my English, I am french)
I had this CTD today when flying the Fenix A320 from LDSP to EGKK. It happened near the coast of Engeland on the KUNAV 1G STAR near waypoint KKE64. I might try the flight again tomorrow and see if I get the same CTD.
I did another flight to different airports and was able to complete the flight succesfully.
I’am not sure whether this is same reason… we have some topics, e.g. near Linz (LOWL), where only for some users the same location allways cause that error, but its not reproducable for others ( in contrast to grammar… error ).
Therefore I checked the coords and had no issue so far.
The old guesses are about the G1000, but not sure.
Ah okay, so it is most likely a problem on my end. Will try cleaning the scenery indexes, etc further.
Thank you for your help and time. Much appreciated.
If it IS the cache - then this just adds to a pattern of bad error handling. MS / Asobo NEED to implement much, much better, and more resilient handling of errors, cache corruption, etc. If there is a problem with some data in the cache, reload it, report it, and don’t crash.
I’m going to got out on a limb here, and perhaps suggest it’s in part due to them being primarily a console developer. Maybe bad habits from working on a closed platform.
That said, I’ve not read about crashing issues with the Plague Tale games, so perhaps not.
yep, as mentioned… the VCRUNTIME140.dll ( which differs to the topics main issue ) was a bit more tricky. In the post which I linked , I also mentioned a user post which mentioned steps which helped him, but not sure about the other cases ( I also linked a second case ) and whether will be helpfull in your case.
So I tried deleting the scenery indexes, content.xml, empty community folder, deleted marketplace items and finally world updates (and ofc combinations of those things)…
And still got the same CTD as the same coordinates.
Currently reinstalling the sim -100 GB to go. Yay.
Edit after reinstall: I still get a ctd in the exact same spot with a fresh install with no extra content installed - I give up this was/is painful.
