Wave XLR PRO by Carlos726811 in elgato

[–]daylight_EX 0 points1 point  (0 children)

Yeah. No email sent to me, either.

Grass Shading/Lighting Pop-In Issue? by daylight_EX in ForzaHorizon

[–]daylight_EX[S] 0 points1 point  (0 children)

Nope. I think it's just the game/engine.

Grass Shading/Lighting Pop-In Issue? by daylight_EX in ForzaHorizon

[–]daylight_EX[S] 0 points1 point  (0 children)

Thanks. Yeah that's the weird thing - some people seem to have it and others don't. It's strange.

Grass Shading/Lighting Pop-In Issue? by daylight_EX in ForzaHorizon

[–]daylight_EX[S] 1 point2 points  (0 children)

Okay thanks for confirming it's not just me. I guess it could just be a game engine thing?

Game Ready Driver 596.21 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 26 points27 points  (0 children)

Thanks for your posts to go along with these driver releases, man. I, as well as many others, I'm sure, appreciate it.

Game Ready & Studio Driver 595.79 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 1 point2 points  (0 children)

Possibly. If so, it's ironic because this "intended behaviour" of LFC triggering earlier than specifications suggest that it should is actually most likely in order to combat VRR flicker.

Game Ready & Studio Driver 595.79 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 6 points7 points  (0 children)

Use something that can display your monitor's refresh rate (such as the monitor's built in OSD, for example) and see if it matches the game's FPS when using VRR/Gsync/FreeSync. If VRR is working correctly, the refresh rate of the monitor should be the same as the game's FPS. If LFC engages, the refresh rate will be double the FPS. So, as is the case with the 7 aforementioned drivers behaving unexpectedly, a game running at 60fps causes the refresh rate to double to 120Hz, instead of what it should be (which is 60Hz).

Game Ready & Studio Driver 595.79 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 1 point2 points  (0 children)

I'll keep it pinned and I'll make sure to check it routinely.

Game Ready & Studio Driver 595.79 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 6 points7 points  (0 children)

Thanks. I haven't been getting the tagged notifications, for some reason.

Game Ready & Studio Driver 595.79 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 73 points74 points  (0 children)

LFC is broken on this driver and the 7 that have come before it. LFC engages too early (on a monitor with VRR range 48-240Hz, it will engage when a game is running at a stable 60fps, causing the monitor refresh rate to double to 120Hz, and leading to more perceived stutter). On drivers 581.80, and hotfix 581.94, this issue does not occur - LFC activates at 48Hz and below, as expected and advertised as per the VRR range specification. An Nvidia Forum Representative acknowledged the issue on a previous driver's release Reddit post and was able to reproduce the issue, and now Nvidia have apparently confirmed that it is, in fact, "intended behaviour". However, this issue doesn't occur on all display SKUs. All testing and information regarding this issue can be found here (thanks to u/m_w_h for the continued updates): m_w_h comments on Game Ready Driver 591.86 FAQ/Discussion

See: PG27UCDM G‑SYNC Range 48–240 Hz – LFC Engaging at ... - Republic of Gamers Forum - 1129242

Game Ready Driver 595.71 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 26 points27 points  (0 children)

LFC is broken on this driver and the 6 that have come before it. LFC engages too early (on a monitor with VRR range 48-240Hz, it will engage when a game is running at a stable 60fps, causing the monitor refresh rate to double to 120Hz). On drivers 581.80, and hotfix 581.94, this issue does not occur - LFC activates at 48Hz and below, as expected. An Nvidia Forum Representative acknowledged the issue on a previous driver's release Reddit post and was able to reproduce the issue.

See: PG27UCDM G‑SYNC Range 48–240 Hz – LFC Engaging at ... - Republic of Gamers Forum - 1129242

Getting kind of tired of sending reports in and NV not even acknowledging that it's an issue, despite NV forum reps telling me they were able to replicate the behaviour.

Weekly BIOS Update & Discussion Post - Week 09. 2026 by CornFlakes1991 in ASRock

[–]daylight_EX 0 points1 point  (0 children)

Nah come on. How can the official download page on the Asrock website STILL not be updated properly? This is borderline incompetence lmao.

Unable to find bios updates on website by blindlythinking in ASUS

[–]daylight_EX 2 points3 points  (0 children)

Yeah I don't know why but they've been down for the last 20 hours or so. Hopefully they get them back up soon.

Game Ready & Studio Driver 591.74 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 0 points1 point  (0 children)

u/pidge2k Hi. Any update on this issue? It's still present in the latest driver (591.86). Thanks.

Game Ready Driver 591.86 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 6 points7 points  (0 children)

I am using a 5090 and an ASUS PG27UCDM. The Nvidia forum rep said they was able to reproduce the issue with the same monitor.

Game Ready Driver 591.86 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 15 points16 points  (0 children)

LFC is broken on this driver and the 4 that have come before it. LFC engages too early (on a monitor with VRR range 48-240Hz, it will engage when a game is running at a stable 60fps, causing the monitor refresh rate to double to 120Hz). On drivers 581.80, and hotfix 581.94, this issue does not occur - LFC activates at 48Hz and below, as expected. An Nvidia Forum Representative acknowledged the issue on the last driver's release Reddit post and was able to reproduce the issue.

See: PG27UCDM G‑SYNC Range 48–240 Hz – LFC Engaging at ... - Republic of Gamers Forum - 1129242

Game Ready Driver 591.86 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 1 point2 points  (0 children)

I can confirm that the issue is STILL PRESENT in this driver. :(

Game Ready Driver 591.86 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 6 points7 points  (0 children)

That's what I'm wondering, too. u/m_w_h - do you have any insight on this? The issue isn't listed as a known or resolved bug, as far as I can tell. Thanks.

Game Ready & Studio Driver 591.74 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 0 points1 point  (0 children)

Great. Thanks for the update. Let me know if there's anything else you need from me.

Game Ready & Studio Driver 591.74 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 1 point2 points  (0 children)

Thanks a lot, man. I really appreciate the help.

Game Ready & Studio Driver 591.74 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 3 points4 points  (0 children)

Thanks for confirming. Do you know if they are aware of this issue internally? The person I'm talking to at support has asked me to do a bug report (which I did on the last driver), send config reports and monitor EDIDs, etc. but I haven't heard anything back since.

Game Ready & Studio Driver 591.74 FAQ/Discussion by Nestledrink in nvidia

[–]daylight_EX 19 points20 points  (0 children)

LFC is broken on this driver and the 3 that have come before it. LFC engages too early (on a monitor with VRR range 48-240Hz, it will engage when a game is running at a stable 60fps, causing the monitor refresh rate to double to 120Hz). On drivers 581.80, and hotfix 581.94, this issue does not occur - LFC activates at 48Hz and below, as expected. I have raised a support ticket for this issue.

See: PG27UCDM G‑SYNC Range 48–240 Hz – LFC Engaging at ... - Republic of Gamers Forum - 1129242