Isn’t a well-defined hardware standard one of the key advantages of consoles, meaning (presumably) that software can be made very stable when the variable of different hardware is removed?
I think the subject says it all. To me, as someone that has fought CTDs on my PC since day 1, I’m actually encouraged that Xbox users are also experiencing CTDs. For those of us on PCs that have tried every suggested fix out there, it gives me a little hope that maybe it isn’t my PC, and the software really is the problem. I can only hope, because I’m exhausted and frustrated.
I was thinking along the same lines. I would assume that developing for two configuration X and S should be way easier and give a much more consistent experience compared to all the variables that can cause conflicts and issues in a PC setup… Of course Xbox is newer and needs refining but still. Not a programmer or an expert but from what I read in this forum a lot of the issues could be from the servers too or download speeds because as a Xbox simmer I often find other Xbox having crashes that I don’t experience which would seem weird given they are the same machine running the same software ( provided add-ons are not installed )
For over a year I have been doing my best to wrap my head around a number of these CTD issues. There are a good number that will not go away until “some” users recognize that they are their own worst enemy as they refuse to accept that many CTDs ARE system/configuration problems.
Don’t take that to mean all CTD are the users fault. There are some that defy reason. What you are pointing at is one that I believe is the result of data corruption, not code errors. I have been experimenting with a couple of friends that have unexplained CTD’s. One in the central US, one in Australia and one in Canada. The user in Canada is running on XBox X.
Seems they can all fly without CTD if they do it offline. Online, even with settings dialed back they cannot manage more than an hour or so before getting booted. All have decent internet connections, the user in Canada is running a 1 gig fibre connection. Interestingly, we have run some network tracking and see a stream of dropped packets and retries leading to the CTDs. Not sure where the disconnect is happening. Azure servers or somewhere else but the correlation is nearly indisputable.
If you are experiencing CTD, I strongly suggest testing your offline stability. If you still CTD, then a hard look at configuration may be needed. Otherwise you may also be one of those that are experiencing online data corruption.
EDIT:
As @Salem978 pointed out, there are definitely some issues with specific locations. Some have been identified and solved. Some have been identified and all you can do is avoid them. Some are not identified and those are causing what appear to be random CTDs because users report, “This piece of XXXX constantly crashes!”, instead off actually offering some usable information.
Location errors rely on quality info from those affected. When that happens, there are some meticulous users that are very good at tracking it down and presenting it to Asobo. When they do that, it generally gets fixed.
For me it has never been the software as it is so to speak, just parts of it.
1st, I like the old style Cessna and sightseeing on short flights, much more than an hour is rare.
That eliminates a ton of problems right off, long flight crashes, G-1000 issues and even loading the landing airport as much of the time it’s already there.
I’ve come to accept the Atlanta, GA area is a slideshow crash causer as well as the DC area even more so. Several times I thought the sim was having an issue and eventually something as simple as starting from a different parking space loaded it up fine.
There are also parts of the planet that look bad but every available source has bad pictures of it so it is what it is.
Also … some of the base code was written when the 360 was the XBox