ZERO improvement from the last builds RE: Xbox performance degradation with certain aircraft. The issue still very much exists, and somehow feels ever worse now.
Black Square TBM (w/ PMS50 GTN750) again became an absolutely unusable slow-motion stuttering mess almost immediately upon activating the avionics master switch. Performance smooths out somewhat when not on the GTN750’s map display. I couldn’t bring myself to even try anymore and abandoned the flight. This aircraft performs FLAWLESSLY in the SU15 public build.
Menus and world map are atrociously laggy and slow.
The vague one line release note for this build also doesn’t inspire confidence… Historically this indicates they feel the build is nearing ready for release. IT IS NOT. Please do not release this to the public in this state unless you want an absolute disaster on your hands. There is MUCH work left to be done to correct these major performance regressions introduced on Xbox and to polish the build, and there is certainly no rush to get this out of the gate.
EDIT: I’ve left the beta again. If I only have a short time left to enjoy a smooth and pleasant experience with the sim in the aircraft I paid a lot of money for, I’m going to do just that.
I agree with all of this.
I have reluctantly decided to leave this beta but for my own reasons which are:
there does not seem to have been any attempt to act on comments in the surveys - in fact, this is the first time for quite a while that survey comments are properly aligned with the current beta release. That tells a story - and it is not a good one as devs would obviously have been unable to correlate comments with a beta release - so they either haven’t even tried or have already decided to release “come what may”
despite all the comments which tend to show that issues are concentrated around the standard avionics - G1000NXI, G3000/5000, G3X, - there have been lots of updates - and performance of these systems ( and the Collins Proline) in third party aircraft even those that have been optimised for Xbox, has deteriorated significantly. Custom avionics from third party devs seem in general to perform much better. There is no sign this is even being looked at. Furthermore the release notes for the first build reference improvements/changed to two avionics variants which aren’t even in a single aircraft in MSFS2020 - Primus epic 2 and UNS1 -EW. How are we supposed to test these with no aircraft avsilable?
Whilst it is true that some third party aircraft are performing well, many aircraft with the affected avionics are not - and this list includes stock aurcraft, not just the third party add ons.
This is a total mess and it will be a PR disaster if released in this state.
I will return to the beta if there are signs that this is being investigated and we get some builds thst address reported issues - there’s no point to it otherwise.
It’s important to ensure this build performs at least as well as SU15. If there are doubts it will then please postpone for 6 months to allow proper testing - or perhaps cancel it - in current state that would be preferable.. thanks.
Begs the question ‘is this system update necessary?’
At least everything worked in su15. I’d be happy with new bing maps like we see in this beta but that’s all that has improved over SU15. Everything else has not only gone backwards but perhaps is the very worst we have experienced in terms of visuals, performance and working payware aircraft.
I repeat that the beta started off very positively and severely went backwards with the build that introduced a fix for WASM.
I would echo the above comment that this is very far from acceptable in its current guise. There is no hurry to release this update if AT ALL!!!
Not too happy with the performance overall, it’s noticeably worse than the public build, especially in third party planes, and there are barely any visual improvements. In fact, I see large blurry tiles on the ground where the PG details should have been.
Anyway, performance-wise, it’s not in a good place right now, same for visuals.
For most of us on Xbox, 2020 is the only way we can successfully complete a flight at the moment, as 24 is in such a mess, beta and non beta. Please don’t release SU16 until it is fully ready, as we won’t have a properly working SIM at all otherwise.
The only reason so many people join the 24 beta is because SU2 is virtually unplayable 75% of the time, so everyone wants to try the beta to see if there are any improvements, as they want a trouble free flying experience.
Did a few flights already with PMDG 737 and 777F.
The 737 was performing very well in the public build since its (737s) release. In the beta it is stuttering and goes into slow-motion on final and landing, even on small, default (not handcrafted) airports. That, in my opinion is unacceptable in a flight sim. I have been flying the PMDG 737 since its release on Xbox and before I joined beta I could be 100% sure I will have a smooth, high FPS experience every time I was flying to any default and relatively small airport (e.g. LEIB). Even most handcrafted airports were ok and super smooth unless it was something huge like KJFK or very poorly optimized. In the beta most airports, big or small, give stutters on landing.
I also had some CTDs and black avionics in some areas - I could not finish a single flight over the Alps near Switzerland / northern Italy in the 1.39.4.0 and 1.39.5.0. The last build that was stable for me was 1.39.2.0.
I’m not sure what kind of issues you are facing with the SU2 public build as it runs as expected for me, no problems at all. I do however fly in Free Flight only. MP, live weather, live traffic, and all those goods enabled.
Anyway, back on topic: SU16 beta is not great ATM, SU15 is okayish.
I hope they take their time with SU16 - I really want 2020 to be as close to perfection as possible because 2024 is a sad and broken mess.
Unfortunately I have to agree, looking at the MSFS 2024 and all the unfixed bugs and issues with the 2020, I have 0 confidence in Asobo/MS at this moment and this beta keeps getting worse with each build. Just had another CTD approaching LESO, tried again and was able to land but got low fps and stuttering on landing which never happened before in any public builds - I fly to LESO very often and it was always super smooth. This time, not only low fps and stutters, but textures and graphics were blurry and much, much worse than in the public build…
I understand that it is a beta, but… just look at changelogs - there is no information about changes/fixes, there is no feedback from the devs and they just throw another build at us with no information about what has changed and what they expect/what they would like us to test and so on, and the bugs/issues that we have pointed out in the forums remain unfixed. What are we supposed to do with this beta?
I really hope they will take their time and not release anything until it is ready.
Hate to be that guy but it appears that devs are just pressing buttons and hoping for the best, breaking years of development from third parties so they have to reconfigure their own products which worked perfectly well beforehand. It begs the question, what are they trying to achieve? The sim ran really well! Ok, there is definitely a degradation over the years when it comes to visuals but surely just a ‘tweak’ here and there? Looks like they’re trying to re-write the whole programme going by the evidence of the builds.
It seems as though they are using the same GDK as 2024, which as we know suffers from the same issues, especially the stutters and freezes. There is something seriously wrong with the new GDK, and I don’t even think the Devs know how to fix it. That is the impression that I’m starting to get anyway, every new beta release seems to make things worse.
My friend, who’s playing on an Xbox Series S, told me that version 1.39.2.0 was running “pretty well” for him. Although he experienced some stuttering due to the GDK implementation (I’m not sure if telemetry is enabled), he was able to fly into most complex airports without any black screens - just some stuttering. He was actually impressed and excited, especially since on SU15, he couldn’t even handle heavy airports without crashing into black screens. He was expecting progress, not regression. However, with the latest update to version 1.39.5.0, he says he’s having trouble with the PMDG 737 again. Now, he’s getting constant black screens in scenarios that previously worked fine. He claims it’s impossible to fly on the current version - even the slightest thing triggers a black screen.
Thanks for your response, SheikElGebel. Indeed, but see, version 1.39.2.0 showed that it’s possible for the console to “handle everything” even if it costs FPS instead of having a complete black screen. Talking to my friend, he said he prefers “a thousand times” the loss of FPS that will improve as you leave the environment that causes the FPS loss rather than getting a black screen and losing or frustrating the flight. What I think is that the Asobo Dev’s should go back to 1.39.2.0 and see what was done well that allowed the Series S or X, for example, to have a moment of almost “glory” regarding black screens, and from there progress and not regress. Just reminding that in my humble opinion, SU16 will be the salvation for the console in these details of black screens, and the focus should be on the console. I’ve already left the console for some time and have no interest in being in the current beta compilation, as SU15 is quite stable here on my PC. But SU16 should be the improvement that was missing for the console, and in version 1.39.2.0, we saw that a “middle ground” is possible: stuttering and momentary FPS losses without the darn black screen. And who knows, maybe a mitigation of the stuttering too.
I’ve been giving SU16 a bit of a wide berth ever since the horrible menu stuttering and extreme time loss started, but from what I’ve gathered from reading the forums, black screens are becoming shockingly more common with each update of this beta
I really appreciate your answer, I don’t want to go out of the thread but for clarity I have to say, as I’ve already written somewhere, that I was forced to go to su16 because of the continuous Ctds in Su15 1.38.2.0 which didn’t allow me to play. now that in su 16 black screens and ctd have arrived I tried to go back to su15 1.38.2.0 and with great surprise I don’t know why., I would like to understand the reason, I no longer have ctd, fps are ok, only sometimes very small slowdowns but nothing serious.
So this is my experience and it’s right that the developers knows.
P.s. I’ve reset my xbox so many times and reloaded the sim that it came back virgin.
I am getting horrific stutters and black screen with 1.39.5.0, i thought it was my xbox so i did a full reset to no avail, then to find out its an update? I give up with this game.
Please provide additional information in the comment section below 
Reminder: