Do you have the same issue if you follow the OP’s steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
in my case i started the flight with the a310 at ESSA on the runway, ready for takeoff. all screens were black from the beginning. Engines were up and running. Also the EFB was black.So i Closed the sim, reloaded it and restarted the same flight at the same location: had a short flight (20mins short circuit at ESSA) and everything worked fine. will continue testing with longer flights tomorrow.
all the best.
i don t know if it could be related but immediately before i had a previous flight with the longitude at LIRF with 3rd party airport.
Using Xbox series X
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
ok, had a pair of flights LIRF-LIML and LILM-LIRF this morning with the a310 on Xbox series X. more than 2 hours each, from “battery on” to “battery off”. Everything went uneventful. No black screen, no instability issues. 3d party addons for both airports. Had a very plesant experience. will continue testing and let U know if any problem occurs.
I saw this, once, the last time I flew the A310. The brightness was turned all the way down on the tablet — even though I had not touched it nor set it that way.
My friends on Xbox are all complaining of continuous CTD from the A310 on the SU12, each reporting CTD’s at different phases of flight. I manage to do 1 or 2 flights that work perfectly, on the third flight when starting pushback, or configuring the FMC, or configuring the EFB, or looking around the aircraft is guaranteed CTD. It’s sad because it’s the best commercial aircraft that is available, in my opinion, on the Xbox.
There’s something related to memory as it has been all the time, flying from or to 3rd party airports guarantee CTD or black screens, same with flying online or with live traffic, it’ll cause the same.
I uninstalled all my airports, and I’m currently flying offline with traffic off and photogrammetry off as well. I’ve been able to complete 3 flight without issues, I’ll try flying more and report how it went
In the dev livestream last week Martial did a big section going through crash reports and their metrics analysis for the platforms. On xbox over 75% of all CTD were caused by out of memory.
Sadly it’s down to players at the moment to manage themselves how much complexity they have in the sim, and this how much memory risk they are prepared to take.
I was late to the Dev Stream and arrived shortly before the Marketplace segment.
I know they have thrown out the “out of memory” thing before, but did they give any detail as to what that really means?
A city could have enough water stored in a reservoir to serve the city for an entire summer and then some, but if they let that water leak out due to poor infrastructure, then that water isn’t enough.
Are we looking at a case of poor use of the available memory or poorly optimized add-ons or memory management issues within the sim itself or is it a case where this sim is too much for the Xbox?
Any details?
To add to this, I’ve heard it thrown around this forum that they (the devs) have said they haven’t hit the capacity of this sim on Xbox. If that’s the case, then what is the deal with the memory? If it doesn’t have enough, then you can’t say there is more to be gotten out of the Xbox.
I suspect it’s a combination of all of the above, but there was no information on relative importance of each. There were pie charts for each platform showing different crashes, on xbox there were several slices of the pie for out of memory which together added up to over 75%. For PC there were still large segments for out of memory but it totalled a lot less of the pie. They had some big segments for driver issues etc.
Martial did not explain what these slices were, my guess is it’s location of crash derived from the stack trace you’d get in a crash report. If so that only tells you where it was trying to allocate when it failed, not where all of the memory was already gone to.
Prior to SU12 there were a couple of other bugs causing a significant number of crashes on xbox but those were fixed in SU12 and now the metrics show that all significant crash causes were out of memory.
I remember the comment on a previous dev livestream that they are sure they have not reached the limit of xbox capability yet. They did not clarify further but I took this to mean that they believe optimisation on the software side is possible to enhance the game further. Clearly right now they are hitting and exceeding at least the RAM capability of the box, and from the slideshows we get they also sometimes exceed the CPU, but it’s good that they believe there is more they can improve in the software to better use what is there.
This is a rather “strange” statement from them, in my opinion? Basically they are saying ok listen we know that certain complex addons can make the Sim unstable, or even crash it but buying and use them is at your own risk because at this point we don’t have a solution for this? That’s strange.
Note that for me personally the Sim is very stable at this moment, and i recognize the work they have done to come to this point.
Edit: the dev stream hasn’t been uploaded to Youtube yet?
Just started a flight and literally just spawning the memory is already low, look how the cockpit and other textures are missing. I used to fly from any 3rd party airport in SU11 using the A310 without any problem or the memory being low at the very start of the flight. At this time i think I’m coming back to the default aircraft which works well (in performance). They really need to sort this out ASAP.
That’s pretty pertinent Nixon. Of my friends who are flying on the Xbox with the A310 giving a lot of CTD is the Series S. In the Development live, it was the champion of problems related to memory in the graphics presented there.
I just watched the Q&A. And I think the section when they talked about the stability was great. So good to see all the data they have collected and still collecting. And also it’s so good that Jorg said that stability is still their number one priority.
I used to enjoy the XBOX S and there were times in the SIM when it seemed more stable than X. I decided to move to an X to enjoy sharper cockpit and improved graphics and I wonder if these complex plane are becoming too taxing for the S. To me SU12 problem has been with World Update disappearing and reappearing in the most inconsistent manner but as far as flying the A310 and using the SIM it’s never been so good and stable. I haven’t had a black screen or a CTD in SU12 yet and I have mostly flown out of Add-on airports. If it helps I share what I do and works for me. 1. Always quit the SIM and shut down XBOX before a new flight. 2. Don’t use cache 3. Multiplayer is off but everything else is ON 4. Start A310 from Cold and Dark and follow procedures and learn how to fly it 5. I do occasionally have an external view when Pushing Back or while flying but I mostly stay in cockpit view. 6. Finally I mostly fly max 2 hours flight which is what I prefer to do anyway. No time for longer ones but so far it seems that consoles do get more CTD the longer the flights. I don’t have loads of Add-ons but I have planes I like and quite a few airports, mostly middle sized one as the largest ones so far have proven quite challenging on XBOX. Wishing all a good flight.
Your ideas to overcome the CTD’s is a workaround for what is happening with the A310. However, it is very complicated to do an average flight with a certain weight in the conscience that if I go beyond 2 hours of flight, there is a probability of having a simulator crash. I can fly 2 flights or 3 max with the A310 on the SU12 (Series S), after that it’s guaranteed CTD. It’s very complicated to fly “in handcuffs”, like, “don’t install such an addon that is a guaranteed CTD” or not “fly more than 2 hours and the console will not hold”. Well, I’ve already flown on the A310 for 10 hours on the console, I confess that I was apprehensive.
Can this get fixed soon? I really can’t even start programing the FMC because of constant CTD.
I really don’t get how instead of upgrading the performance on console it just decrease drastically smh
