For comparitive purposes, you should try the same flight using only the stock sim and the same graphics settings but with no add-ons.
You don’t need external or complex addons to overwhelm your VRAM. Your graphic settings are way too high.
HDR, 4k native and Ultra settings: that is absolutely crazy with 16 GB VRAM. I have some settings on High, all traffic settings are lower, and DLSS Quality activated. That is working nice with 16 GB.
5 Likes
Folks, a large number of posts were flagged by users as being either off-topic and / or inappropriate; and violations of the Code of Conduct. These posts, and any replies to them, have been removed.
This is a bug topic for providing feedback to the developers about the issue so that they can fix it. Please keep your posts focused on the bug and how your feedback can help the developers, and refrain from making personal comments towards other individuals.
As per the Code of Conduct:
- A Pilot is a Pilot - Treat everyone in the community with respect, and seek to have positive experiences with your fellow pilots.
Please also note that this topic already has the bug-logged tag, so the issue reported by the community has been successfully reproduced by the test team and turned into an official bug. The bug will be assigned, prioritized, and worked on for a future fix.
Thank you.
1 Like
I have everything on the lowest settings and VRAM is still maxed out like crazy. This wasn’t the case before. Framerate cut in half, jumping around between 80 and 40Fps without changing anything to the settings or the sim.
1 Like
What is “before”? SU3? And how much VRAM do you have? What scenarios are you flying, and which settings do you use?
1 Like
Yeah i noticed in HWinfo my virtual memory is going red all the time in msfs 2024. 5080 16gb. I never had the hwinfo untill very recently though so not sure how long it’s been happening.
I have textures and clouds at ultra, LOD 200. Aircraft traffic/sea etc is off or lowest settings.
1 Like
I have an ASUS 5080. The textures are still a killer. I set to Low. You cannot tell the difference unless your nose is on the runway 
Clear skys.
2 Likes
Cheers ill try it thanks.
Yeah i think the reason i might have been stuttering is because my vram was maxxing out, do you think this is probably correct?. Lowering textures to high instead of ultra seems to have solved it, might need to test a bit more but seems like thats the reason.
I guess, I missed the “build versions”, but with a 16GB 5080 I see mega stutters. Then checked the GPU mem usage: 15GB in Taskmgr, in 2024 (Debug mode) it jumps over the max 15something GB max available causing the stutters (FPS jumps between 40-80) Everything low, 2.5K res.
Tell me how it turns out. BTW, if you are using the registry hack that displays DLSS values to screen in real time, that uses VRAM also.
5080 users should stick together. Mine is so heavy I have to carefully set the bracing to keep it stable… maybe just in the ASUS MB.
As already mentioned: Ultra Settings with 16 Gb VRAM is not a good idea.
1 Like
VRAM can also be used by apps running in the background. A single open browser tab can use up to 2 GB VRAM. That is of course missing in the simulator.
Although MS has improved the VRAM situation in SU4 signigicantly, you have to take care about your setup and configuration:
-
close all unnecessary background apps
-
chose appropriate settings. “High” is a good starting point, and then you can reduce some settings, in particular traffic, but maybe also terrain caching or texture resolution if necessary.
-
Raytracing Shadows are also consuming much VRAM.
-
And it is recommended to use DLSS Upscaling in order to reduce the render resolution.
1 Like
Does using HDR use much vram ?
It depends. It uses more VRAM, but how much more depends on the resolution, scenery and objects.
1 Like
In my experience, since SU4, the VRAM is constantly being purged of off screen assets, no matter the VRAM utilization, and it makes the screen freeze/stutter/jerk for a short time with every swift/quick change of view, most noteably when looking up from the cockpit, or looking to either side, after the view has not been altered for more then a few seconds beforehand.
On my system, this is perfectly reproduceable, even when the VRAM utilization is as low as e.g. 6GB, when e.g high up in the air and FPS in the three digit range.
Looking at the metrics as shown by rivatuner, I can monitor the VRAM utilization drop by e.g a few hundred MB or even a GB, once the view is not being altered for a view seconds.
Then, once the view is being altered again, the screen freezes/stutters/jerks for maybe half a second or a second, until VRAM gets filled up again, and it is smooth sailing after that, for as long as I keep altering my view. This can be repeated ad nauseam…
Because the mouse is also not responding linearly to inputs, but with hard coded acceleration,
this jerking/freezing is exxagerated, as this (extremely annoying) mouse acceleration makes you altering your view more rapidly, thereby requiring more VRAM to be fetched/reloaded in a shorter time, and resulting in even more annoying/longer freezing/jerking.
I really hope, the devs are aware of and can get on top of this for the upcoming SU5 beta.
It is very annoying, and a huge regression from SU3
3 Likes
I know, I start in dual GPU mode and use Optimus, in that case the other apps use the Intel i7 (14th gen) GPU memory and not the Nvidia I have. Of course I checked this, why would you think I did not
…and I have everything on the lowest setting as I said before.