Followed your entire process to the letter, with all the reboots, etc.
Emptied my Community folder.
Started the sim back up and loaded the C152 at KDEN. Waited and waited for it to load.
Finally had to kill MSFS with the Task Manager.
1 Like
After several tries I got this to work. And now no CTDs.
I noticed that if you have navigraph installed, when you delete the content xml and it repopulates, it turns on the default nav as true again. So I exited the sim, set it back to false, rebooted the sim and it worked! Haven’t had an issue since. 3 flights into KDEN.
That is the only thing I did differently from these steps, and until I did that, I was getting CTD. Might be a navigation conflict.
I have not navigraph installed and I had several times CTD when flying from/to flightbeam KDEN.
Its sooo strange issue because it seems the CTD ocours randomly. Im not having the issue the 100% of times, but the most of times yes.
I thought the problem was the ai traffic but lately I had a CTD without ai traffic.
Im flying the most of times with the FBW A320.
Just a heads up, version 1.0.8 has been released today on Contrail!!!
Lets hope this cures some of our issues and we all can enjoy this great add-on airport!
1 Like
Lets see when the update will be available in the MSFS marketplace 
1 Like
Well, I was hopeful to be able to operate the A320NX mod out of this airport without any issues but it still seems as if some kind of issue crops up when the two combine… Loaded in just fine but as soon as I started powering up the aircraft it crashed. Something going on with these two. Will try again at some point.
Flightbeam KDEN (most updated as of Sep 17, 2021) I have run 8 full flight tests from at least 100 miles away, and landing on KDEN Runway 7 and 8 instantly trigger CTD. Not sure what the problem is.
2 Likes
I didn’t think this was a problem for me, but discovered it recently now too. I’m still on 1.07 from the marketplace though
I tried a flight again yesterday and all went well, thankfully. Using the latest version 1.0.8 of the airport with the latest development version of the A320NX after their 0.7.0 release. Development version 74045fb5eb77b3043f816d8d26028c33fb63bfd4, 2021-09-19T20:59:10+00:00.
7R ILS is still 5 degrees high though 
Did you start at KDEN or did you just fly into it. I can fly into it now, but on the start up process had a couple lags then CTD at the gate
Again I’m still awaiting 1.08
I started there. Loaded into the United maintenance pad, powered up and sat there for like 20 minutes on APU. I got a little sidetracked taking screenshots lol.
1 Like
I am getting the CTD on approach. But when I load at the airport it does not CTD. This is with version 1.0.8.
What runway? What aircraft?
FBW with runway 16L.
1 Like
Perhaps try to use the latest development version of the A320 if you’re not using it. Perhaps you’re using the stable build 0.7.0? Right now the latest version was released 2021-09-21T04:28:49+00:00 SHA 5aa13749c38b71725802d104a32d44d4141e5088
It gets usually two updates per day…
Make sure you don’t have the marketplace version still installed if by chance at one time you installed it?
You can delete it from content manager in game and then verify it is removed by looking in Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official for the folder named flybywire-aircraft-a320-neo
While you’re at it if you are using the development version you can try a reinstall of it. Manually delete the folder flybywire-aircraft-a320-neo in the community directory Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community
Then delete the content.xml located in Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Deleting the content.xml is from what I gather a good thing to do when uninstalling add-ons because it has been noted in the past where users are uninstalling mods either manually or via content manager that references remain in the content.xml. Perhaps this can cause a conflict.
Furthermore, browse to the following directory Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\flybywire-aircraft-a320-neo and delete everything except the work folder and the ThrottleConfiguration.ini
Clear recycle bin.
Run the FBW installer then download/install latest development version.
Reboot PC and try again.
Do you have any add-ons for any surrounding airports?
You can try to reinstall the airport to rule out any possible corrupted files? And in doing so also
you could delete and rebuild scenery cache while you’re at it if you have it enabled.
Are you by chance using navigraph airac?
I haven’t done any flights inbound to 16L. If I get a chance later I might try it. Some users have reported in the past getting a CTD landing at one runway while no problems at all landing at another. So it’s up in the air… 
So, as of tonight I guess it is still hit and miss with this airport especially when using the FBW A320NX… Last night I had a nice time with it with no issues but tonight it crashed the sim. I decided to go and try out 16L and so I set up a flight from cold and dark, programed in a 16L DEP/ARR and as soon as the engines started spooling up the sim locked up and I got the error window saying Microsoft Flight Simulator not Responding. Worked just fine last night and the only difference tonight was I updated the FBW Mod through the installer and programed in the 16L. Another thing I noticed tonight that I have never noticed in the past, taking quite a few screenshots while at this airport mind you is that the static traffic scenery textures where pink but when I zoomed in they loaded in, zoom back out to normal zoom and they turned pink again…
I suppose it is all up in the air here or rather should I say, grounded for now… I might have to start flying another aircraft or two more routinely out of this airport to see if any crashes occur. I don’t fly any other aircraft out of this airport often enough to rule out an issue with the airport, A320NX or a combination of both.
I wanted to give it one more go just to see, but this time again resulted in the simulator not responding.
Another thing I noticed was that this time around there were no static aircraft loaded in at the spots they were at during the previous attempt. On the previous flight when I zoomed in on them and the textures loaded in it didn’t look like the standard AI liveries but real world liveries. Honestly right now I can’t remember if I have ever seen real world statics used at this airport or not, can anyone confirm if the airport has statics with real liveries around the airport? Is this a possible culprit to the random crashes people are experiencing? I have Flightbeam’s KPDX and that airport has static elements with real world liveries.
This time I wasn’t even able to make it to programing the flight before it crashed.
1 Like
I used to fly often from/to Flightbeam KDEN and I have never seen real world static planes like, for example, in Flightbeam KPDX (I also have the airport).
I said “used to fly” because Now I prefer to fly from/to another destinations due the CTD problems in KDEN 
I have installed the v1.0.7 version and still waiting for the v1.0.8 version in the MSFS marketplace.
I hope the Flightbeam KDEN CTD issue can be solved soon. Is by far my favoritte airport… its just awesome.
2 Likes
It’s probably safe to say that even the latest version 1.0.8 is still having issues. Sadly for @eduio13 and others that have purchased through the marketplace are not going to be assured 1.0.8 is even going to work for them by the time they get it, when 1.0.8 is crashing for people currently. Is 1.0.9 going to work?
So tonight I did some more test flights with various other aircraft and with all the ones I used it crashed every time. Particularly with the last few tests it was interesting to get a crash in the same place and at the same moment upon getting close to an area I wanted to take a screenshot of.
Second to last flight tonight I decided to try a helicopter mod and use it to fly around low and slow to look at the airport and I noticed an issue with the terrain on the northern side. As soon as I got close to it the sim crashed. Note that I do not have Asobo KDEN installed and don’t have scenery cache enabled anymore. I see no difference in performance so I might as well not use it since problems tend to crop up from it when updated content comes out. So, after this crash I rebooted again and loaded back in and took the DA40 this time. I taxied over to the area where the terrain issue is present and then parked the aircraft about 150 yards from it then took the free camera over to this area and right after I took a screen shot the sim crashed again…
Hopefully another update can finally resolve peoples crashing. And I feel for the ones that are going to be waiting for close to another month before they can use this airport as intended…
1 Like
Yes, all of us that have purchased the airport via MSFS marketplace will be one step away from those that purchased it directly from the developer.
Asoblo should fix the marketplace, it feels completely abandoned.