Please use this thread to provide general feedback and impressions about Microsoft Flight Simulator 2024 Sim Update 7.1 Beta (v1.9.20.0). For feedback about specific aircraft, please post in the appropriate forum topic.
If you would like to report a bug, please create a new topic (or upvote an existing topic) in the appropriate subcategory of the Sim Update 7 Beta | MSFS 2024 section of the forums. Please use the full bug report template when creating a new bug report.
On a scale of 1-10 (with 10 being smoothest), how do you rate the Performance of Microsoft Flight Simulator 2024 in this build on Xbox Series X|S and Xbox Cloud Gaming?
1
2
3
4
5
6
7
8
9
10
0voters
On a scale of 1-10 (with 10 being most stable), how do you rate the Stability of Microsoft Flight Simulator 2024 in this build on Xbox Series X|S and Xbox Cloud Gaming?
On a scale of 1-10 (with 10 being smoothest), how do you rate the Performance of Microsoft Flight Simulator 2024 in this build in Virtual Reality mode?
1
2
3
4
5
6
7
8
9
10
0voters
On a scale of 1-10 (with 10 being most stable), how do you rate the Stability of Microsoft Flight Simulator 2024 in this build in Virtual Reality mode?
I finally got the “live” version about 18 hours after release. One thing I noticed is that at some point when they updated the XBox app, it reset one of the options to automatically update your programs, so some folks had the updated version and didn’t know it until they checked. I ended up unchecking that box, and trying to update through the store, and when that didn’t work several times, I turned the auto update back on and “managed” MSFS2024 to check the version, and soon after that it started the update. So not even sure what action(s) updated it, or whether it just finally hit my system.
In any case, there’s now another “flighting” version to fix the drag issue and a couple of other things.
Regards
On ms-store, this update was available through the Xbox application and not the Microsoft Store as for the previous updates. Same happened with the 1.9.18.0.
Did my usual test flight in the Extra 330LT from London City to Heathrow. I experienced an unexpected glitch in that my X.56 HOTAS disconnected early in the first flight (stick only, throttle and rudder pedals still working). I setup a new flight and that issue had corrected itself.
I was then able to complete my normal test flight. In the only flight I did on 1.9.18.0 (SU7) I knew in advance there was a drag issue, and I found the Extra to fly a little differently than usual - e.g. it would sustain an overspeed condition in level flight. Those behaviours seemed to have corrected in 1.9.20.0 and it felt normal flying and landing.
Other aspects of the flight were a little odd in that it seemed to be stuttering a bit, but a) that’s quite common in the first session after a new build, and b) I’m still experimenting with dynamic mode DLSS Framge Gen and I’m not sure I’m going to stick with that.
I believed this was the case with SU 7 beta and the result was a not fully vetted release. For far too long beta testers have been reporting bugs that were ignored and have made there way into the final release. I do believe many of us are simply fed up with the process.
Public beta testers are a bonus to help catch edge cases. QA is a whole profession and process and you can’t substitute it with a bunch of regular people pootling around in the flighting version.
This is purely my personal opinion, but it feels as if either there is no QA team, or the people assigned to QA lack a solid understanding of flight simulators and aircraft systems.
I think the use of a beta programme to resolve the drive issue may well imply that it is not going to be as simple as pushing out a hot fix - the development and introduction of the new DLC racing content may have made this a more difficult task to achieve.
From time to time, I help with PC-related issues for someone on the so-called QA team at a well-known game development studio with “Red” in its name. I’m sure you know which one.
However, just because I help him with his PC doesn’t mean he’s an idiot or doesn’t know what he’s doing. We simply have different areas of expertise. He does his job, and I do mine.
I’d bet that the MSFS QA team consists of professionals who know what they’re doing.
With MSFS 2024 approaching its second anniversary, I find it hard to understand why obvious bugs in individual aircraft are still being left unfixed. I just needed to vent a little.
One example is the Saab 340, where the HSI course deviation indicator always points north, regardless of the GPS course. I honestly don’t see how a bug like this could possibly go unnoticed. And these are just some of the bugs I’ve come across in various aircraft.
Anyway, that’s enough venting from me. I’ll leave it at that.
