Have you disabled/removed all your mods and add-ons? Yes
Are you using Developer Mode or made changes in it? No
Brief description of the issue: (SERIES S) Since AA1 beta update and fix of LOD issues on xbox, the CTD and black screens have increased drastically compared to the public released version. In the public version I was able to use 3rd party addons with any aircraft and now it just CTD everytime I try to fly, even if the airport is default.
Provide Screenshot(s)/video(s) of the issue encountered: Not able to since always CTD
Detailed steps to reproduce the issue encountered: Start a flight from gate, try to program and get the aircraft ready. CTD secured 100% of the time
PC specs and/or peripheral set up if relevant: xbox controller, mouse and keyboard
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OPās steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Iām on the Xbox Series X.
Iāve noticed a big increase in CTDs too, so much so that Iāve opted out of the beta. First time Iāve had to do that.
I tried the TBM-930, Citation, and Longitude. The only way I was able to get them to work was at a stock airport with minimal scenery in the area. Instant CTD with any 3rd party airport, or hand crafted Asobo airport. I was thinking that maybe the updated avionics in these aircraft (which looked very nice btw), were causing the issue because of increased memory usage, but I donāt think thatās the case.
Tried many of my other aircraft, and the same thing was happening. CTD after CTD at any hand crafted or 3rd party airport. Everything was working after SU11, which to me was the best update weāve had. Now version 1.30.5.0 seems like a step backwards. Asobo please fix this problem before the release candidate.
Series X here. A LOT of CTDs. Usually while loading a flight. Also restarting the sim seems to take longer now so the CTDs are extra annoying. Havenāt had a CTD mid flight yet.
But, oof. Last night I had at least 3 CTDs. 2 with the Longitude. 1 with the Vision Jet.
I had one or two the day before as well, but wasnāt paying attention to what I was flying.
I receive an occasional crash to desktop on XSX but not too many. Have you reset your rolling cache to see if it makes a difference or not yet? Letās not forget that this is a beta and not the final version.
If you are experiencing CTD with the new Vision Jet, itās a known issue on the developerās discord channel.
Iām not particularly upset with them, bu lt there have been a few. Havenāt found a pattern yet as played too little to be of use. But these have involved various aircraft including (and Iām wary of naming as may not be the causal factor) A310 and C414AW. This has been at addon airport Toulouse and also at default (very) basic airport France: Puivert lfnw, and add on Yellow Pine US.
Like i say itās not been too painful as the A310 flight i hadnāt gone to the trouble of inputting a flight plan and the Yellow Pine was C414AW after shutting down the systems, following landing.
I have been lucky with CTDās on flight sim, can probably count on one hand the number Iāve had in the last year and a bit. But when I loaded into the beta in the Vision Jet I got a CTD immediately. When I reloaded, I adjusted the map detail in the MFD to show less detail (only show small towns when I zoom in a lot) and Iāve had about 6 hours of various flights in different places (big cities, small towns, heavy traffic, light traffic) and everythingās been very stable.
We talk a lot about VRAM limitations on the XBOX, I wonder if thereās also some CPU bandwidth issues. I know a big limitation of the CPU on the series consoles is very limited on board cache.
Well this issue was specifically identified in the release notes for the beta version. But at least they did mention that they were aware of the issue and working to fix it (hopefully in an āin-betaā update vs the January update).
Regards
I read an article about how Xboxās enemy is its own operating system. According to the article Microsoft is intentionally blocking XSX from reaching it is full capabilities. They can unshackle the XSX through system updates but wonāt do so. I wonder why.
I wish I could find that article myself.I did not have the time to find out why Microsoft is doing this. I will try to Google it. I will link the source here if I can find it.
To me it seems like some LOD conflict with 3rd party stuff. I have some areas like HI that has birds, cranked up traffic, the ships, etc so itās a pretty full area. No issues, coming into to even some smaller airports and getting CTDās. Seems to time out RIGHT when that last full-detail drop comes in at most airports is when it craps out. Either flying over or on approach. I will say itās fantastic having general LOD back rather than flying in the tiny bubble of āworldā that you can see beyond in every direction the public version.
I havenāt flown a ton yet on the new beta version, but in the time that I have it has certainly not been as stable as the last public version, but the crashes have been infrequent enough that Iāve still enjoyed flying it, and itās still MILES better than the disaster that was SU 9. One thing I notice is that there is a lot of audio crackling and glitching happening, even while the sim is initially loading. These audio crackles and dropouts have always been a sign that the sim was close to crashing.
All of that said, the restoration of much of the scenery detail on the XBOX version has been fantastic and going backward again on image quality in order to chase performance issues is a non-starter as far as Iām concerned. Image quality is what sets this sim apart, so it should be non-negotiable. Water it down and we might as well just use X-Plane. I would actually rather have a crash here and there than go back to the extremely dumbed down image quality that we had to endure prior to this update.
If excellent image quality with at least acceptable performance canāt be achieved on XBOX (even though we had both with SU 7 - another story) then Iād rather shelve the sim until Microsoft releases a mid-gen update to the console or just switch to PC. In fact, if Microsoft is truly serious about making this title a standout exclusive on XBOX, then they really need to release a āSuper Series Xā as soon as possible. Iād be willing to pay a premium for one right now if it was available.
I play on the series x
I find I can load any aircraft from any airport on a fresh full boot of the game.
The first few flights are usually ok.
If I have to go to the xbox dashboard then I am assured of a crash in the next hour or so.
Quick resume generally is very unstable, although once in a while I can get an hour or so in before the inevitable crash.
Still love playing the game, nothing else has had a look in really apart from Elden Ring on PS5.
I do know for a fact that all console games are subject to a list called either TRC or TCR from either Sony or Microsoft that they have to pass before being released. This list includes length of loading screens, stability, quality of UI etc, and even at itās most stable this game should fail - more surprising when itās Microsoftās own baby.
Seems a bit unfair to any other developers who may have their releases delayed while they satisfy all the points on said list.
I also worry about all the crashes and overheating cooking hardware - that must be a concern for Asobo - as a player I donāt want to know as ignorance is bliss, but I do wonder, perhaps from a scientific point of view, if anyone has had hardware failure due to CTDs etc?
Maybe what is needed at this point for the Xbox is an option for LOD. Those who have a lot of 3rd party content can have better performance, and those that want better image quality can have that as well. It seems that there isnāt enough memory to have both, so under the circumstances a choice would be nice. Sim update 11 arguably may have gone too far for performance, while this latest version in the beta may have gone too far for visuals. If a balance canāt be achieved, leave it up to the individual user.