Empty Community Folder 

Asobo TBM 930 on KSJC runway ready to fly 12 FPS down to 8 FPS when it starts moving.  Warning message about GPU resources. Identical setup prior to Beta 2 gave 50+ FPS

Same runway, same session, same settings Asobo 172  48 FPS and 50 FPS after liftoff.

Asobo 172 take off from KSEE with 80+ FPS - 10-minute flight approach on LOC D 75 FPS down to threshold then 4 FPS finally down to 1 FPS after stopping on taxiway 

Shut sim down and restarted it at KSEE with C 172 - 15 FPS on Rwy ready to fly

Shut sim down and restarted it at KSEE with C 172 - 75 FPS on Rwy ready to fly

Using CapFrameX & Intel PresentMon - no difference in GPU VRAM usage between low and high FPS - the only difference is the duration of the GPU queuing which exceeds 500ms at times.   I guess the update did not improve, and in my opinion worsened the GPU/VRAM issue. 

The Beta 2 sim does load faster 84" compared to 106" in last stable release.

But... the time to go from Free Flight FLY to Ready To Fly on the runway is wildly variable.  Same airport, same rwy, same airplane - sometimes 35", sometimes 65", and occasionally 200".  Resource usage, including internet, is similar between the various starting times.

???

Part of the changelog was extra code that would reduce FPS while they monitor some data.  Maybe that is the issue.

I can't get further than 15 seconds into a flight, so you are doing well 🙂

Just tried the Caravan. Nothing in community folder. Move the throttle to take off and CTD. Not worth getting frustrated over. Going to uninstall it for now and see how things look with SU 99 is released. 

Maybe it's because it's a "Beta"?

I've never really understood the attraction of being an unpaid Beta Tester.

But you guys knock yourselves out

It's the nature of a large update with a ton of changes and interconnected systems. They want people to bang the heck out of it and report issues so they can look into it.

Also, a lot of issues folks run into are with 3rd party addons. That is not in Asobo's area to fix. Unless of course, it's a code issue impacting a library that the addons use.

For example, were you using the default KSJC or the default?

Lastly, a lot of people treat betas as a way to look at new features or maybe fix an ongoing problem. The reality is betas will often make people's experience much worse in the early cycles.

1 minute ago, Rusty Spanner said:

understood the attraction of being an unpaid Beta Tester.

In my case at least, it resolves at least two pain points: the transponder on the default MAX, and the throttles on the a400 not liking below 0 C temps. It also clears up a lot of the issues with trees on the grass in airports.

That said, I agree and the betas are on a short leash.

20 minutes ago, DavidP said:

Maybe it's because it's a "Beta"?

word not allowedshow is more accurate. 

11 minutes ago, Rusty Spanner said:

I've never really understood the attraction of being an unpaid Beta Tester.

But you guys knock yourselves out

I will explain it to you! Back when 2020 was released, initially there were no public betas. Asobo in house testing was missing a  lot of bugs, and most of us would suffered with bugs between official updates. The public consensus was for Asobo  to release public betas. which they eventually did! Public beta are known to stress test software quicker and expose  problems more effectivaly than in house testing. So here we are now !

No one forcing anyone to be "unpaid Beta Tester", but those who opt to become in one in opinion do a great service for public all of us!   

18 minutes ago, Rusty Spanner said:

I've never really understood the attraction of being an unpaid Beta Tester.

But you guys knock yourselves out

If you are doing final testing before a major release, and you think everything is solid but just need to test with a wider audience to catch any stragglers, then no problem. But we are literally the only testers on this project. This is the 737 Max of flight sims. 

22 minutes ago, Rusty Spanner said:

I've never really understood the attraction of being an unpaid Beta Tester.

It's called 'helping'. Sometimes there is no fee involved. 

1 minute ago, sd_flyer said:

I will explain it to you! Back when 2020 was released, initially there were no public betas. Asobo in house testing was missing a  lot of bugs, and most of us would suffered with bugs between official updates. The public consensus was for Asobo  to release public betas. which they eventually did! Public beta are known to stress test software quicker and expose  problems more effectivaly than in house testing. So here we are now !

No one forcing anyone to be "unpaid Beta Tester", but those who opt to become in one in opinion do a great service for public all of us!   

Let me explain it to you. There is no testing going on except us. This is not acceptable. We should be the LAST LINE OF DEFENSE, not the ONLY LINE OF DEFENSE.  

26 minutes ago, Rusty Spanner said:

I've never really understood the attraction of being an unpaid Beta Tester.

Its the love of flightsim, what is new, what has changed - its fun to partake.  I have the steam version, so I simply select 'none' in the beta tab if there is a show stopping bug - in 5 minutes I'm flying the non beta. 

 

3 minutes ago, RobJC said:

Let me explain it to you. There is no testing going on except us. This is not acceptable. We should be the LAST LINE OF DEFENSE, not the ONLY LINE OF DEFENSE.  

Do you work for MS/Asobo that you can say this factually???

Seems suspect. How did they get MSFS2024 even to a usable state to release without some amount of in house testing.

You seem intent on bashing MSFS2024 because we are being "invited" to participate in a Beta release.

An unstable beta? Oh dear, that's terrible! And - we're not even getting paid for it?!

I'll probably just add fuel to the fire here - but, jeez - unstable beta? Aren't betas inherently unstable? As in they need fixes? Since when did we get so entitled?

Disclaimer: I'm not even in the beta. 

Edited March 26, 20251 yr by Cpt_Piett