KADW - Andrews - CTD Analysis by Community contributions

[N6722C]

YES !!! What has got removed by removing the file (maybe)

[HXArdito]

The ■■■■ Costco crashed our sims?

[Nirgal2776]

@N6722C

Note: Replacing that bldo010.cgl with the file from a few months ago, did not seem to cure the CTDs, but , for the time being, until Asobo does a proper fix, removing that one file would seem to allow flying back into that popular area.

i think an “autogen” building from blackshark is corrupted and by removing its footprint contains in this cgl file, the error gone. But the problem is not really in the cgl, t’hat’s why you have the ctd with the old cgl. but it is out of my skill. Only Asobo or blackshark can fix this

[Nirgal2776]

i don’t think the area affected by the missing file should be very large

[trex5365]

@HXArdito

Costco crashed our sims

I almost spit out my coffee.

Thanks @N6722C for corralling the troops.

[Nirgal2776]

@N6722C

great job all, especially @Nirgal2776

my pleasure my friend

[N6722C]

I think this is what was being corrected ?

BTW, it is EXACTLY at the Center point identified earlier !!!

[Nirgal2776]

the issue should be with the building at this place, not with elevation (contain in dem*.cgl)

[N6722C]

@trex5365

Thanks @N6722C for corralling the troops

Its great to see the Forum Community working to together in a positive way.
Amazing what a group effort can achieve.

[trex5365]

Asobo, as a thought, the sim should be able to ingest bad data and tolerate it. It should not CTD for this kind of error.

[Nirgal2776]

handling error is always difficult in such a huge program with millions of code line. i don’t blame them for it, i’m a c++ dev and i know how it can be easy to make a mistake, even in a small software.
But at least, they should listen the community to fix issue. they seem so deaf to information feedback…

[N6722C]

And some entry in the Dev Console log would have possibly saved everyone a lot of time and effort ( Including Asobo in the future)

[HXArdito]

Yup, great job guys! That was well executed investigative work!

Now a mod has to pass it to Asobo please, because id assume it will be relatively easy for them to identify the issue.

[trex5365]

@Nirgal2776

they seem so deaf to information feedback…

I agree with your point in general. I don’t think they’re deaf… I think their agile development roadmap is too long.

Maybe six mons initial launch delay might have had the MVP and subsequent releases in a very different place.

[Nirgal2776]

@N6722C

I did rebuild the layout.json ( do not know how really necessary that is )

i didn’t have to and it works, so it should not be mandatory

[trex5365]

@tamalien can this thread be escalated to Asobo? 100% reproducible CTD has been isolated and workaround identified.

[N6722C]

@Nirgal2776

handling error is always difficult in such a huge program with millions of code line. i don’t blame them for it, i’m a c++ dev and i know how it can be easy to make a mistake, even in a small software.
But at least, they should listen the community to fix issue. they seem so deaf to information feedback…

What surprise (and upsets me) is to see all the error messages in the Dev Console log, day after day, week after week, Month after month, Revision after Revision, and no attempts to correct what seem to be very basic errors.

This is the low hanging fruit - errors that are being flagged, often in detail, and should be easy to fix – yet they get ignored, while more Gaming features are being piled on top of a shaky foundation, that is buckling under the strain.

[Nirgal2776]

so now you know how to do if you have the same ctd in another place. Run Procmon from syternalssuite (from Microsoft) to monitor MSFS activity and find last files accessed before the crash.

[Nirgal2776]

yes, but i remember fsx had a lot too viewable by activating error logging (i don’t remember where, in .cfg ?)

[N6722C]

How about those registry keys not found ? (not existing … seeming to have corrupted path ? . )