Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.
3 tags are required - add them in the tag section next to the title above:
One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue: frame generation keeps being dropped/made inactive
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Every session since SU4.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Open sim, start flight, Nvidia frame generation is toggled on in settings.
Fly around a bit, frame generation toggles off as observed through steam FPS counter showing “FPS” rather than “FG”, with noticeable drop in performance.
Go back, toggle frame generation in settings off, then on (or alt-tab from full screen) to reset FG, fly around a bit more, then lose frame generation again.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
[PC Only] Are you using Developer Mode or have you made any changes to it? No
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
[PC Only] What GPU (Graphics Card) do you use? Nvidia RTX4080
[PC Only] What other relevant PC specs can you share? 12700k, 64gb DDR4 RAM, NVME, Ethernet
MEDIA
Please add a screenshot or video of the issue occurring.
FrameGen is deactivated by the system as soon as the MSFS windows loses the focus. it is not a bug, it is a feature. If you play in full-screen, it is activated automatically again as soon as the MSFS gets back the focus, but not in windowed mode, as far as I know.
There are several identical threads already in the forum, it is always a matter of window focus. Just use the search function.
this is not what is happening, this happens in both full screen or windowed mode, and no other programs running the background. im not clicking off the screen, im still in the sim. clicking the mouse on screen does not bring frame gen back
I have used the search, this is the reason why I’m asking as this question has not been answered. What do you mean by “untenable”? This is a new issue, I have not had this prior to SU4 finalizing, it was not present in the beta, and not in previous sim updates. I’m simply reporting a bug…
@Trex2269152 as you have experienced, windows focus isn’t always the culprit. In 2024, it seems FG can be lost if the base frame rate falls below your monitor’s frame gen lower range. Usually around the mid 40’s and below.
(monitor’s Gsync lower range, not, frame gen lower range)
whats the solution to that? I have not encountered this issue previously and i’ve been on MSFS since launch of 2020, with a 40 series card for years now successfully using frame gen
You are most likely CPU limited in those situations. That is usually caused by TLOD settings being to high or perhaps having Trees or a lesser extent Buildings settings to high. Also, the setting for the cockpit screens set above medium hits the CPU a bit hard as well. Just my experience.
One last edit: It seems to me that 2024 doesn’t interact with the nvidia drivers as well as 2020 does. Especially those released since the 50 series cards. Again my personal view.
@Trex2269152 I experience it from time to time in very, very demanding situations. But it always corrects itself as the demand lessens. But I run mostly ultra and Tlod 350 in the a320 mostly. 9800x3d, 5070ti. It could help to DDU clean install your nvidia driver and clean caches. But beyond that, I really don’t know.
What is the “monitors frame gen lower range”? What has the monitor to do with frame gen?
The goal of frame gen is to increase FPS is a way that it allows a smooth display anytime. It is usual that the base frame rate is far below the lowest support Hz of the monitor. This is no problem, it is the desired use case.
yeah, thanks for your help, just tried a clean driver install and still seeing the same issue unfortunately… appreciate you actually listening and trying to sort it with me unlike the other poster. Will keep trying to debug, but looking forward to if anyone else has seen this issue
Yeah, I agree that FG just doesn’t seem to have as smooth a functionality interacting in 24 vs 20.
Edit: I’ll correct an obvious mistyping for the nitpickers, where I typed FG can break when fps is below the monitors lower frame gen range, I of course meant monitors lower gsync range.
Ah. And why couldn’t you give a reasonable answer right away? Because in its current form, the sentence is nonsense.
And the fact remains: it is a standard use case for Frame Gen that the FPS drops below the monitor’s G-Sync limit. I’ve never heard of this leading to Frame Gen being disabled. Do you have any sources for this? G-Sync controls, how the monitor displays the images. It has absolutely nothing to do with Frame-Gen. Ok: Stutters become visible as soon as the FPS fall under the G-Sync range of the monitor. But Frame Gen is still working.
Alright, update time. After pretty much a full day of testing, reinstalling drivers, adjusting settings, etc. I have narrowed down the culprit to the vsync on option in the nvidia control panel. This is very unfortunate as having this off results in some pretty severe screen tearing… and I’ve had this setting on ever since the sim launched, and also used it with 2020… not sure what has changed recently to have this conflict with frame gen, but heres hoping that either a sim side or driver side fix is released relatively soon.
TLDR: Vsync in NVCP set to ON will conflict with frame gen and cause it to stop working periodically.
Can’t confirm. I’m using frame gen together with V-Sync and G-Sync without any issues, as do most of the users. Have a look in the G-Sync threads, there are hundreds of users confirming it also. SU4 has changed nothing regarding this.
I don’t know what to tell you man, the only thing I’ve toggled off is vsync and now FG is back working as it was before. I’m just sharing my experience, you can stop arguing about it…