It’s been a very perfunctory beta programme - for all, but especially for Xbox users.
The first build broke WASM and it took two weeks for a fix to be issued in a new build. This was two weeks of wasted time as many users with third party aircraft didn’t enter the beta until WASM was re-enabled.
Then we had avionics performance problems, which attracted lots of posts and discussion and turned out to be an issue that could and should have been fixed much earlier - it was a fault introduced during compiliation of the beta.
To add to this, several times we have had a somewhat absurd situation where thr survey threads don’t match up with the beta build that has been released. I regard this as very basic housekeeping that’s needed to properly collate beta test observations with each correct build.
Minimal release notes on beta builds - either the beta test observations are not being actioned - in which case the need for a new build is questionable - or changes are not being documented in any useful detail. Either state of affairs is not a satisfactory result.
It all feels quite sloppy - MSFS2020 is advertised on the store as a product optimised for Xbox but the performance of this beta suggests that this has not been the case with the latest changes. The effects on Xbox performance have been marked and with the many issue introduced - honestly, to me it has felt that we are moving backwards rather than forwards on this beta - much more time and attention is needed from MS/Asobo to get this right.
It’ becomes even more important for SU16 to be optimised for PC and Xbox when you consider the fact that many third party aircraft in MSFS2020 are not compatible with MSFS2024 - some never will be, despite all the assurances we received - and it thus becomes important for us to have MSFS2020 properly preserved to fly them in. As Xbox users are struggling with MSFS2024 performance wise, it becomes even more vital thst they have a simulator that performs adequately for all types of aircraft.
To add to all these woes, which are bad enough, the size of the update files should be a matter of serious concerns. The latest build gave me a download of over 49GB. I have a 500mb/s full fibre link but the MSFS servers caused many issues last night and it took me 12 hours of stsrts/restarts to download and install the update. An update of this size that could take hours to download is a problem waiting to happen on full release day.
All in all, this beta has been proceeding with insufficient care and attention being paid to it. One or two of the CMs keep telling us that SU 16 won’t be cancelled and will happen - but given the state of this beta and the issues associated with it currently, it would be yet another huge miscalculation to proceed without taking into account the wishes and needs of the users.
A rethink is required - this beta, if not cancelled altogether- which I still think is a better option than stubbornly releasing a product that does not afford a satisfactory/good performance for all uses - should at least be put on hold for 12 months until MSFS2024 is in a better state and more resources can be allocated to developing SU16.
Unless the serious issues with black avionics and stutters are not fixed with SU16, then it should definitely not be released. If this happens then we will have two broken Sims, and quite frankly I will just give the hobby up entirely.
Judging by the changelog, there is no sense in testing this beta build on xbox at all, since they have not fixed anything and CTDs and black avionics are still there. It actually is very disrespectful for all the beta participants - either they change nothing or they just do not share any info regarding the changes/fixes.
I personally dont think theyre focused at all on su16 for both branches (pc and console). This is just them shotgunning an update for 2020 because they promised us a decade of updates for 2020. What really worries me is the short changelogs, and the bugs added to 2020 with su16 that has not been answered and or brought up for discussion by Asobo. Really really hoping they can work on WDA (world data alignment) with the default airports matching the satellite data.
Seems like the current state of the SU16 beta is causing a higher-than-average number of people to inadvertently or allegedly contravene the code of conduct for these forums.
I can understand the level of disappointment and frustration this is causing - I’m as worried as anyone!
But we do need to be measured in our responses if we are to be listened to. In the main we have had a very good experience with MSFS Flight sim on Xbox, even though the platform is starting to show its age. Many of the third party developers now rely on sales of their aircraft to Xbox users - and have recognised the benefits of optimising them for Xbox.
We do need some help from MS/Asobo with this too though - if they conduct some QA testing on COTS Xboxes and use the results to inform their development, it would and could be a quick win for everyone - it would most likely benefit users of low and medium end PCs too.
I’ve just spent some time with the 2024 SU3 beta and flown a perfect flight (apart from my lousy landing) with the CRJ- 7, so it is possible to get a solution that works well enough for Xbox pilots - GA and commercial pilots alike.
Yes, the SU16 beta is a mess - probably through a lack of resources and if I was MS/Asobo I would pull the plug on SU16 - allowing all users to rely on SU 15 as a fallback option for incompatible aircraft, whilst concentrating on improving MSFS2024…. With a little more attention to the COTS Xbox.
Its like that on many forums now. I get the ultimate goal is to have a family friendly community but some things that do get flagged are critism that is taken negatively by users. An option to unhide the flagged post per user to user would be a great addition.
Not only is it true, but it’s a genuine reflection of how we feel. I’ve said this on the forum a while ago, around November 2016, but beta SU 15 versions 1.37.16.0/17.0 were the only ones I have been genuinely happy with the sim. However, they discontinued it because the new GDK wasn’t “allowing” flights to perform well after 7/8 hours of flights, there were major stutters making the sim un-flyable and they couldn’t figure out why. However, from personal experience, it is possible to do 6+ hours flights from handcrafted airport to handcrafted airport in the Asobo 787-10 with very minimal stutters. Cold dark with simbrief integration to final gate. So I say, yes maybe we can’t do 8+ hours in heavy duty airliners, but at least we could fly. Even if it’s not final build, let’s just have it as a beta.
Impossible to disagree with the above comments. As far as I’m aware, and I’m sure someone will correct me if I’m wrong, is that the developers have not actually made a clear statement as to their intentions with this beta and ultimately the sim itself?!
Put simply, what are they trying to achieve? What area are they looking to improve? What are they looking to implement? So far all we have seen is the sim looking FAR worse than it ever has since release and performance is also the worst that I’ve seen it. Not exactly a winning or positive combination! Not to mention 3rd party product conflicts.
Will the developers PLEASE communicate what the situation with this update is actually all about because so far, nobody has a clue.
May also be worth remembering the old saying ‘if it ain’t broke….. don’t fix it’