Re: Frame Generation locked rtx 4090

I think it is a really shady tactic to sell the hype at beta with stuff disabled at launch.

@GhastlyTT  What do you mean? The entire reason that there are posts about this is that it is greyed out and disabled in the menu.

@mackanz72  It makes perfect sense to delay the feature as there's a lot of visual glitches and artifacts present in the current state of the game. Even if you would be able to run DLSS-G with the game now, it would look really bad. And lets be real here, DLSS-G isn't the sole reason that you are buying F1 23.

@dotazuredit's also greyed out and disabled in F1 22 if you have HDR turned on. That doesn't indicate that it's completely unavailable at this time. What I mean is if it's a feature coming in a future update, as alluded to by Nvidia's press info, it should be identified as such in the game itself or the menu option should be removed entirely until it's in the game.

*I now see that I wrote disable when I meant remove in my original post...

No, but it is the reason i got a new screen. And why wouldn't EA say so before people are buying the game? Especially since it was working in beta.

For those who want to enable DLSS-G/frame generation before it is officially re-added to the game can do so manually doing so by setting DLSS-G to true in hardware_settings_config.xml

<dlss_g enabled="true" />

You need to set Nvidia Reflex to "On" (not "On + Boost" as it currently seem to be broken and enable half rate V-Sync, or even quarter rate V-Sync)

0 = Off, 1 = On, 2 = On+Boost

<reflex mode="1" />

Frame generation will still be greyed out in the settings, but it will be fully functional* and generating pseudo frames.
*Potentially buggy in some scenarios. 🙂

Edit: I'd recommend to replace the nvngx_dlss.dll and nvngx_dlssg.dll that are bundled F1 23 and replace them both with version 3.1.13 (both available at Techpowerup).

This whole DLSS 3 feature by Nvidia is a big crap, why does it require each time an update from Nvidia and not just by the game developer.

@c6829615538f9c53 Currently Nvidia Reflex is required for DLSS-G to be fully functional, and the "on+boost" setting is currently broken in F1 23 as I previously explained.

In my case I have DLSS-G running and fully working when using DLSS and DLSS-G version 3.1.13, did you update the DLLs or are you using the bundled DLLs?

If this doesn't work in your case, this might be an indication why they have chosen to not let users enable it.

Anyway, the behaviour you are describing sounds like boost actually are enabled as that seem to erroneously using half-rate, or quarter rate V-sync, which will mean that you get either 72 or 36 fps if your monitor is normally running at 144Hz.

Can you verify that you have Reflex set to 1 (On) and not 0 (Off) or 2 (On+Boost) <reflex mode="1" /> in hardware_settings_config.xml.

You might also want to check whether vsync is true or false in hardware_settings_config.xml.

The blur you are describing is not likely to be related to DLSS-G. It is more likely to be the anti-aliasing (TAA, DLAA) or the upscaler that you are using (DLSS, FSR2, XeSS) being the actual culprit regarding that matter.

DLSS-G is "just" interpolating frames in-between real frames, DLSS is the tech upscaling the resolution of frames, it is two different technologies.

---

@c6829615538f9c53 wrote:
@dotazured
After I updated the DLLs, the problem with the half frame rate disappeared. But the frame generation still doesn't work.
I have an average of 144fps in the benchmark, sometimes a few fps more or less. The 144fps is a coincidence :-) Nothing to do with the 144Hz HDR1400 monitor :-)
Whether I enable DLSS-G or not doesn't change the fps or the CPU or GPU load.
Tried all possible options, including HDR off and on, full screen, fixed mode, etc.
Unfortunately, no frame generation is active for me.
Are you sure it really works for you? :-)

Here is a link to my current settings and a screenshot of the benchmark:
https://www.dropbox.com/scl/fo/0l6b5kabhkgexqshzd0ae/h?dl=0&rlkey=be6k5oyglg1m0wjyitbdwxt5w

Maybe you can compare it with your settings?

Thanks

---

According to the config file you provided you have HDR enabled.

<hdr mode="1" peakNits="1000" />

Try closing the game and then setting "hdr mode" manually to 0.

Other than that I can't see anything that would be a reason for concern.

I assure you that it is working for me as I am able to get a significantly higher (and smooth) experience with every setting maxed out, including RT on high.

But it isn't impossible that it is somewhat broken on certain hardware configurations.

I think that it is pretty clear that there's a reason behind it being disabled for the time being.

Edit: I have noticed that some settings might overwrite the DLSS-G setting and in some scenarios you would have to manually enable it in the config again.

@dotazuredThat's an excellent observation! Thanks!

I have been playing around with the development versions of SL and DLSS-G for the last hour or so and got to a point where my game no longer started, after rechecking/re-validating the files I am no longer able to get DLSS-G working again. ☹️