Hello guys! In my perception, it’s not straight related to the time of the flight, but to how long the route go through high traffic and places with lots of details.
I was able to make two flights without having problems for more than 2,5 hours. One through the desert and the other one through the ocean.
I also have the perception that when it happens, the CTD is coming soon.
Yes, I’m flying the a320n and I am also getting the screens going black followed shortly by the game crashing and going the xbox home screen, thats 2 flights today both at about the 2 1/2hr mark.
I do notice that its at about 20mls out and just before finals into landing
So far I have made 4 flights after the update without CTD from 44min to 2.5 hours flights. (A320) and no black screen either at the beginning of Mfs but since I stopped making the checklist I haven’t had a black screen for over 90 flight hours with a320. try it without a checklist.
Here on Xbox Series S I’m having the same problem (wifi only connection)
I’ve seen this issue at least with the Cessna 172 and A320 neo. It takes around 1 to 4 hours of constant flying to occur and the A320 is somehow more problematic. I have yet to fly a leg on this plane without this issue. Even basic 1 hour trips from LAX so SFO have never been successful for me.
Somehow this bug shows earlier when (live) traffic is enabled. When disabled it takes a few hours, like 2 to 4 to black out all the avionics. Even the small displays on the FCU are gone. But I like flying with traffic, feels so empty in the world when you’re the only plane in the air.
Shutting everything down and restarting the engine midflight doesn’t bring back the displays. The autopilot freaks out sometimes and is mostly uncontrollable.
The simulator CTD after some time when this bug happens. Either exactly on touchdown or during flight. I’ve never seen a recovery or normal behaviour afterwards.
Could be a memory leak or networking-problems. In the end, all the displays are actually websites with java script and this could be the memory hog here.
I think it’s just that the simulator isn’t quite there yet on the console. There are bugs here and there. The updates don’t bring anything at all whether it’s on the flight system or the photogrammetry. The simulator is identical to its release on July 27th with many crashes. Apart from all the system bugs, the most recurrent problem despite the help they have provided is the simulator crashing. For my part there are only discovery flights that have no problems but if you create one, all the problems are displayed. I just wonder how long we’ll have to wait, because when we had to buy the simulator, the console and the gadgets that go with it, we didn’t spend any money.
Unfortunately, the majority of the users do . And I have tested every case in this issue on both the x and s series and the screens do go black . This is a logged bug and is being investigated and worked on .
For what it’s worth. I tried out a longish (for me) flight this morning in the A320Neo at 4hrs 20min, EGPF to GCRR. I did it to see where my XBox X was at re long flights, as I usually stick to sub 2hr ones, especially after reading about the various problems people encounter with black screens, CTD’s etc.
Well strangely I managed to do the whole trip, and whilst encountering some of the more usual FS2020 bugs along the way (including the really annoying complete loss of audio for ATC for most of flight), I made it into GCRR with full avionics screens intact & active (no black screens observed) - much to my surprise I have to add.
Now since I have the same XBox series X hardware as others, the only possible other factors may be -
It was only a 4hr 20min flight so not THAT long relatively speaking
I have set a 40GB cache instead of the default 8GB (maybe this helps? dunno)
The route had very low air traffic density about compared to others (I had live traffic/live weather enabled, not much weather at destination though)
The route involved a lot of travel over seas (maybe not caching as much land scenery?)
Destination was not particularly dense scenery wise (low density, small island, low traffic airport)
Maybe done at a quieter server time of day? Friday morning 8am->1pm (ish) BST.
Just an FYI to anyone interested. I may try another 4+ hr flight again to a more dense area.
Will give it a try next. Like I said neither start nor finish nor inbetween was scenery or traffic heavy today. I guess flying Germany to Heathrow you get scenery, busy traffic, lots of airports, cities and then end up flying into one of the most heavy scenic city/airport combos out there - definitely more resource heavy. Will give it a go sometime soon and report back. I do remember doing Paris to Heathrow not that long after XBox launch and seeing a big framerate drop on Heathrow approach.
Nightflying is finally back on teh agenda tonight after today’s hotfix though!
Just completed a 1hr 20min evening flight in A320 Neo from Munich EDDM to Heathrow EGLL and had no avionics malfunctions or black screens or CTD’s. I did have some serious frame rate issues banking whilst oriented north towards London from a southern approach (probably single digit frame rates at times, where I though XBox may CTD but it didn’t). I find that during these phases its best to change my view to the PFD’s instead, not sure that helps framerates but it helps my vision! I lined up ok with runway 27L and framerates for ILS into Heathrow itself seemed quite acceptable.
Notes:
I have just installed the latest hotfix (17/9) and completely wiped clean my 40GB sized cache prior to this flight, I usually do after any updates though. Other than that, Live Traffic was On, ATC was busy (& stayed audible) and Live weather was On, but skies were clear around London tonight. Again all on an XBox X with latest updates etc. all running at 4K.