Major? All I’m seeing are a bunch of visual tweaks (like moving a button here and there), but nothing that actually changes the gameplay — the control tower bug is still there, the weather isn’t really live, Career Mode is completely broken, and that’s just the start. Maybe we didn’t read the same patch notes . Not all of us are obsessed with VRAM! ![]()
WASM crashes weren’t really reintroduced in 2024. They never went away if we consider aircraft from other developers, notably the default Inibuilds a320 and a310
Im just quoting pmdg who says some wasm-bugs that were fixed in 2020 were reintroduced in 2024.
Point is: seems like several developers are waiting for some fixes in SU2…
I don’t use career mod and maybe we are using the sim for different purposes and who knows what else they are working on behind the scenes unless you work at Asobo?
And what about the introduction of features like FSR3? Dude those aren’t minor changes.
Hopefully not to soon as long there are major bugs in the current beta… reproducable ctd at certain locations etc… i left the beta today as i got too much ctd recently… su 1 works stable.
I doubt doubt the mouse issue on the overhead panels of the TBM 930 will ever be corrected.
Ever since Asobo and MS have begun messing up collision meshes in 2020 releases, they NEVER ONCE have been fixed. My guess is they stopped testing airplanes in VR.
These wouldn’t even be hard fixes for the aircraft devs to make it correct from the start. They are just flat out ignoring it.
2024 has just gotten sloppier.
Best we can hope for is community improvement mods.
I wouldn’t be surprised if this build of the SU2 beta is the RC (release candidate) unless they decide to fix easily reproducible CTD(s) that is low risk and doesn’t endanger the stability of the current SU2 build. They are listening and deciding on the feedback here if it is a final SU2 or needs another RC - that’s why they are called “candidates”.
Think of the software as a tree, and the roots are the initial release, with the trunk as the main build (future SUs and CUs) and the branches as the SU/beta. Any fix or new feature always get put in the main branch, but the fixes in the SU need to be approved first as to not destabilize the beta branch. If too risky or complex to fix, and there is a workaround or not a regression, then it unfortunately gets pushed to a future beta.
That is why the moderators push for as much information as possible, including easily reproducible steps that QA and developers can see the issue right away without guesswork. The betas are time-sensitive and every bit helps.
Except of course most of those “easily reproducible CTD(s)” are not in fact universally repeatable. And therein lies the rub. Certainly the sim still has serious bug and issues, but as for something that can crash the sim for any user just by following X,Y, Z steps, that doesn’t really seem to exist.
So do the developers hold off releasing SU2 to keep trying to chase down edge cases affecting some percentage of users? Or do they push it out, take a week or two, then begin the SU3 beta cycle?
As the SU cycle winds down, the dedicated beta QA resources are focused on those limited fixes that were approved by release management, and then the RC software overall to make sure that there are no side effects (regressions) from the fixes - impossible to catch everything with limited time & resources. That is not to say, if QA suddenly reproduces a major CTD in the RC, that they won’t look at the “showstopper” and force another RC.
It is not an easy decision to release or not (generally called a ‘Go/No go’) - not everyone is happy, but at one point, you need to take the hard decision to release, otherwise SU beta never ends and resources are tied up … instead of helping the rest of the team who are developing the current main branch (SU3/future versions).
The TBM must be jinxed…lol When I went to select aircraft to change to the TBM in my sim it CTD. I haven’t had that happen in a long time unless it was something I did to cause it.
I restarted the sim and I see what you mean by the horrible reflections. It definitely needs to be addressed.
but more than anything I wonder… what’s cooking for the surprise sim updates?!?
I’m already over the people that will complain about whatever it ends up being, either because they wanted ABC but we got XYZ, or because MS/Asobo shouldn’t have made any new “surprise” content until the sim is 1,000% perfect (which will never happen).
And this is why we can’t have nice things ![]()
Yeah, maybe we’re not using FS2024 the same way! Personally, I tend to do everything the game has to offer and explore all its features. FSR3 coming in 2025? About time! Even if I don’t have AMD cards. Same goes for DLSS. (Here, we’re talking about visual rendering.) ![]()
But none of that fixes the bugs that ruin the experience and realism. If many players are still on the 2020 version, it’s not because of the visuals, believe me. (I’m not even going to mention the hundreds of posts about the bugs.)
So whether it’s with DLSS, FSR, or in 2D pixel graphics, if the result’s the same, I honestly couldn’t care less. That said, I respect your opinion, we all have different expectations ![]()
The last “monthly” Dev Livestream was March 14th, the one before that was Feb 5th. Seems they skipped April and it’s now May 12th, I have no idea when the next one will be. May 8th they said, " Our monthly Developer Livestream for May is coming soon! We don’t have the exact date locked in yet, but follow our social platforms to be the first to know as soon as we announce the date and time."
I’m starting to lose all hope they have 2024 under control. Supposedly 2024, a whole new version was needed because 2020 was fundamentally unable to be fixed in may ways or new features were impossible to implement? I have trouble believing that anymore, they wanted more revenue. They should have pushed all the career mode BS back and just given us a clean workable sim with an in sim marketplace first. They shouldn’t have put the 2024 year on it and released it when it was ready. This whole disaster seems to have been pushed by marketing and accounting and not developers or customers.
I was having some hopeful flying in SU1 months ago on my laptop (I9 13900H, RTX 4070), so I finally tried it on my 5900x RTX 4080 desktop and it started out great but became unplayable after trying VR (original Pimax Crystal) in VR or non-VR. It’s like 2 to 5fps in non-VR, won’t even run in VR at all, crashes or the display is just artifacts, black areas, with other chunks, and at best 5fps, more often just frozen entirely. Default Steam version, no add ons. Tried verifying the install and that did not help.
This is an absolutely pathetic state of affairs. So beyond frustrated. An absolute disaster and I have lost all hope SU2 will get a non-beta release before June. An absolutely dysfunctional process by Asobo and absolutely dysfunctional communication with us users.
I hope improved night lighting of cities and night lights in general (blobs ? blobs everywhere!). Or g-effects on cameras. Or better turbulence with g-effects on cameras.
New NVIDIA driver 576.40 specifically lists Microsoft Flight Simulator 2024, so perhaps that is significant for SU2? Am in a flight presently so will download the new driver later today. Cheers!
The online user only restricted to the beta participants it is very bored, empty skies/airports, not to join more betas probably if this continues in the next haha
I think this is only about the DLSS overrides in the Nvidia App so you can take advantage of the newer DLSS models. I don’t think there are any other improvements for MSFS 2024 specifically
but we already have the overrides from 1 month now .
Crazy that we hear absolutely nothing from ms or Asobo, really strange.