Xbox Series X
PG On
16Gb Rolling Cache
Live Weather On
Ground traffic Off
Air traffic Off
Multiplayer Off
Wired 1.5Gb Internet
In each build of the SU16 beta to-date, certain aircraft using specific avionics suites suffer from severe performance degradation. This performance degradation results in extremely poor ground detail/LOD, constant stutters, very low fps, 1-5 second pauses, and occasionally black screens.
These performance issues begin as soon as the avionics master switch is activated, and become progressively worse over time both on the ground and in the air.
This performance regression makes these afflicted aircraft unusable in the sim.
These severe performance issues do NOT exist in the public build of 2020, with all of the aircraft mentioned below performing flawlessly.
Ground textures were great but are now blurry. I’m absolutely sure that issues that we are now experiencing were apparent upon the introduction of the build that addressed WASM.
Not only are ground textures blurry but performance isn’t as smooth.
I must add that I am using the V2 Neo by inibuilds which has been performing very well until recently.
Fully agree with op, workingtitles gpses are the biggest suspect for me, especially that it was subject of update. Just now gas superstearman with gps430 - after 30min of smooth flight - first stutters and thereafter black avionic gps no recovery. vfr map, changing views, even atc bar seems degrading performance
I’m playing on Xbox too, and the degradation in performance from the last beta update is absolutely terrible. The SIM has now become unplayable. Even up until the last update I thought they were making progress, but this is the worst that it’s been! Nothing works.
cows da40 first stutters then black avionics (very light generic airport and no pg) … please msobo revert any avionics update just leave us with new bing maps
This. Roll back all of the avionics updates for the next build. If nothing else, at least it may help us see if they are the root of the ongoing issues that have been introduced.
Also, I find it interesting that this regression post has not yet been flagged as “Feedback Logged” or “Bug Logged” considering how widespread and impactful this issue is for Xbox users. It would at least be encouraging to see that our voices are being heard, and offer a bit of reassurance that they aren’t going to release SU16 to us in this state…
Exactly. I’m very discouraged at the way this beta has been conducted.
Very lax so far - not enough care an attention.
This avionics issue needs a real good look at before there’s a full release..
Impact on Xbox users is large - and it’s about (actually, well overdue) that MS/Asobo did some thorough COTS Xbox testing themselves.
The original release notes included details on changes/ updates to two avionics systems which we can’t even use in MSFS2020 - are these impacting in some way and how could we test properly anyway, with no aircraft avsilable that uses them?
The effect that tweaking avionics settings has is certainly disproportionate and affects stock airplanes as well as third party ones. This must be logged for investigstion, please…
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
@Stendec341 - I agree fully. The problem with this beta so far is that everything was introduced all at once, and not staggered. This makes it very difficult to pinpoint exactly what is causing this regression. When the beta first released, we had no WASM aircraft - Being unable to effectively test the beta at that stage, I couldn’t tell you if this performance degradation existed in that build or not. Then once WASM was fixed and we could start using our third party products again, this regression came to light. Is it rooted in WASM? Is it rooted in Working Title avionics? Is it rooted in the new GDK? Is it rooted in the new aerials? Unfortunately, it’s impossible for us to test and determine this on our end, so it really is 100% up to the devs to figure this out.
About half of my wasm fidekity planes suffers severe performance degradation, it have to be addressed on priority right.
Just after my gps (530/430 or 1000 avionics) goes black the game became super smooth and performance is superb - no stutters for camera changing, all becomes great, just no avioncs
UPDATE
After few minutes with BLACK avinics flight (cows da40 super smooth) - CTD (XBOX X).
UPDATE
Activating //42 FLOW causing the same performance downgrade as avionics… seems like wasm or gdk then… BUT READ BELOW
UPDATE
MILVIZ PC-6 Gns530/430, smooth flight for 50min, then activated //42 FLOW (just weather) - severe stutters - next minecrafted passanger - next blacknavionics - then super performance (60fps) - what is significant FLOW with black screens - caused NO degradation (still 60fps). GNS 530/430 seems to be main factor in this case.
For users who can, it would be helpful to see the FPS counter when the degraded performance is occuring, to see which threads are affected.
None of the WT avionics use WASM. All of the avionics updates were included in the first build and there have been no further updates since.
No, it would not be possible for them to impact anything. Avionics only run when they are instantiated in your aircraft. These avionics are not running if they are not in your aircraft, and their mere presence on disk cannot have any impact on the performance of other avionics, as they share no code: every instrument’s code is bundled individually with that instrument specifically for this kind of reason, to maintain isolation and prevention against regressions in unrelated packages.
Flow also does not use WASM. It does, however use the JavaScript technology stack (Coherent) inside the sim engine that is also used by the WT avionics. Flow, however, does not share any JavaScript code at all with the WT avionics, indicating that something inside the engine itself may be at issue, since there is otherwise no overlap between the two.
Matt, thank you for the interesting insight. It’s very reassuring to see you in here taking our comments seriously, as from everything we have been able to deduce, this severe regression is likely tied to the Working Title avionics updates included in this beta. Something is very much not playing nicely with 2020…
Unfortunately as Xbox users, we have very few tools at our disposal to be able to offer any in-depth details/insight about our sim experience while this performance degradation is occurring, apart from subjective descriptions about what we are observing. We unfortunately don’t have an fps counter to pinpoint the affected threads.
Although we of course are looking at that possibility, that does not seem likely, given:
users have seen performance degradation when using other utilities, like Flow
users have seen degradation when other third party avionics are used (like the GTNs, or the CT182T, which uses the pre-WT G1000) that do not share code with the sim avionics
the WT avionics do not share any code with each other (all of their code is separated), and they were all updated in completely different places and ways (and some not updated at all)
The performance degradation tied to avionics didn’t appear to be reported until several builds after the avionics updates were deployed
All of these indicators point away from the avionics update and towards a sim-side JavaScript engine issue, which is the only common denominator between these items.
pls Read my comment up, the FLOW doesnt affect the performance over all, it was the avionics which relased resources after blackout. Check my edits.
update
Just now another examplle comanche (gns530/430) after stuttering and blackout of gns and efb performance is back… THEN CTD
New case:
XBOX X, CAS J3 Cub (no avioncs) , New York+photogrametry - after 15min of flight over Brooklyn - stutters - minecrafted passanger - CTD
Seems like all my wasm planes are wasted in current beta state
I just want to clarify something you stated - These issues came to light in the second SU16 beta build (in which WASM functionality was fixed). I believe these issues may still have been present in the first build, but they weren’t widely reported because everyone was holding-off using the beta until WASM was working…
In any case, something isn’t working correctly and needs to be addressed before SU16 can release, so I’m glad this is being discussed/investigated! I’m sure a solution will be found… It has to be.
Masachusets area.
FI bf109 (pg, gns430, full realism) after 10min of flight - stutter - blacknavionics - CTD
2nd flight - FI bf109 (pg, NO gns, full realism) No crash but low fps (like 30, for me it’s slideshow) and terrible (fs24like) LOD - trees squares popping on 1 mile away…
UPDATE
Back to su15, like night and day, no stutters, great performance, just few pictures from recent reunited su15 flights.
seems like wasm or gdk then… BUT READ BELOW
