Hi everyone,
I’m sad to leave the Beta program and stop trying to help it progress. But this SU3 Beta is really causing me too many issues. I spend the little free time I have fixing problems rather than flying. Device issues, crashes, no progress in the career mode, and the lack of challengers in the Challenge League are all reasons why I prefer to enjoy Sim Update 2 instead. Maybe I’ll join the SU4 Beta later…
Enjoy your testing.
I hope SU2 is a big improvement for you, I am not sure if you were in the SU2 beta but its been a long beta, so why not enjoy the stable? 
release for a while.
You can return to beta testing anytime, as long as it’s available to new subscribers (as in joining the flighting)… it does make you tinker more than proper flying.
I am in the SU3 but I like to beta test in general as well.
Enjoy your testing.
Enjoy your flights 
instead of in the equipment room of the aircraft.
I had to leave too when my brakes decided not to work, or get assigned. went back to SU2 production, and they work, so another regression. On top of all the rest of them from SU1 not done
Sad sad sad and sad, and sad, sad, sad and sad 
I am trying to understand, how they were able to release this game? I am thinking about, to stop playing for 1 year from now. Is this for real? What kind of project is this? I use the SU2 and it has a lot of issues. Then i read SU3 has also a lot of issues.
I am not going to spend my time for reporting bugs or test a alpha/beta game. I am just trying to figure out, what to do now, to stop playing, to continue with MSFS 2020 or simply delete everything.
This is my last microsoft flight sim game. I don’t have the passion for another game from them.
I don’t understand all these crashes people are having. I haven’t had a single crash. Some of the flights I do are hours upon hours long with MSFS 2024 running at full graphics settings. Last night I did a flight that was 5 hours long.
Well, I dont have crashes, seems to works more stable now.
But the issue is the FPS drops before landing, or on the ramp etc. They mest up something with the SU2. SU1 was working best for me, no FPS drops, maybe 1-2 CTD in a week or so.
Yeah this issue I have.
I noticed if you did back to back flights with SU3 the sim would be more likely to CTD. If I started the sim, did 1 flight and then exited the sim before doing another flight it seemed the likelihood of a CTD was much less. This was my experience - ymmv.
Hello folks,
As we have said many times before, the beta builds are for testing purposes only. They are not for early access or a sneak preview of upcoming changes. If you would like to assist the development team by purposely using a pre-release build that will likely be less stable and have unexpected bugs and issues compared to the regular release build, then we encourage you to join the beta and log your feedback here on the forums. If you would prefer to use a more stable build, then please do not join the beta and remain on the regular release.
Thanks,
MSFS Team
Honestly, I think there should be a popup with a message like this on the main menu or something like that with the betas builds. Looking at Discord servers or reddit, too many people use the betas versions with a crazy amount of un-updated/unsupported things in the Community folder and then complain that the sim is not stable.
I agree but it is a two way street. When we identify bugs they should be fixed ASAP. In SU3 my controls disappear so testing is not really possible. So I have to revert to 2020 and the SU16 beta.
Hello @GlitteryGecko5,
Sim Update 3 has been released for less than five business days as of the time of this writing. Bug fixes take time and are not instantaneous. The specific issue to which you refer here has already been logged internally and is being prioritized for a future beta build. This was mentioned at the top of the release notes for yesterday’s 1.5.2.0 beta build:
We’re also investigating another top issue reported by the community (the sim only recognizes one connected peripheral), and working to fix this as soon as possible.
Thanks,
MSFS Team
Hi SeedyL,
Yes, I understand that it is early days right now and that we must be patient. Fortunately, I have 2020 to revert to to get my daily simfix. However, I cannot resist commenting that sometimes it feels as though we are in an alpha test rather than a beta test. But perhaps I am being unfair.
Gecko.
My devices are dropping out all the time t this sage I don’t know of a fix so I’m grounded
I too have dropped out of SU3 Beta. The constant CTD’s proved too much to take but the early positive reports enticed me in. I joined the SU2 Beta when testing was already well advanced and the various regular updates were always extremely stable. I guess I expected a similar level of stability with SU3. As it is the frequent crashes seem totally unpredictable with no common theme or cause.
I shall follow with interest reports of progress and if I detect some sense of stability being established, I may rejoin the experiment.
(post deleted by author)
I totally agree, and we do expect there to be bugs, but when the bugs are total show stoppers then it’s difficult to continue testing and naturally beta testers will want to leave the beta program and revert to something they can actually use, rather than wait another week for the next build.
Back when I used to beta test X-Plane, we had the ability to install the beta version for testing as well as a stable release for general use.
It would be good if we could do that with msfs too.
I had this issue too. Do you have a Bravo throttle quadrant connected?
I found the problem was that SU3b 1.5.2.0 had assigned the parking brake to a switch on the Bravo (I think it was 44, but not 100% certain) and that was causing a conflict and the brakes wouldn’t work. When I removed that binding my brakes worked as they should on the button I had manually assigned to toggle the parking brake.
The major lack of any regression testing internally before release of any update is alarming, it appears Asobo have learnt absolutely nothing in terms of what a Public Beta is supposed to represent.
The sheer amount of new areas broken in SU2 that were fine in SU1 and now with SU3 even more newly broken aspects come to light, it’s plainly not good enough.
We’re supposed to help test specific areas that have been worked on to the benefit of the developers, but instead we’re battling constant regressions because of the spaghetti code approach - it’s been this way since the first 2020 beta and nothing has changed.
The whole beta period needs a complete overhaul from top to bottom, internally they need to hire and commit to regression testing practices for every single update and not to release those updates until those regressions have been fixed internally. It’s currently a mess and as above has been for years, it’s very disappointing and as a user who wants to help it’s extremely frustrating to the point why bother!?
But this has been said time and time again in the past, our thoughts, our bug reports, our help is largely falling on deaf ears.
Hello everyone,
Asobo/Microsoft, I’m fully supporting you.
The idea was not to spark a controversy, but simply to say that the state of this beta for my use cases was not sufficient. I’m not complaining; I’ve participated in all the beta programs and fully understand the conditions. In this version, there is a set of inconveniences that prevent me from enjoying it adequately.
For me, the spirit of experimenting with software, not in a professional context, should still allow me to benefit from using it. As bugs are identified, they should be reported and workarounds found to continue using the software. Unfortunately, that’s not the case for me at this stage.
I would like to add that I fully support Asobo and Microsoft. I understand the process you are in, as I have spent my entire career in IT, from development to enterprise architecture and I remain a developer at heart. I know exactly the process you are going through.
What I find quite challenging for detecting regressions is that one either needs access to your complete test log or to the release version of the software to make comparisons. A single person cannot perfectly know the exact functioning of a version of such a vast software, so it becomes difficult to determine if something is a regression or not. Ideally, for those participating in the Beta program, it would be great to be able to launch the sim in both Release or Beta modes. This would allow for enjoyment, testing, and comparison.
I also want to take this opportunity to congratulate you on the incredible level this software has reached. I started using Flight Simulator on the Sinclair Spectrum in 1982. It drove me to obtain my PPL, Night Rating, and eventually an ATPL. Flight Simulator holds a special place for me. The studio’s closure around 2001 felt like a dagger to the heart. Imagine my excitement when 2020 was released, and now with VR, career mode, and challenges—it’s just phenomenal.
I’m sending you lots of energy to continue this saga. Best wishes, and I’ll certainly return for a future beta.
FlySafeNFast