Please indicate your playability of the sim with the following statement - Xbox stability in this build is generally:
Better than the current public retail build
About the same as the current public retail build
Worse than the current public retail build
Unable to tell
0voters
To report a bug, please use a sub-category of Sim Update 4.
Please provide additional information in the comment section below
Reminder:
Add-ons/Mods/Community content are not official Microsoft Flight Simulator products and may cause issues with the Build. If you encounter any issues, temporarily disable ALL add-on content then try again. If the issue stops, add back the add-on content one by one until you find the add-on that is causing the issue.
Simply wow, zero stuttering, everything’s smooth so far, outstanding performance, a very nice flight, a completely different game… Now it’s really fun!
Performance and stability looks good. But my custom control profiles definitely got set back to a previous version. IDK if the beta update or refreshing the rolling cache was responsible. It doesn’t seem that either should have caused it, but something definitely did. Many settings were changed back to their default values.
So they offered 3 fixes for stutters + 1 from .30.
PMDG 777er KJFK - KATL. Default video settings, no fauna. Planned on Simbrief, imported to EFB via MSFS Planner and full ATC. EFB for weather and charts. PMDG TWIP, ATIS and ALTN requests. 128 Gb cache. The works?
3:30 EST Friday afternoon - after 8pm (hour plus of TOD pause.) - Residential internet primetime
Very minor stutters in preflight to taxi phase. Smooth takeoff and climb throough DEEZ SID. Got smoother with altitude. Descent featured one significant stutter near 10,000 ft. Smooth from there to manual landing.
A minor stutter or two in taxi to gates. (Sim hadn’t offered taxi to gate for 777 for some time so that was a welcome return).
Shut down fine. Esc and clicked end flight - CTD.
Given the history vs the impressive visual and technical performance of this flight - the CTD seems almost trivial. Its not - but - all things considered…
1Gb internet, hotas, keboard, mouse, controller- all wired
It’s working for me. Flew on .31 yesterday and today and made adjustments to control curves during both sessions after using “Search by input”. I’m using the Velocity One Flightstick.
Its stable for me. The only issue left that I can see is that the preflight station checks don’t always appear to work – a few of the checks on the C172 G1000 only appear after you leave and then look back. also, if you turn off autopilot with the gamepad(Right Bumper + D-pad Up), you can’t turn it back on with the mouse. both very minor.
Whilst there have obviously been great improvements on the performance side, the stability of this beta worries me.
Last night a WASM crash on the A350, whilst taxiiing after some oddities loading up the flight and then a CTD whilst I was taking another look at the PMDG B777 freezes in flight - long 20-45s freezes accompanied by a sound similar to (but not the same as) speed brake deployment.
There are also third party aircraft that won’t even load. Navigraph data is broken on some aircraft too,
If you look around the forum, there are a large number of “regressions” being reported, but this beta build has introduced so many instabilities (WASM related?) that the normal way of recording “regressions” isn’t sufficient to cover the mess.
Add to that freezing when zooming in on the map view, long load times in free flight, with sound cutting in and out and this now feels like the mess of a very early beta….
If the stability of the beta isn’t properly investigated before release, SU4 is going to create more problems than it solves or improves..
Weird you say about speed breaks… in my flight last night using A350-900 I noticed on the ecam during descent that speed breaks were automatically deploying but only by a fraction which caused issues when trying to arm the speed brakes for landing as they kept auto deploying but only by a fraction. This has never happened in the past.
Whilst the latest beta build has made a huge improvement in performance on Xbox for which I for one am very grateful - it’s made a real and big difference - I’m going to sound a bit like a grinch now:
From the very start of the SU4 beta a lot of WASM instability has been introduced - and has not been adequately dealt with (regression reporting isn’t adequate when such a large range of issues are introduced). We have symptoms in complex third party (and default)aircraft ranging from complete failure to load at all, long freezes in flight, Navigraph update failures - and other system issues. I’m not going to list the ones I’ve experienced again here but they are numerous and some serious.
The problem is that - especially with third party developers badly affected, we are in for a long haul before these issues are all dealt with and solved. Think weeks or months or perhaps longer.
So I’m surprised SU4 is going to be released in what I think is an unacceptably unstable state - customers who are not on the beta are going to be in for some unpleasant surprises - the excellent performance improvements on Xbox notwithstanding- as they find many of their favourite aircraft are broken or even that a newly purchased one doesn’t work - or even load in the worst case.
It is also - as these issues are slowly resolved- going to make it exceptionally difficult to move on to a new beta phase in a satisfactory manner.
I think it may be a big mistake in the making to release it in this state.
Please provide additional information in the comment section below 
Reminder: