I also get these in flight, and randomly when changing to a new aircraft, it will lock up and I get the dxgi_error_device_hung (0x887a0006) error. 4090, no issues prior. Lowered settings and rolled back Nvidia driver as well.
My sense and read of the read of this is that it is multi-determined. The question I will try to answer for myself is: are there still memory-leak like issues at the end of SU2 that compromise playability given the amount of VRAM available to me? While this was #1 on the bug list, my understanding after 2 Dev Livestreams that it is not one single bug, but a compound finding related to optimization needed across multiple assets and perhaps other unstated causes they are working on in 24.
1 Like
Not an answer but an observation. I noticed that my VRAM usage in the beta is lower than update 1. And that is with all the same graphic settings. So I think there has been some tweaking, as my 4060 ti was usually just below its 8GB max, while I am seeing high 6s and low 7s now using the same aircraft in the same scenery. Also there has been a change to how my 4060 ti performs. Previously it was annoying often well below maximum utilisation and 80% or lower was common. But now it is humming along at 99% all the time just like MSFS 2020, so it seems that update 2 is better utilising my GPU now.
2 Likes
Yes, I have that too.
You folks are using GSX in a beta?
Sure - as far as I’m concerned, beta = current 
2 Likes
I was having performance issues and CTD with this turned off (as I read the release notes prior to loading in for the first time) to get a baseline without it reducing performance and performance in airliners was terrible. I then switched it on but didn’t have time to try it but if it barely functioned with it off …
2 Likes
Overall, performance and stability have improved a lot. I have a 4060 and I noticed that the VRAM usage has dropped by about 5%, not much, but it helps with performance. I noticed that when the VRAM increases to a critical limit, a warning message appears and apparently sends a report to the developer. I believe this will help with improvements in the future. I don’t play career mode yet, so I can’t comment on simRate in it. I’m waiting for the simulator to mature so I can use career mode. I’m eagerly awaiting the fix for the bridge in Rio de Janeiro, I believe this will be easy for the Devs. Please fix this. I thank the MSFS/Asobo team in advance.
1 Like
i didn’t see that the saab fmc software had been updated to v2 so im assuming its still not gonna work.
I’m using 3.3.9 without any problems, what’s your problem?
1 Like
Have you noticed that when using GSX on SU2 beta, a blank blue message box appears at the top left that doesn’t go away from the screen at all unless you restart the simulator?
1 Like
I’m in a Multiplayer flight and SU1 people can’t see SU2 Beta people and vice versa.
2 Likes
Dude, look what worked well for me… I have an nvidia 4060 and ryzen 7600x 32gb of Ram. I uninstalled the simulator and reinstalled it again, after updating the DLSS with the DLSS SWAPPER, to version 310.2.1 for FG too, without anything in the community, I ran the simulator at 1440p on high, with the SU2 beta. Everything worked perfectly without CTD, I flew for 3 hours and opened and closed the simulator about 3 times, everything ok. Now I’m gradually putting the add-ons from the community and testing them one by one.
2 Likes
Remember that you are in a BETA version whose purpose is, precisely, to reveal the bugs and developers can fix them before finalizing the work. Therefore, you should not compare it with SU1 until the final SU2 is officially released.
3 Likes
Folks complaining about bugs instead of reporting them don’t seen to understand this.
8 Likes
Will be activated again in the next beta update. Officially it was a mistake
2 Likes
After rollback MSFS2024 SU2 to the public version my rolling cache file is gone and the sim don’t want to make a new one.
Path is wrong and i can’t point it to the right path, also a can’t change the size of the rolling cache. It always flipping to zero. 
It should have been like that from the start.
We.would.not have lost the beautifull weather pre SU5
2 Likes
I tend to only fly in VR and so my testing so far reflects this.
What I have found is a couple of fixes that bugged the hell out of me for a while.
Firstly, the large black square when you enter VR mode. The square is at least semi-transparent and if nothing else it makes it look a feature rather than a bug.
Also once you reset the view point the window disappears, correctly, no more having to press ESC and ESC again to be able to proceed.
Another thing is that only sound thread appears in the Windows 11 Volume Mixer settings. No more 2,3,4 or more and then trying to find which one will actually reduce the sound to avoid annoying the other half.
My main issue that I have experienced so far is with the new Foveated Rendering option in VR.
It seems that if you use OpenXR Toolkit it crashes to desktop as soon as you enable VR, at least for me.
If you disable OpenXR Toolkit it works fine but I was getting 70-75 fps in the cockpit of an aircraft on a runway. With the option disabled, and in the same aircraft on the same runway, I was getting 90 fps.
I understand that it uses more CPU if you set the option on, but that is one big drop.
So as it currently stands, I would rather use OpenXR Toolkit for some of its options than Quad view.
Other than this quite big thing for me the experience has been positive so far.
so can someone explain what the point of giving us all the different companies but then only give 5 million credits in the beta, what should have happened is that a screenshot of your current balance be taken before the beta went live and that balance be copied over. then with everything available, then the cost of new planes was 1/10th the price like how Elite Dangerous did its betas.