Exactly – If you did not want the CTD, the fly elsewhere where there is no CTD, and look at the pretty scenery elsewhere, now it is know where the CTD area is.
If you want to fly in the DC SFRA, then
(1) The community has found a temporary fix. (Thanks @Nirgal2776 )
(2) The community has informed Asobo, who are looking into this particular CTD issue.
(3) If you want “EMMERSION”, something that many claim to want, and get upset if their “IMMERSION” is broken, then you should be aware of the DCA SFRA which Adds to the “IMMERSION”
Lastly, I’m the Topic Author, and its my choice to add this relevant information to my thread, as an added BONUS EXTRA, now the CTD issue has been dealt with.
Read the solutions/work arounds, but before I tinker with any files pending SU7 incoming soon, just wanted to ask - would this CTD I just had after a completely smooth nearly 5hr flight be related to this issue? As soon as I crossed the river immediately southeast of Joint Base Andrews, entering my STAR to KLGA, I got a CTD at FL350. Seems a little outside the initial range update in the OP but close enough to Andrews to definitely be suspect enough to me, so just adding my information.
The flight had been completely smooth up until that point when it suddenly CTD’d without any stutters or other warnings.
Presumably this is the same issue but again, clearly well above 2000 feet. Also, will doing the fixes/deleting the file cause any problem when the SU7 update rolls out soon?
I read through the thread, just want to make sure I won’t cause an issue with the incoming update.
This certainly looks like the same issue that everyone else has experienced in this region. It will affect approaches to KDCA.
In terms of preparation for SU7, I renamed the offending file, adding a .bak to the end of the file so that it would not be read by the sim. I also have made a note to delete the .bak component of the file (i.e. restore it to original state) prior to running the update for SU7, if that helps.
The size of the CTD area depends on your Scenery LOD.
When I plotted out the area, I had a very LOW Scenery LOD, (25 ? ) as this made the area smaller, and therefore the determination of it’s center more accurate.
It appears that taking bldo010.cgl out of play removes all the terminal buildings at KLGA and leaves nothing but the jetways. Anyone else check LaGuardia? The airport returns when I restore the file. I guess it’s a trade off based on where you want to fly.
KADW is located in scenery area 0302, which covers most of the US northeast, including airports as far north as Boston, and as far west as Detroit.
It appears that the CGL folders use the same numeric naming convention as the base scenery folders, except they drop the third digit - so \0302 becomes \032