Or they could just go back to 2020 which is a million times better!
Interesting! I have the same issue.
Pretty stable for me so far but I have not tried any complex aircraft yet. Performance maybe a little better than SU1 but probably too soon to tell. The only issues I have relate to the toolbar apps and panels which are not working (e.g. Navigraph, VSR, Sayintentions).
I donāt believe anyone who has taken part in the SU2 beta has experienced a 0xC0000005 error. In most cases from what Iāve read the CTD is caused by a Nvidia Direct3D .DLL file.
Every CTD is circumstantial and could be specific to a group of users with similar variables. For me it seems to be with certain aircraft, for example when I select the default A310 I always get a CTD - this occurs when selecting my departing airport (irrelevant where) and clicking fly now.
After a day, my feedback is mostly that the load times for flights are awful. Iām going to see if thereās a voting thread for it, but I and others are seeing 30 seconds all the way up to nearly 5 minutes to load flights even with empty Community folders. I have no idea if itās only Steam users, something to do with the temporary memory tracking they added to this beta, or what. If itās the latter, Iām okay with it if it helps them learn something.
Other than that, Iāve had a good experience overall. My prayer for SU3 is that we get a serious, SERIOUS tree removal effort. Whatever algorithm places trees is fundamentally flawed (trees all over barren mountains, deserts, so many trees for no reason.) Already voted on that elsewhere, not trying to open a can of worms as itās not a SU2-specific issue, but fingers crossed it can be addressed at least this year.
This isnāt the first time. Shambolic roll out. Thousands of bugs, many obvious. Phantom updates and now a poor beta release. When it works, its a great product but the quality assurance from MS is appalling.
Just to begin with: where are all my expensive planes (PC-12x2, PC-24x2) that I bought after earning every penny in hard bugged missions over time?
They have been replaced with much cheaper planes without any warnings!
Also my companies were changed: I had only 3 companies but 9 planes, now I have all company types with 11 planes I havenāt chose!
And I havenāt started anything yetā¦
Itās not just you, itās not just Steam users, and Iāve waited >10 minutes to load into a flight before quitting and giving up.
The long list of bug fixes we got at the release - are those in Beta2 or were those for the normal sim. All I am reading is how many problems there are with Beta 2 and I might be mistaken but if those bug fixes were included I do not see it here! I read that more things are broken.
Does pushing the ESC key (while loading) and the FLY NOW resolve your problem? It worked for me a few times.
You must read the release notes. This is separate from your normal career mode and you will get those back if you opt out.
Iām flying mostly in VR. FSLTL causes CTDs everytime, and I had to remove it from Community folder. After that SU2 beta has been stable so far. Performance and image quality are at least same, or better than in SU1. Quite happy for this beta release, and waiting for EFB in VR mode. And hopefully 3rd party addons like FSLTL will work better in few weeksā¦
Please read the release notes. The answer to your question is near the very top.
Changes to Career/Challenge League in the Sim Update 2 Beta
Beginning with the Sim Update 2 Beta, Career and Challenge League will have separate progress and leaderboards from the live build.
This means Career mode progress in the live build will not carry over to the flighting build, and vice versa. In addition, Challenge League in the flighting build will have a separate leaderboard from the live build.
Making Career and Challenge League progress separate in the flighting build allows us to test additional changes and fixes that cannot be tested in the live build. All Career specializations will be unlocked by default in the flighting build to allow participants to preview changes that might not be available (based on Career mode progress) in the live build.
Thanks,
MSFS Team
They clearly fixed a lot problemsāthe list of fixes in the release notes was super impressive. While only they know, even one new problem could be causing the bulk of CTD issues many of us are dealing with. You can fix 1000 things and simultaneous introduce one new bug and make the product unusable for lots of folks. For everyoneās sake, I hope it is localized.
Nope. See the thread I linked a couple posts above.
Thatās useful information. Are the users reporting a lot of CTDās using AMD or Nvidia GPUās, for example. I have a 3090 FE, and a non current driver, I forget which version exactly.
Another positive flight experience.
I just did some pattern work in the DC-6 at KPRB.
Iām really pleased to see that something was fixed in the SDK, because now BMEP is being calculated correctly and I can, once again, use the power settings I know for operating the engines safely.
The only oddity was the clouds all disappeared from the sky on final and then on short final they all loaded back in. Perhaps a weird METAR vs. world weather boundary thing?
Performance with the DC-6 was awesome, Iām still feeling that FSR 3 is a much better FG solution over AFMF, which was already great.
All in all, Iām really having success with SU2 Beta, minus the odd CTD here and there.
Iād agree with this statement particularly regarding the graininess for the first hourā¦now it seems back to how it was before SU2.
āLoading unusually longā: stuck at 97%. Yesterday CTD one after another. Worst version ever (until now, of course: even after the initial release no one would have said that we would ever see something so ridiculous, and instead it happened, and it will happen again)