It’s true. For HD resolution and maybe in some cases 2K. But not applicable to 4K. They just forget to mention it…
Not if his secondary scaling was originally set to 2.0 as he mentioned in his following post
In that case he still used about 2K resolution. Having about half of the pixels means linearly less performance required to draw them. Hence having 30% set and doubled it still means only 60% and that’s around the 2K resolution. Far from being 4K and that’s why he immediately experienced massive FPS reduction as soon as he started to set higher resolution.
Having 12Gbyte of VRAM and using the sim in real 4K is currently not possible. It’s not even possible 24Gbytes of VRAM in many cases according to some experiences here.
If the solution is to downgrade your resolution to make it usable then it simply cannot be advertised as a 4K simulator.
2 Likes
Don’t do things like buying a new graphics card!
It’s Asobo who has to optimize VRam management.
12 GB must be more then enough to run MSFS2024 on 4K after optimization of VRam management by Asobo.
Effective VRAM memory management ensures smoother performance, reduces load times and prevents graphics failures caused by VRAM depletion.
3 Likes
I can assure you that 8GB, the recommended amount, is not enough for 1080p at medium texture resolution with high fidelity aircraft at handcrafted airports. I mean it does run fine in a Cessna 172 so maybe that was their target 
2 Likes
this is the thing
WHY would i settle for 2024 @ 70 tlod
when i can run 2020 @ 230 tlod
think about it asobo
1 Like
I was referring to the FHD quote, his resolution is clearly marked at 2303 X 1295 which takes into consideration the secondary scaling option, if not then 30% of 4k would be 1151 X 647.
Achieved resolution here is a little below 2560 X 1440 but defintely higher than quoted “only bit above FHD resolution”
If I may ask, where was the sim advertised as a 4k simulator? most modern games support 4k resolution but they not sold in this way.
It’s all about VRAM memory management and that is a task for Asobo.
8 Gb must be enough when Asobo has optimized there Memory Management.
MSFS2024 is not ready yet! 
2 Likes
That’s … not how the game plays at all. It’s a set of semi-open worlds that you can move through seamlessly, essentially forever unless you trigger certain story-related events (which you don’t need to do). The game is constantly generating new animated people and animals, foliage, and prop elements, processing shaders and texture files for thousands or tens of thousands of objects in each world as you move through it and interact with it all. That game is also built using Vulkan, like all MachineGames projects are, and does all its GPU work pretty close to “bare metal,” perhaps even moreso than DX12, though that is debated.
But aside from that, you’ve ignored the larger point: the game allocates VRAM to itself and then the VRAM usage, whether reported by the game’s own data display; Task Manager; and third-party tools liek MSI Afterburner, basically never changes. So all the manipulation going on, even during the occasional cut scene or transition, is not reflected in the stats being displayed.
And THAT is my larger point - there are multiple ways for a game engine to allocate, fill, purge and refill video memory. The post to which I was referring was pointing out that FS2024 doesn’t seem to release memory. I noted that numbers displayed for VRAM use are only part of the story, using the Indy game as a counter-example. That game grabs all the VRAM, uses it all the time the game is running, and never seems to run out. It loads data, purges it, and refills it continuously for hours at a time, all “behind the scenes” while stat monitoring utilities simply show that all GPU memory is in use. But if you only looked at the monitoring software you might be alarmed because it shows almost every bit of VRAM being used and never released as you play.
FS2024 operates differently, grabbing memory as needed, releasing some of it, grabbing more, etc. At least, that is how it’s supposed to work - and is working for some of us. But it’s clearly NOT working that way for others, and finding out why is all that should matter.
2 Likes
For reference thought I would put up some card benchmarks from this site… think has been cited:
https://www.passmark.com/products/performancetest/price.php
My 3070ti is running at about 60% of a 4090.
Anyone try the 566.45 hot fix driver and see if there’s any behavior difference?
This hotfix addresses the following issues:
- [Indiana Jones and the Great Circle ] Some users may experience intermittent micro-stuttering [5015165]
- Improved stability for UBISoft games using the Snowdrop engine [4914325]
It is not adressing issues of MSFS2024.
Why is Asobo so quiet?
8 hour flight, ruined by 2 fps at 30 ft above the airport.
Go around, same again and planted her
4080Super. High settings, (not much on ultra).
1 Like
Yes, there are a bit less stutters with 566.45 on my end. May be a placebo:)
as i understand it, they are closed for the holidays right now
maybe they have a skeleton crew for emergencies, if that
2 Likes
Just because it doesn’t list a specific game doesn’t mean there’s not a fix that applies to that game too.
1 Like
No, I have tested in the same environment as previous driver and I can confirm is way less stutter.
But I think there are more audio stutters, I have to check on my end!
After every reinstall of NVIDIA drivers the installer installs her audio drivers (even if I do not select them to install) and as I use Realtek Audio I have to remove them manually in the Windows - Device Manager - Sound, video and game controllers.
These are - NVIDIA High Definition Audio and NVIDIA Virtual Audio Device (Wave Extensible) (WDM) and they create some stutters on my system If I do not remove them.
I bought the JustFlight RJ over Christmas, they even list a caution in the manual about a VRAM leak in 2024. At least it’s getting recognition. 
Don’t embarrass yourself more I suggest.
-
I wrote “FHD” before I read that the 30% meant 60% IRL for him. That’s almost 2K. Still pretty far to be called 4K as he referred to it.
-
It’s 2024, almost 2025. It’s not the time when applications are advertised as 4K compatible as it’s a pretty basic feature for anything. It’s the time when it should be explicitly stated if 4K resolution cannot be handled by today’s HW. Not an issue if you know it before and get prepared for it. You can still decide about spending your money or waiting until better HW appears. Furthermore Asobo’s own marketing materials suggested a configuration that runs the sim at native 2K resolution at best as being “optimal”.
If it would be a simple HW performance issue as Asobo stated that’s even worse as VR generally requires more graphics performance than 4K resolution (if you don’t want a washed-up mess) so they should have mentioned that FS2024 is NOT native 4K and VR compatible with the current HW available as many of the sim users use 4K monitors, multiple monitors easily reaching up to 4K or above together, or VR. Believe it or not for flightsimming large and high resolution displays are pretty normal for many reasons.
Furthermore the way this issue appears and the available resource monitoring tools show the usage/overcommitment of VRAM doesn’t point clearly to HW deficiency. The way the sim uses the VRAM seems to be a lot more inconsistent than it should be and steps you take which should immediately help the situation still won’t help for minutes (like exiting to main menu where there’s no reason to overcommit your current VRAM for minutes and not free it up immediately), like there are no definitive steps to have the issue happen. It can happen more likely on busy airports but when it really strikes cannot be defined. Sometime the same airports is lag-free for 15 minutes and sometimes the issue kicks in the first minute without having more traffic or any significant factors changing. Sometimes it happens at only 80% used of the maximum VRAM capacity and all tools (just like the built-in FPS meter) show the same values so it’s hardly a misread.
And we’re still talking about a config which run the 2020 in native 4K resolution without an issue above 30FPS. But that was DX11…
2 Likes