Do you have the same issue if you follow the OP’s steps to reproduce it?
• No
Provide extra information to complete the original description of the issue:
• G36 plane instantly causes VRAM to spike to over 12GB which causes frames to drop from 60+ to single figures
If relevant, provide additional screenshots/video:
•
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• Massive fps/stutters when trying some planes like C-17, A321, A330.
Other planes like A400, A320neo have flaweless performance which I’m happy to.
If relevant, provide additional screenshots/video:
• Don’t have.
It does work, the in sim fps counter just shows the fps before framegen.
Negative! Its theSmartDocking in DevModeToolbar that breaks FG.
Unlike 2020, ‘DevMode-show fps’ now includes frames generated by FG.
Aha, well i stand corrected!
I don’t use FG, but that’s very interesting info. Thanks.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• GPU Watt drops down to 140 W and lose FPS. At the begining of the flight everything is good, like you can see on the screenshots. After a while have massive FPS drops, and the only thing i see is the GPU W drop. Happens with airliners like 787, A321, etc. With GA planes in career mode is good and stable.
Correction: Happened with a Cessna 172 too. Never happened before, always had 55 FPS stable with C172. I was in a field now, no city around, no buildings, anything and it just went bad and didnt recover. Even backing up to the menu didnt solve the issue, had to restart the game to be good again.
How they still say its about “hardware limitations”??
If relevant, provide additional screenshots/video:
•
You should try turning off the Dev Mode. It will leave the FPS counter showing with it off. I was encountering the exact issue as you. Once i turned off the Dev mode it worked fine and FPS stopped the random dipping.
Hello. Here’s a question, MSFS 2024, Steam. After a long flight (career and free flight), after touching the strip, a problem with performance arises. At the moment of the run, a drop to 2-3 FPS begins. But at the same time, as soon as the plane stops on the strip, the FPS rises to 45-50, as soon as you start taxiing - the FPS drops again to 2-3. At the same time, everything is fine during takeoff and flight. As an experiment, I changed the settings to low, the drop in FPS while the plane is moving remains. This happens both at large airports and on unpaved strips.
I also observed: if you open the tablet at the moment of the FPS drop, the FPS returns to normal and the plane remains in motion, but as soon as you start taxiing, the FPS drops again.
OS: Win11
MSFS 2024 steam version 1.1.10.0
Hardware: Ryzen 5 7500F, RTX 4060 8Gb, RAM 32Gb DDR-5, Ethernet 150 Mb/s
Just loaded up 2020 after a couple of weeks using 2024. The performance difference is unreal. 2020 feels so smooth, even at really heavy airports. 13600k RTX 4070 32Gb
BLUF: JFK not ready for prime time with a 3070. I did another flight this time from Newark and in the sky ran 40-50 FPS but as soon as on the ground with texture ran 15-20.
The ILSs are quirky too with poor pickup and bad offsets.
This is worse than SFO. I did fly it 5 times so it is not the cache.
Does look good… just slow and pretty much unusable on the 3070… if it does not work or runs as slowly on the 4090 it is definitely them:
There might be truth to “HW limitation” conclusion Asobo gave us during the dev q&a. To me, it feels like the root cause of this issue is actually poor communication from MS/Asobo around published system requirements and specifically lack of non-RT (raytracing) and RT specific specs.
I’m here with 5800X3D, 4070 Ti, 32GB RAM.
With RT shadows enabled at 1440p (100% render scale, TAA, the rest of settings is a mix of high/ultra), custom EETN scenery and Fenix A320, I run out of VRAM before I even load in and FPS tanks into single digits - absolutely unplayable.
By simply unticking RT shadows box, in exactly the same scenario my FPS increased by an order of magnitude - to mid 70s.
As an example of what MS/Asobo should’ve published, here are specs from the recent Indiana Jones game:
Don’t get me wrong, Asobo should do their best at optimizing the game (especially in the current state of the world, where games are released half-optimized and rely a lot on DLSS/frame gen to bring it to playable FPS numbers) and maybe there is some memory leak, but there is indeed a point where you will just run into HW limitations and that point should be communicated much clearer, so we - customers - can better understand what performance to expect with the hardware we have.
That’s true, but it shouldn’t be the case. The program is not handling DX12 VRAM usage properly. Whether the programmers don’t understand how to write code that dumps VRAM registers when textures aren’t being used, or something else, it ain’t working right.
I think they’ll get it right eventually, but right now that ‘Recommended’ spec is a joke.
Guys, maybe I can help some people. I had a problem where the flight always went perfectly smoothly, but when it came time to land the FPS dropped to 5.8; I went for a test flight, lasting approximately 1 hour in the Fenix (A320), and after I took off I decided to close Coault (GSX) in the hidden applications bar. Result: I never had an FPS drop again when landing, and the FPS remains high after touching the ground, and even opening the Coault after landing the FPS remains stable.
GSX has an option to close the application when you are at 10,000 feet elevation or above. Had that option been selected? I will try closing it though, to see if I get any benefit during the landings.
So far, it seems to me all the specs they published are for non-RT scenario and they just forgot to communicate this to us. If the come out and say those specs are for the RT scenario (RT shadows = on), then we have a problem where stated and delivered do not match in the slightest.
Today, I did a reinstall of the sim along with updating the Nvidia driver to the newest version. Somehow (?) this has seemingly increased performance a lot and decreased VRAM usage. Except for rare stutters the sim seems to run perfectly smoothly with Frame Generation on my system now even in demanding airports on (almost) Ultra Settings. My 32 Gigs of RAM are the likely cause of the (rare) stutters that I still experience (today these were especially prevalent with thunderstorm weather and RAM usage was even higher here) but this was expected from the System Requirements. Upgrading to 64 Gigs would probably alleviate that but already the sim is now running a whole lot smoother than 2020 ever did.
Except that users with 8GB VRAM cards (“Recommended”) who aren’t using RT are seeing their VRAM saturated, and Shared RAM (which is 1/10th the speed of VRAM) being used to take up the memory overflow, causing a huge drop in FPS.
Even weirder is that users with 10, 12, 16GB are seeing excessive use of Shared RAM.
Xbox uses Shared RAM as well, but it’s handled completely differently than how Windows handles it.
Perhaps the “Recommended” spec should have specified: “1080P with Medium Preset ONLY,” because trying to use an RTX 3070 @ 4K seems like an exercise in futility at this point.
Like to try this but no idea where this puppy is hiding?
Coault (GSX) in the hidden applications bar?
Looks like this is a paid add on, not coming with the regular install? Not really familiar with the product.
I can assure you that 8GB cards are running out of VRAM at 1080p and with medium preset selected. GA will run fine, but loading in iniBuilds or other high fidelity aircraft at a larger airport in photogrametry will tank the performance. And once it has loaded in you can change aircraft and location but your performance is gone, you have to restart the simulator to get your framerate back it seems.
