2 hours ago, bobcat999 said:

I agree.  Do it if you need to - it's for people that are too fragile to read genuinely deserved criticism of the Asobo development staff..
There is nothing wrong with discussion about 'bugs' or undesirable effects in a beta, but it seems some people are prepared to accept any old tosh.  
All that insulting talk about support animals and go and touch grass etc. really seems to apply to them, as they are wounded by criticism of their sacred toy.  Too funny!

Not fragile, I'd say. Real complaints and issues, yeah. Some of these are valid complaints. I am sure you have a list of issues in 2024 as I do but currently in this beta build.....it's hardly an issue. Most of my planes work (even the dc6), active sky works and even gsx works. All my scenery works and the performance is smooooth. 

For those that have a hard time and complain about everything (including landing gear for AI planes disappearing or an annoying message on the screen for example) that's fine. It is annoying. But derailing every thread into these topics is exhausting when you want to hear about real issues. But you're right: ignore button. 

1 hour ago, vbazillio said:

Am I the only one - again with this build as with the previous - that don't feel the need for swapping default DLSS v310.1 ? I had good performance and not yet warning of VRAM overused.

Actually, Yeah. I realized my dlss wasn't changed (my fault) and I have left it back at default. Performance is good regardless of the changes from my end.

So far the following works after a few a flights.

Active Sky (not the new beta yet), GSX, AvroRJ, DC6, 777, Dukes, Baron/anza V2, A2A aerostar and Comanche. AtmosCore still doesn't work since the previous SU4 beta but meh not a big deal.  

Edited November 1, 2025Nov 1 by Sonosusto

First proper flight with this beta build;

Pros - Mouse is back in VR without having to switch off the VR controller, the community "hack" to rid the UI nonsense is great (a simple feature/bug can be such an immersion killer), performance is still good for the most part but see below.

Cons - One major lock up in VR whereby the screen just stopped, I thought the game had crashed but it cam back to life after about 10seconds, never had that before as it usually results in a CTD (so that's a Pro in a way but a Con that it happened). Performance isn't as good as earlier beta builds, panning was laggy at times. Take off FPS smooth and fine but landing FPS dropped quite a bit for no reason (empty small airport), carried on in Taxi until parked.

Overall - Decent and enjoyable with a few rough edges.

13 minutes ago, MarcG said:

First proper flight with this beta build;
....... the screen just stopped, I thought the game had crashed but it cam back to life after about 10seconds, never had that before as it usually results in a CTD (so that's a Pro in a way but a Con that it happened). Performance isn't as good as earlier beta builds, panning was laggy at times. Take off FPS smooth and fine but landing FPS dropped quite a bit for no reason (empty small airport), carried on in Taxi until parked.

Overall - Decent and enjoyable with a few rough edges.

Ok. Wow. 10 second lockup of anything is drastic and pretty bad. Did you ever find what the cause was? (for the record my only stutters were loading batc trafffic initially but that is typical when first loading 30+ planes at jfk haha).

Wonder if VR users are having the most of the problems?

I find all of this bantering amusing. MS has a set budget. They have a certain headcount. Do they get rid of other positions to add QA personnel which might mean slower development or do they push some of that burden to the Beta tester community. Or do they keep the headcount as is and slow down development to let their existing QA staff have more time to test, thus less frequent updates. I like the cadence and believe the process is working well. Tremendous progress has been made in a year that I believe would have taken much longer using other methods.

In 2020, people complained that there should be a public Beta. So MS began doing it, and now people complain they found a glaring bug. This issue will be fixed soon because they release 1-2 updates per week. I honestly believe they should gate the Betas because most people should not be participating in them. Just look at all of the unhinged emotional reactions in this thread. 

1 hour ago, Sonosusto said:

Actually, Yeah. I realized my dlss wasn't changed (my fault) and I have left it back at default. Performance is good regardless of the changes from my end.

So far the following works after a few a flights.

Active Sky (not the new beta yet), GSX, AvroRJ, DC6, 777, Dukes, Baron/anza V2, A2A aerostar and Comanche. AtmosCore still doesn't work since the previous SU4 beta but meh not a big deal.  

Thats funny because for me Rex Atmos is working SINCE the last Build. It wasn't for the previous two or three versions... 😄

15 minutes ago, ThomseN_inc said:

Thats funny because for me Rex Atmos is working SINCE the last Build. It wasn't for the previous two or three versions... 😄

😀 I guess Rex doesn't like me. 

 

25 minutes ago, Gulf76 said:

I find all of this bantering amusing. MS has a set budget. 

 Just look at all of the unhinged emotional reactions in this thread. 

All true. 

Thankfully, most things are working and that annoying message popup etc leaves the screen after a few seconds of taxing/rollout etc. I mean for gosh sakes even the DC6 and its gyropilot are working. "Reversers" and all. 

Edited November 1, 2025Nov 1 by Sonosusto

36 minutes ago, Gulf76 said:

I find all of this bantering amusing. MS has a set budget. They have a certain headcount. Do they get rid of other positions to add QA personnel which might mean slower development or do they push some of that burden to the Beta tester community. Or do they keep the headcount as is and slow down development to let their existing QA staff have more time to test, thus less frequent updates. I like the cadence and believe the process is working well. Tremendous progress has been made in a year that I believe would have taken much longer using other methods.

In 2020, people complained that there should be a public Beta. So MS began doing it, and now people complain they found a glaring bug. This issue will be fixed soon because they release 1-2 updates per week. I honestly believe they should gate the Betas because most people should not be participating in them. Just look at all of the unhinged emotional reactions in this thread. 

Absolutely THIS !!!!

 

1 hour ago, MarcG said:

First proper flight with this beta build;

Pros - Mouse is back in VR without having to switch off the VR controller, the community "hack" to rid the UI nonsense is great (a simple feature/bug can be such an immersion killer), performance is still good for the most part but see below.

Cons - One major lock up in VR whereby the screen just stopped, I thought the game had crashed but it cam back to life after about 10seconds, never had that before as it usually results in a CTD (so that's a Pro in a way but a Con that it happened). Performance isn't as good as earlier beta builds, panning was laggy at times. Take off FPS smooth and fine but landing FPS dropped quite a bit for no reason (empty small airport), carried on in Taxi until parked.

Overall - Decent and enjoyable with a few rough edges.

yes, I see this lock ups frequently, much heavier as with the prior .19 build. 

Maybe vote here:
https://forums.flightsimulator.com/t/overall-lower-frametimes-but-spiking-higher-frametimes-as-well-in-vr/745129

the .21 build at my end

Lower 0.1% Frames, BUT when a low Frametime happens, the spike is much higher, up to 0.5 and 0.6 Seconds!!! This means a real “hanging Frame”. Therefor the overall smoothnes seems better, but these pulsing hangers are a bigger issue for me in VR as the prior .19 build. The spiking frames occur every 10 to 15 seconds.

This is related to AI in Game Traffic. Realtime Traffic on, Airtraffic density to High and Parker AI Density to Ultra.

As soon es I turn AI in Game traffic off, the Stutters disappear completely.

In .19 build the in Game traffic had no stutters at my end.

9900X3D

5090 RTX

64GB RAM

5 minutes ago, mpo910 said:

yes, I see this lock ups frequently, much heavier as with the prior .19 build. 

Maybe vote here:
https://forums.flightsimulator.com/t/overall-lower-frametimes-but-spiking-higher-frametimes-as-well-in-vr/745129

the .21 build at my end

Lower 0.1% Frames, BUT when a low Frametime happens, the spike is much higher, up to 0.5 and 0.6 Seconds!!! This means a real “hanging Frame”. Therefor the overall smoothnes seems better, but these pulsing hangers are a bigger issue for me in VR as the prior .19 build. The spiking frames occur every 10 to 15 seconds.

This is related to AI in Game Traffic. Realtime Traffic on, Airtraffic density to High and Parker AI Density to Ultra.

As soon es I turn AI in Game traffic off, the Stutters disappear completely.

In .19 build the in Game traffic had no stutters at my end.

9900X3D

5090 RTX

64GB RAM

Really glad you found the culprit so far. I wonder...are you using any liveries or traffic from 3rd parties (or their liveries?) or is this strictly default asobo AI liveries/traffic? 

10 minutes ago, Sonosusto said:

Really glad you found the culprit so far. I wonder...are you using any liveries or traffic from 3rd parties (or their liveries?) or is this strictly default asobo AI liveries/traffic? 

I use liveries from FSTraffic and FSLTL, but downsized to 1024x1024 Pixel, instead of the original 4k size. The traffic behavior, injection, is pure MSFS RealTimeAI Traffic, in sim. 

Edited November 1, 2025Nov 1 by mpo910

Hi everyone, the following is a copy/ paste of a comment I left at the official MSFS beta 'regression' topic. It was 'hidden' by the 'community'

PLease Asobo, now that you have brought so much attention to one of your silly ideas, wont you please listen to the community of serious simmers and also remove the stupid TOGGLE EFB__SHIFT+C ENTER AIRCRAFT message in the walk around mode.

I realize that the ‘gamers’ are the users you most depend on, and without them, this huge project could fail. However, please, can’t you make these annoying messages optional? Most ‘simmers’ don’t want or need these messages taking away from our immersion. 

End quote.

The following is the reason given for the post being hidden.

 

Your post was flagged as inappropriate: the community feels it is offensive, abusive, to be hateful conduct or a violation of our community guidelines.

Your post has been hidden due to the amount of times it was flagged by community members. If it was not deleted or removed by a moderator due to the severity of the content, please consider how you will revise your post to reflect the feedback from moderators. You can edit your post after 10 minutes, and it will be automatically unhidden.

However, if the post is hidden a second time, it will remain hidden until handled by staff.

For additional guidance, please refer to our Code of Conduct. End quote.

I am curious; was my post offensive? And how have I violated the code of conduct?  

Please educate me.

 

 

 

43 minutes ago, Romeo_Tango said:

Hi everyone, the following is a copy/ paste of a comment I left at the official MSFS beta 'regression' topic. It was 'hidden' by the 'community'

PLease Asobo, now that you have brought so much attention to one of your silly ideas, wont you please listen to the community of serious simmers and also remove the stupid TOGGLE EFB__SHIFT+C ENTER AIRCRAFT message in the walk around mode.

I realize that the ‘gamers’ are the users you most depend on, and without them, this huge project could fail. However, please, can’t you make these annoying messages optional? Most ‘simmers’ don’t want or need these messages taking away from our immersion. 

End quote.

The following is the reason given for the post being hidden.

 

Your post was flagged as inappropriate: the community feels it is offensive, abusive, to be hateful conduct or a violation of our community guidelines.

Your post has been hidden due to the amount of times it was flagged by community members. If it was not deleted or removed by a moderator due to the severity of the content, please consider how you will revise your post to reflect the feedback from moderators. You can edit your post after 10 minutes, and it will be automatically unhidden.

However, if the post is hidden a second time, it will remain hidden until handled by staff.

For additional guidance, please refer to our Code of Conduct. End quote.

I am curious; was my post offensive? And how have I violated the code of conduct?  

Please educate me.

 

 

 

There are many individuals who struggle to accept reality and believe that everything is fine. This seems to be developing into a cult-like mentality where any report or complaint about a bug, or evidence of unrealistic expectations, is automatically flagged as inappropriate. While some people are satisfied with the progress being made, they are also people tired of the dismissive attitudes, such as "Oh, it’s nothing," "I can live with it," "I didn’t notice this," "It’s just a small issue," or "The future looks good." This mentality of downplaying concerns and silencing criticism because the truth can be uncomfortable is detrimental to software development and progress, ultimately hurting customers in the long run.  

 

2 hours ago, Sonosusto said:

Ok. Wow. 10 second lockup of anything is drastic and pretty bad. Did you ever find what the cause was? (for the record my only stutters were loading batc trafffic initially but that is typical when first loading 30+ planes at jfk haha).

Wonder if VR users are having the most of the problems?

Nope first time that's happend, I haven't had many lock ups resulting in CTDs but this was just different in the way it came back to life! Thankfully the flight wasn't ruined but it wasn't a good thing regardless, will see if it happens again.

I have flown several flights with the A2a Aerosoft 600 and the Duke Turbo.  No issues on my end.  If your biggest problem is a popup message  that disappears, you have a serious skills issue.  Think of flying IRL and letting a minor distraction such as a loose door or strange rattle fly you into the ground as recent events have demonstrated.  It is a nothingburger, IMHO