Just tested LFPG F14 with Fenix A321, you can see the results.
FG on, all options HIGH with ULTRA clouds
Yes, it is a disappointment that the announced 5080 only has 16GB. The 5090 is overpriced. Maybe this new NVIDIA generation is a no-go and maybe it is better to wait for the next gen or maybe consider AMD.
3 Likes
I did two test-flights today.
Today the sim performed much better than before. VRAM utilization between 85% - 97%. 25 FPS - 35 FPS .
EDDF (Aerosoft 3rd Party) - EKCH (FlyTampa 3rd Party) with BATC traffic
EKCH (FlyTampa 3rd Party) - EDDF (Aerosoft 3rd Party) with VATSIM traffic
Airplane: Fenix A320 with 4k livery
GPU RTX 3080 TI (12 GB VRAM)
RAM 64 GB
Resolution 5120 x 1440
TAA
Raytraced Shadows = OFF
No Frame generation
Don’t know if there was a hidden bugfix in the last hotfix included. Also, I think yesterday, there was some unexpected downtime… maybe they changed something on the servers… maybe the servers are now streaming more optimized textures?
I hope there will be some communication by MS/Asobo, soon.
2 Likes
Agreed,
Guys, can we try and keep it on target here and not talk about the 5xxx series Nvidia cards?
What’s going on here is certainly to do with msfs24 and not limitations in our hardware. Lets keep discussing the software vram issues. Hopefully we have some word from Asobo imminently
10 Likes
I have the same 8GB card and you have to find a way to change your TLOD accordingly. I am still walking away from this mess. I had noticed the caching is a problem. I could run the C-172 with no problems as it uses 1 GB less of VRAM than the B-787. I could sorta get the B-787 to run, but only for one flight then the FPS went down the tubes again. Had to reboot. Another sign of poor memory management in relation to their cache (I set aside 128GB).
I noted that the 2020 B-787 flys way better and uses less VRAM also, but its flight controls are busted in 2024. I think you can look forward to that as they put more planes back in the marketplace. There is an un-deactivatable B-787 Base model that is probably the source of the problem.
Later this year will have to buy new W11 computers and one will be with the RTX - 5080. I need that for data analysis, but I am sure? it will help here, maybe.
Good luck, makes interesting reading.
1 Like
I’ve seen you post this several times - this is not my experience. The FS2020 787-10 flew fine for me for 4 hours yesterday from KORD to KSFO - everything worked as expected, at least until landing and the FS2024 physics glitch I encountered on braking. VRAM use on that flight ranged from a low of 9.5GB flying over the Great Plains west out of Chicago to a high of about 12.8GB on final approach over the Bay into 28L at San Francisco. Up to that point, the flight was fine.
But this is really off-topic in terms of trying to figure out what is triggering the sim to over-subscribe peoples’ VRAM.
1 Like
Maybe you have a 12GB card. I have the 3070ti that only has 8 so I watch pretty carefully. The 172 stays down around 5 GB and is OK and goes to 6 on landing with the textures in the runway. I did manage to get the B-787 to fly in the MS2024 version but it was by hook and by crook and it would not consistently work. For me that starts at 6 and goes up over 8 when the trouble begins with the runway textures so it stutters on landing.
I almost got the 12 GB card but my motherboard would not work with it according to ASUS. Will build a new computer later in the year. MSFS is a secondary use of this machine.
Yes, I had the same experience with a better performance after the January 9 hotfix, although the description does not indicate this.
https://www.flightsimulator.com/release-notes-1-2-11-0-hotfix-available-now-msfs-2024/
So, i did a test flight between KSLC and mineapolis…
At KSLC, performance was acceptable (with the a321 from inibuilds), the flight was really smooth in terms of FPS, and the approach through the clouds more than ok !
But… passing the threshold of the runway, at 50 feets… FPS went down to single digit, and it has been terrible ! After stopping the aircraft it became a bit better, but never recovering (max 20 fps)…
I guess there is too much things to load at the same time in big airports… it was better managed in 2020 for sure…
1 Like
This is why TLOD should be adjustable.
1 Like
You mean lowering it even more than 50? Having TLOD at 10? First thing is that the sim then looks like a game from 20 years ago, second thing is that it barely even helps.
2 Likes
My best guess is your rolling cache had not yet streamed the destination airport.
So there were delays whilst the CPU streamed ground textures into the cache file, sent them to the GPU which then had to render a more detailed scene. The delays add up to very low fps for a few seconds.
After landing those download delays stopped, so fps improved. But the GPU RAM may have been overloaded.
One trick is to spawn a Cessna at the destination runway, watch Task Manager network activity, pan around until the network activity stops.
Press ESC then Q and pan the freecam around until there is no more network activity.
That awkward process is a way to force-download textures into the rolling cache. With airport textures in the cache before you land, the landing stutters should be reduced.
Looking at MyLibrary there will be an option to download favourite airports…eventually.
Hope that helps.
Have you all ask your question about this problem or others for the upcoming developers stream?
There is a link there to do so,
web form
Yes, I did, and asked if they were continuing to say that it was a “hardware limitation issue” or if they were working on it…
2 Likes
I would strongly suggest - those of you submitting questions about this issue - that you provide details/links to posts in this thread showing the sim demanding more VRAM than is present on peoples’ systems. You know, where people load in and DevMode is showing 9+GB in use on an 8GB card; 14GB in use on a 12GB card; 19GB in use on a 16GB card, etc. When this is occurring for people using 1080p or 1440p, NOT running multiple 4K screens, that’s even better, as it demonstrates conclusively that the problem is not simply people trying to push too many pixels at once.
They need to see the situation is actually the sim, not the simmers. Details will help guide that discussion.
4 Likes
Well in this thread there are screenshots showing that.
There are also screenshots showing the VRAM only half-full, AND at the same time the shared RAM is still containing several GB of overflow GPU data that is not being cleaned up!
So the problem should be pretty clear already.
The developers are not going to have this thread up on their screens if/when Jayne reads the question on-stream. So at least referencing some details in the question is a better move if you want a real answer, rather than just asking, “Are you still claiming excess VRAM use is a hardware problem?”
and never mind the fact that you can run 2020 at tlod 230 and fps still hold strong
2 Likes
Ok, then maybe a better question would be: "Have you found a solution to the gradual FPS degradation caused by shared GPU RAM that is filling-up even when the main VRAM is less than full?"
The fixation on the Devmode is part of the problem. It doesn’t clearly show the split between (a) the actual VRAM used and (b) the amount shared GPU RAM.
Devmode doesn’t show that VRAM has headroom to spare, yet at the same time as the shared GPU RAM is filled with several gigabytes of presumably redundant video data that is slowing everything down.
NB. To see these things (and graphs of how it progresses over time) they should instead be looking at the standard Windows Task Manager’s Performance => GPU tab.