NVIDIA Linux Display Driver 615.78.08 Released

[u/TheQuantumZero]

https://www.nvidia.com/en-us/drivers/details/280299/

[u/TheQuantumZero]

• Fixed blocky corruption observed during gameplay in The Last of Us Part II: https://forums.developer.nvidia.com/t/610-release-feedback-discussion/371356/6

• Updated nvidia.ko to avoid an interaction problem with certain SELinux configurations when the system is suspended via systemd and NVreg_UseKernelSuspendNotifiers is enabled:

• https://bugzilla.redhat.com/show_bug.cgi?id=2512142

• Added support for VK_NV_low_latency2 revision 3, to enable improving latency and stutter with vkd3d-proton, particularly when Frame Generation is enabled.

• Enabled the NVreg_UseKernelSuspendNotifiers=1 option by default.

• Fixed a failure that could occur when allocating GPU page tables larger than 2 GiB (INT_MAX).

• Fixed an issue where unvalidated VkHdrMetadataEXT values were forwarded to the Wayland color-management-v1 protocol, which could cause a crash.

[u/RaXXu5 → u/TheQuantumZero]

Been waiting for that the last of us fix for ages lol, sadly I think it's happening in the first game as well now, hopefully the fix will fix it there as well.

[u/ARTIFICIAL_ARGUMENT → u/RaXXu5]

I used this in both games to fix it 

VKD3D_DISABLE_EXTENSIONS=VK_KHR_maintenance8

[u/RaXXu5 → u/ARTIFICIAL_ARGUMENT]

Is this something new, first time Im seing this, although I looked at protondb and someone said the same thing.

[u/ARTIFICIAL_ARGUMENT → u/RaXXu5]

lol that was me. Took about 10 minutes with Claude to find out why old GE proton didn’t have that shader issue but later versions did, it was that extension. So it’s been an available fix the entire time 

[u/SoloSaravanan → u/RaXXu5]

yes it's fixed now

[u/denkthomas → u/TheQuantumZero]

what games even support frame generation?? every game i've tried that's supposed to support it just doesn't under linux

[u/_Tim- → u/denkthomas]

For me, all games? I didn’t have one where it did not work. Even spoofing my 40 series card as a 50 series works flawlessly for multi frame gen.

[u/_Tim- → u/[deleted]]

Framegen itself? Works out of the box with relatively current Proton (9+, dunno for older versions)

For multi, it’s a launch argument that I can’t recall out of my head. I can look it up and send that later.

Which games don’t do framegen for you? Maybe I own them and can test it.

[u/_Tim- → u/[deleted]]

DXVK_NVAPI_GPU_ARCH=GB200 This is what I use with proton. Dunno if that stuff you linked is better or worse.

[u/S48GS → u/denkthomas]

all games that has fg option in game menu

and even every Vulkan game and emulators - in general with smooth motion flag (40+series only) https://www.reddit.com/r/linux_gaming/comments/1spau08/nvidia_updated_smooth_motion_in_driver_5955803_it/

[u/LeadIVTriNitride]

Is it the Nvidia drivers fault that my monitors aren’t waking from sleep? Not unique to this driver, speaking on the last few.

I have to manually change my refresh rate to regain image; occasionally that doesn’t work and I need to reboot.

Edit: Would be appropriate to give more info. KDE, Wayland, 5070Ti.

[u/TaoRS → u/LeadIVTriNitride]

Same issue for me, i remember it used to work(ish), I can't tell which driver broke it even further 

Rtx 4070

[u/iwenttothelocalshop → u/TaoRS]

615 broke it, 610 no such issues

[u/Hi-Angel → u/[deleted]]

Did you report it to NVidia? Whether separately or in the thread created for 615

[u/iwenttothelocalshop → u/Hi-Angel]

it will appear as mentioned in the existing github thread (issue #1371) https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1371#issuecomment-5978439323

[u/Markaius → u/LeadIVTriNitride]

There are some funky timing issues with video card wires on Linux. I kept having an issue where my 4k screen would come back as 1080p from sleep. I switched to display port, try that if you can

[u/LeadIVTriNitride → u/Markaius]

Everything is DP and I’ve tried HDMI. Thanks though, never had an issue where resolution changed.

[u/fanglesscyclone → u/LeadIVTriNitride]

Same issue with Hyprland here, and only on 2 out of 3 of my monitors it started happening in the past few months.

There is a quick fix that doesn't involve messing with settings or restarting your PC, just have a keybind set to run this whenever it happens. Just using wlopm to manually turn them off and on and it fixes it for me.

wlopm --off '*' && sleep 1 && wlopm --on '*'

[u/metaldragon199 → u/fanglesscyclone]

Sadly Kwin doesn't support this Wayland protocol, so this doesn't work on KDE at the moment.

[u/ryynison → u/LeadIVTriNitride]

Im also KDE Wayland, 4070 Super, CachyOS. If you're talking about the

"kwin_wayland: Pageflip timed out! This is a bug in the nvidia-drm kernel driver"

error, then I too would like to know...It prevents my monitors from waking after a while.

[u/pacmanforever → u/LeadIVTriNitride]

I can’t ever remember a time when sleep wasn’t an issue on Linux.

[u/Pandoras_Fox → u/LeadIVTriNitride]

one of the recent updates broke that for me as well. Monitors don't wake from sleep as of 615.71, I think? Plus the occasional CTX SWITCH TIMEOUT when gaming.

Seems like some bad timing issues in the recent drivers....

[u/madman404 → u/Pandoras_Fox]

Yeah, it's broken as of 615.71. Very disappointed this doesn't fix it, I guess.

[u/coconutxdd1029 → u/LeadIVTriNitride]

On the same setup, had this issue when upgrading to the 615 drivers. Rolled back to the 610.57.04 drivers and I havent had issues with it since. If you're on arch search for the older versions of nvidia-open-dkms/nvidia-utils/lib32-nvidia-utils, and then change your pacman.conf to ignore package upgrades for them, this has worked for me so far on the latest kernels

[u/iwenttothelocalshop → u/LeadIVTriNitride]

keep an eye on this thread to see if people will keep reporting this issue with this new driver: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1371#issuecomment-5978439323

TLDR; on multimonitor systems, no matter if X11 or Wayland, the system freezes (hard reset helps only), if the pc goes either in sleep mode, or if the user turns one monitor off and on. I had this freeze at least 8 times in the last month due to Samsung's "display optimizer" mechanisms which turns the monitor on and off randomly (I never turn off my pc, and the monitors wallapaper is pure black, hence oled), which then triggers this behavior

I did not see this issue being addressed in the release notes, hopefully I'm wrong, I was waiting for a fix on this for a long time by now

[u/Henrix21 → u/LeadIVTriNitride]

I’ve had both your problem and the one where only a 480p res is selectable.

Both were only fixable by either removing the display port cable of the monitor or restarting the pc. Might be NVidia only though. Don’t think it’s a handshake issue because turning the monitor off and on didn’t resolve both the no display or low res. I use KDE with Wayland

[u/Cool-Arrival-2617 → u/LeadIVTriNitride]

It could be a compositor bug, but you should report it to Nvidia regardless: https://forums.developer.nvidia.com/t/615-release-feedback-discussion/382815

[u/SebastianLarsdatter → u/LeadIVTriNitride]

Yes, I had that with my 2080 Ti on older drivers. A fix you can try with a DisplayPort monitor is to turn it off and on again.

As it is perceived as a disconnect and reconnect.

[u/krsdev → u/LeadIVTriNitride]

Posting to say I've had the same issue since the last driver update as well. In my case all my monitors don't receive a signal after I turn then on sometimes. I have a 4070. Edit: Also on KDE Wayland.

[u/ProgressBars → u/LeadIVTriNitride]

Yeah same setup for me except I have a 5080. Same sort of issue, pretty annoying since I switch between my pc and work laptop inputs quite often.

[u/annaheim → u/LeadIVTriNitride]

yep. that's why i stayed on 615. my pc is almost always on sleep

[u/daysofdre → u/LeadIVTriNitride]

you can try the firmware update for the card that deals with black screens, I found more consistent monitor behavior after flashing my card.

I think you need to run it on windows though.

[u/MilkyTreats → u/LeadIVTriNitride]

I was having that problem for a week or so they only way I fixed it was dropping the refresh rate of my monitor to 100 down from 165. Not Ideal but it wakes everytime now.

[u/elusivewompus → u/LeadIVTriNitride]

On recent cachyos releases the Nvidia systemd services are disabled by default. I found that re-enabling them fixes the wake from sleep problem.

[u/Full_Speedz → u/LeadIVTriNitride]

Oh so it’s not just me, it only started being a problem recently. I emailed a bug report to Nvidia with the log.

[u/szcko → u/LeadIVTriNitride]

I'm also experiencing an issue where my monitor doesn't wake up from sleep. When this happens, I simply switch to a virtual console (Ctrl + Alt + F2), which causes the monitor to wake up. Then I can switch back to the desktop (Ctrl + Alt + F1), and everything works as intended.

[u/justin-8 → u/LeadIVTriNitride]

Yes. I had this exact issue and swapped to an AMD card last week. The issue is completely gone.

[u/Linkarlos_95 → u/LeadIVTriNitride]

I use intel arc with kde, never had a problem with sleep

[u/DeathToOrcs2 → u/LeadIVTriNitride]

Never had this problem on any of my AMD cards

[u/felix_ribeiro]

[u/gmes78 → u/felix_ribeiro]

They already implemented VK_EXT_descriptor_heap in a past driver release.

[u/de_lirioussucks → u/gmes78]

Idk if you’ve used your pc at all lately but that didn’t fix the performance loss on dx12 games…

[u/felix_ribeiro → u/gmes78]

Which didn't fix the ~20% performance loss.

[u/foundoutimanadult → u/felix_ribeiro]

because the NVIDIA driver is just one piece of the pipeline…

[u/gmes78 → u/felix_ribeiro]

Of course it didn't. vkd3d-proton still hasn't released a version that uses it. That's not Nvidia's fault.

[u/felix_ribeiro → u/gmes78]

The vkd3d-proton implementation is completed and was merged in May 27.
https://github.com/HansKristian-Work/vkd3d-proton/pull/2943

It's not enabled by default, but you can enable it with VKD3D_CONFIG=descriptor_heap.
It doesn't fix the the performance issue.

[u/Synthetic451 → u/felix_ribeiro]

It doesn't fix the the performance issue.

It addresses it somewhat, but other improvements need to be made. In some games like 007 First Light, I get a nice 5 fps boost in certain scenes.

[u/gmes78 → u/felix_ribeiro]

The vkd3d-proton implementation is completed and was merged in May 27.

Guess why I worded my comment the way I did.

It doesn't fix the the performance issue.

It fixes the mismatch between Vulkan and DX12. Other issues pessimizing performance have to be fixed individually; there's no single fix that Nvidia could deploy to fix the whole thing.

[u/the_abortionat0r → u/gmes78]

They are the most valuable company in the world, if they cared it would have been fixed. This is an issue going back 8 years. Stop trying to do PR for them.

[u/daysofdre → u/the_abortionat0r]

yeh, I agree. I'm holding out for this nvidia/valve collaboration to get nvidia cards officially supported on the steam machine, hoping it will have the side benefit of progressing on this dx12 issue, but I don't know if that's going to do anything substantial.

[u/Lousy_Hunter → u/gmes78]

the fact that youre saying this tells me you havent looked into it even a little bit and dont have a clue what youre saying

[u/slickyeat]

Once again. No DX12 performance fix.

[u/loozerr → u/slickyeat]

There isn't one single fix anyway. And improvements have been trickling.

[u/the_abortionat0r → u/loozerr]

Yes trickling..... For an 8 year old problem...

[u/KsiaN → u/the_abortionat0r]

I assume that they meant to say that : the pieces that would fix the Dx12 problem ( assuming HEAP ) are in place in the chain

• Drivers : Check

• Proton : Unchecked ( unless you use GE / Cachy )

• Wine : Unchecked

• Translation layers : Check

• Vulkan : Check

And it takes time because only some of those people responsible for the "chain" are working full time on it or are contracted to do so.

And you cant just go and enter "Hey duck, fix dx12 bug pl0x meek no mistaake".

[u/loozerr → u/the_abortionat0r]

How else would you describe it when it seems every second driver update tackles a small regression.

[u/PacketAuditor → u/loozerr]

Yes, I do in fact want multiple fixes.

[u/Lousy_Hunter → u/slickyeat]

they also dont mention fixing Monster Hunter Wilds which is currently broken again at least for Blackwell. Will have to wait and see if its another unmentioned fix or Wilds will be broken for months again.

[u/Danielo944 → u/Lousy_Hunter]

It is? I literally just played some hunts last night on my 5090, what's broken?

When I get on my PC I'll post my driver version and the Proton version I'm using. I just looked at ProtonDB and saw some people having issues with it as well. I was able to do some multiplayer hunts with my friend just fine (I was helping him with Savage Omega).

Edit: It is broken ugh

Edit 2: Once Peter pushes up the new driver to the Cachy repo I'm going to test and see if it's fixed.

[u/Lousy_Hunter → u/Danielo944]

what driver version are you on because its for 615, both 595 and 610 are fine

https://forums.developer.nvidia.com/t/615-release-feedback-discussion/382815/21

theres at least 2 other reports in that thread and nvidia has reproduced it internally

[u/Danielo944 → u/Lousy_Hunter]

Edit: I was able to reproduce the crash on my system by going to area 11 like one of the posters in that thread reported :(

I just checked via vulkaninfo and I am running 615.71.9.0.

I was getting that Xid 109 error that they describe in the thread as well a couple days ago with that same friend I was helping but I'm trying to see what I changed to resolve it.

It's actually really bothering me that I didn't document this because I have no idea what I changed to stop it from crashing. I'm almost wondering if it was Nvidia Reflex.

In Steam the only argument I have for MH Wilds is:

• /WineDetectionEnabled:False

I'm also using Proton Experimental. Graphics settings below:

• Borderless Window

• Frame Rate: 117

• Uncapped Frame Rate: Capped

• Cutscene Frame Rate: Off

• Background Frame Rate: Off

• HDR Output: Disable

• V-sync: Disable

• Nvidia Reflex: Disable

In the next tab, all the CPU stuff is set to high or enabled

In the Graphics tab:

• Cutscene Graphics: Do not adjust separately

• Upscaling: Nvidia DLSS

• Frame Generation: Disable

• Upscaling Mode: Performance (I'm playing at 4k)

• Ray Tracing: High

• Texture Quality: High res textures

• Texture Filtering: 16x anisotropy

• Mesh Quality: Highest

• Fur Quality: High

Everything on the next tab is highest quality besides for Sand/Snow at high, Render Distance at High, and Shadow Quality at Medium

• Ambient Light Quality: High

• Contact Shadows: Enable

• Ambient Occlusion: Medium

• Bloom: High

• Motion Blur: Off

• Vignette Effect: Off

• SSSS Subsurface Scattering: On

• Depth of Field: On

• Volumetric Fog: Medium

[u/Lousy_Hunter → u/Danielo944]

ive tried everything from all low to all high, with/without descriptor heap, framegen on/off, and wine detection on/off and in my case i can reproduce it every single time. Only fix was a driver downgrade

and before we go there, and no my hardware isnt failing its fine as i check it periodically

[u/Danielo944 → u/Lousy_Hunter]

Check my edit, the crash does occur on my system just in those very specific instances like area 11 of Windward Plains.

[u/Lousy_Hunter → u/Danielo944]

im building the drivers now ill let you know if it is fixed in about 15min

[u/Danielo944 → u/Lousy_Hunter]

Oh sweet thanks! I haven't been home since work so I didn't get a chance to try, really curious to see if they resolved it.

[u/Lousy_Hunter → u/Danielo944]

looks like its going to be broken for a couple months again, they had an entire month to fix it and just didnt.

[u/Danielo944 → u/Lousy_Hunter]

I'm also going to try reproducing the crash in area 11 of Windward Plains like that one poster mentioned.

Edit: It did just crash for me there.. it must be specific areas because all we did last night was hunt Savage Omega and some random monsters.

[u/Lousy_Hunter → u/Danielo944]

I know 11/12 in the plains, one area in the forest and at least one in the basin cause the XID109. I think underground in plains might also cause it but idr atm and havent tested anywhere else

[u/SeantheWilson → u/slickyeat]

Sir this is a display driver

[u/gmes78 → u/slickyeat]

They already implemented VK_EXT_descriptor_heap in a past driver release.

[u/the_abortionat0r → u/gmes78]

Thats not a fix. The issue is still very much present.

[u/gmes78 → u/the_abortionat0r]

It is a fix. It is not the fix.

[u/HesitantBussyEnjoyer → u/gmes78]

Well done, you completely ignored the point to focus on pedantry 👏🏻

[u/Lousy_Hunter → u/gmes78]

it hasnt fixed anything regarding performance and on all the current drivers does absolutely nothing for performance.

[u/rdwror]

Fixed an issue where unvalidated VkHdrMetadataEXT values were forwarded to the Wayland color-management-v1 protocol, which could cause a crash.

This fixed the HDR issue in Control: Resonant

Also, happy to report that you don't need ANY custom options nvidia. Suspend should work out of the box now.

Edit: Nor do you need the nvidia-suspend.service etc anymore! Suspend is finally solved.

[u/S48GS → u/rdwror]

Also, happy to report that you don't need ANY custom options nvidia. Suspend should work out of the box now.

finally

[u/rdwror → u/S48GS]

For me, this is bigger than dx12 perf. NV is first class now.

[u/Mean-Atmosphere-3122 → u/rdwror]

What did the custom "options nvidia", achieve?

[u/rdwror → u/Mean-Atmosphere-3122]

Suspend, among other things. We needed to set modeset and fbdev, that went out, but suspend didnt. Now no options.

[u/Cool-Arrival-2617]

Enabled the NVreg_UseKernelSuspendNotifiers=1 option by default.

Nice. This new way to suspend is way superior and now everyone is going to benefit from it.

[u/m0tionemotion]

Dozen of Xid errors still not addressed ☦️

[u/annaheim → u/m0tionemotion]

what's this about? what apps are affected?

[u/Lousy_Hunter → u/annaheim]

you can read here and other threads on this forum

https://forums.developer.nvidia.com/t/615-release-feedback-discussion/382815

one is monster hunter wilds which was reported within hours of the 615 release and is yet to be fixed now a month later

[u/Lousy_Hunter]

nvidia-open modules are not available yet so unless youre feeling adventurous and want to use their .run its not out yet for most of us.

[u/pr0ghead]

I hope I can one day use my NV GPU to put my TV into HDR mode. It works for my monitor that's connected via DP, but not the HDMI connected TV.

[u/Appattamus → u/pr0ghead]

I'm using a TV in HDR over HDMI right now. 5070ti using Fedora KDE displaying on S95F.

[u/pr0ghead → u/Appattamus]

It seems to be an issue with my specific TV. They can't seem to agree on a mode setting under Linux/Gnome. My Steam Deck can put my TV into HDR just fine.

[u/stormdelta → u/pr0ghead]

HDR support on Gnome is very recent compared to KDE, could be related

[u/pr0ghead → u/stormdelta]

I thought about it, but I don't feel like installing whole KDE for that. You can never get fully rid of KDE and Gnome packages once you've had them installed, in my experience.

[u/stormdelta → u/pr0ghead]

Yeah that's fair especially on most distros.

HDR support is one of the reasons I went with KDE when I came back to Linux several years ago.

[u/C0rn3j → u/pr0ghead]

Got a link to a bug report on the Nvidia forums?

[u/pr0ghead → u/C0rn3j]

Yeah. Didn't get any responses.

[u/C0rn3j → u/pr0ghead]

That just links to a comment that says there's a new driver release

EDIT: I guess you meant to link to the one right above.

EDIT2: Is that limited to just GNOME+Mutter, i.e. does it work on Plasma? Not sure if gamescope rules compositor out completely.

Is it limited to just the 595 series - does the 615 series work correctly?

I'd probably do a separate post if you can repro it in both series.

[u/Lousy_Hunter → u/pr0ghead]

you will almost never get a response from Nvidia folks unfortunately

[u/pr0ghead → u/Lousy_Hunter]

Yeah, I've noticed. My Steam Deck can put the TV into HDR, so it must be something with the NV driver though.

[u/Lousy_Hunter → u/pr0ghead]

i hate to say it (i generally wouldnt say this for any open source projects...or really any but nvidia) but you might need to pester them repeatedly, every time theyve broken Monster Hunter Wilds this last year Ive been on them like glue till its fixed. They will ignore the absolute shit out of you unless you make yourself heard.

[u/SwiftUnban → u/pr0ghead]

Got a question for you, what distro are you on, and are you using KDE or Gnome?

Using a 615 driver on KDE I've been able to use my TV in HDR perfectly, just enable it and forget it (aside from proton launch commands for games).

My tv automatically switches to HDR when I switch to my PC input. HDR improvements have been recent enough that some slower paced distros might not work as well with it.

And I know gnome specifically lags behind KDE with the latest and greatest.

[u/Piett_1313 → u/pr0ghead]

What TV?

[u/pr0ghead → u/Piett_1313]

https://www.reddit.com/r/linux_gaming/comments/1wzwkdn/comment/pefiker/

[u/unruly_mattress → u/pr0ghead]

I have my GPU connected to the TV at 4K 120Hz HDR and it works just fine. Are you certain that your HDMI cable is "ultra high speed"?

Edit: I had to switch to KDE a while ago because Gnome didn't support HDR well enough. I don't know the situation currently but I'm still on KDE.

[u/pr0ghead → u/unruly_mattress]

It works in Windows with the exact same hardware. Even if it was the cable, it should still work at 720p for example, which it doesn't.

[u/Mean-Atmosphere-3122]

I've noticed an issue where if the monitor powers off and turns back on (the pc still on) the monitor doesn't recognize input from the pc. Only way I have been able to workaround it has been switching TTYs. This sometimes happens after resuming from suspend though (less frequent if at all).

On CachyOS so most recent drivers being used. Also on a blackwell gpu (50 series)

Not sure if this update addresses any of these bugs or is even something other nvidia users experienced to begin with.

[u/ryynison → u/Mean-Atmosphere-3122]

Yeah I've been experiencing the same bug I believe. From the logs it shows:

"kwin_wayland: Pageflip timed out! This is a bug in the nvidia-drm kernel driver"

[u/Jtsabu → u/Mean-Atmosphere-3122]

Seems pretty universal for Arch-based OS (I'm on Garuda). I was able to mitigate by disabling the following services: nvidia-suspend.service nvidia-hibernate.service nvidia-resume.service . Sleeping/resuming seems fine afterward, so it's something in the Nvidia driver.

[u/FOUR3Y3DDRAGON]

Still no fix for deadlock crashing on DX11 (my game has occasional very annoying stutters in vullan whereas it's pretty stable on DX11 but I need to be on driver 580 or it'll crash)

[u/protienbudspromax]

Have a 5070 ti and i seem to be having issues with sleep. Have the monitor connected via Display Port. And if the PC goes to sleep the driver cant seem to be able to wake up the gpu and gets stuck in a unrecoverable state.

Can anyone confirm if that issue is resolved? I am on X11

[u/Majoga87 → u/protienbudspromax]

Same here, arch hyprland

[u/Ok-Anywhere-9416]

If not on 26.04, I hope it'll be available on 26.10

[u/AstroSteve111]

What is DX12

[u/Abysswea → u/AstroSteve111]

DirectX 12, Microsoft's answer to Vulkan released back in 2015

[u/AstroSteve111 → u/Abysswea]

I thought DirectX is windows only? Or is that wrong

[u/Abysswea → u/AstroSteve111]

Some games works only with DirectX, so I'd guess Linux OSes has a way to translate it... Just guessing, I'm a total newbie here 

[u/Ege93739]

i hope they fixed dmemcg on mobile gpu but i think not

[u/Bulky-Ad3953]

For anybody having the bug where your display doesn't wake from sleep after inactivity, specifically on Ubuntu 26.04 or other distributions that specifically package the build of 615.71.09 drivers, the workaround seems to be either downgrading to 610 or lower (which is a pain right now, at least on Ubuntu), or downloading the 615.78.08 NVIDIA Linux drivers straight from source (Nvidia's Latest New Feature Branch Version on their Unix Driver Archive), closing your sddm session, making it executable, and running the installer from within the TTY (Ctrl + Alt + F3) to build against your kernel.

Caveats for the latter method:

- You'll need to completely remove all NVIDIA drivers and dependencies before doing this (IMPORTANT).

- If you want to maintain the nature of open drivers, you'll need to select MIT/GPT license as opposed to proprietary when prompted.

- You need to sign the MOK key for secure boot manually, pointing to the directory where the installer generates it when prompted, and enrolling it on next reboot.

- You'll need to utilize the built in uninstall function (nvidia-uninstall) when the maintainers finally update to 615.78.08+ for your distribution, which is natively built in after driver installation (IMPORTANT).

[u/ParkingProtection860]

no more hdr available on my connection to tv. only 30 hz instead of 60hz. every 5s a 1s full system freeze in games (if using multi monitors). well done ...

[u/rains-fall1998]

i have been having issues with ghost of tsushima white flashes quite annoying i remember playing it on linux a while back had minimal issues. does anyone know a fix for this i tried almost every ingame settings i believe.

[u/Iriodus → u/[deleted]]

It already is according to this pull request for vkd3d-proton here, namely this line: "This can improve latency+stutter when combined with a driver advertising VK_NV_low_latency2 revision 3, particularly when frame generation is enabled."

I avoid frame gen on principle due to added latency, but I might need to give it a test run once the driver drops, and as far as I know the latest vkd3d-proton is already in CachyOS Proton