PC - CTD both Safe Mode and Normal Location Specific (Washington DC Mall)

No I will try that later. I have only tried all over Europe and around Greece. I did find that a couple of Marketplace airports failed but was OK when I uninstalled them and flew to the same generic airport, such as Southend and Brussels. So I assumed they haven’t been updated.

Lowering the LOD will NOT eliminate the CTD in this area, but as the rendering distance gets lowered, you can fly nearer to the point it will CTD. So, lowering the LOD-Radius is not a fix. As EVERYONE can reproduce this CTD, there is something wrong in the scenery or data that needs to be fixed from Asobo.

1 Like

@HXArdito Yes, That is what I want to say. I agree. Thank you.
The issue of this post is not related to the graphic settings or LOD but it is related to the specific area causing CTD. So, Asobo need to make hot fix before SU7.

The issue is somewhere in the RED DOT

The outer FP circle is the closest you can get to that center, with a Scenery LOD as low as 25, @ 2000ft

KADW-Clear_Zone

2 Likes

Flew all round Washington no CTDs. Tried to fly from KDCA to KADW CTD on loading flight. I don’t usually fly America but having no problems round Europe

A temporary solution was just identified by deleting or renaming: bldo010.cgl to bldo010.cglbakup

We did an investigation on this thread:

Asobo, please investigate.

There are several locations of bldo010.cgl
Could you please specify which directory the DC area one refers to?

Mod edit: Temporary work around for this issue
(Note it is best to always back up core sim files before changing them and try to remember to restore them to their original state prior to any updates to the sim)

go to folder

Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base-cgl\CGL\032

and remove file bldo010.cgl or rename it to say bldo010.cg.bu

3 Likes

Found it. But couldn’t hurt having the path here as well. Thanks!

Been dealing with support for three days with this, and have been sent on several wild goose chases–all having to do with imaginary things ‘wrong’ on my PC, rather than what I said up front to them which was, “Your program is bugged, here’s how to reproduce it.”

Did you add this to your zendesk ticket??

I did indeed!

Better than Zendesk – the Asobo Dev are now aware of the issue, have reproduced it, and are currently looking for a solution.

Now all we can do is wait (while we can optionally use the temporary “work around” )

2 Likes

That’s good. Zendesk is good in concept but they thwart themselves by their automated responses telling you to do things you told them you already told them you did then closing the issue thinking they’ve dealt with it.

I reported a 100% repeatable CTD with SU5, including step by step instructions on how to reproduce it, was fobbed off as mentioned and, yep you guessed it, it’s still there in SU6! Never again Zendesk!

I deleted the file, but to no avail. When I start the descent to the Washington area, the simulator crashes.
What to do then?

ThirtyMink11551

Fly somewhere else.

Make sure you deleted the CORRECT file when MSFS in NOT running.

You are the 1st to claim deleting the correct file does NOT stop the CTD’s in this area.

Try with an empty Community folder…

Did this temporary workaround worked for you? is someone else tried this with positive results?

That’s the way out I found, thank you!

Yes, Now, I can fly Washington DC area after deleting the file. But the main KDCA airport terminal buildings have disappeared. But, without terminal buildings is better than CTD.

I had previously bought a third party add on—Drezweicki’s KDCA, and I loaded it in my community folder after applying the fix. Of course that loaded all the terminals back. Not sure if there is any other add on for KDCA, but that might work for adding the terminals back at KDCA. Just a thought. Cheers.