Yet 780 Ti (fall 2013 650€) is still ~RX 480 performance (at least when VRAM pressure or explicit APIs don't kill it) and old hardware is supported ~forever in Mesa and kernel. It's unfortunate.

View this comment - View article - View full comments

Try with Lutris 0.5.9.1 and lutris-ge-6.19-1, there is a checkbox for NVAPI/DLSS support in the advanced runner options that should work.

Though I think something's wrong with DLSS and at least recent 495.29.05 driver, the result in Control or Deathloop seems to look more pixelated than on Windows.

View this comment - View article - View full comments

Would you please not try forcing your opinion onto me? I personally can live with you being able to play with more than slightly degraded IQ. I found FSR to look terrible in every game, unlike DLSS 2(.2). You won't be able to change what I can perceive on my display...

View this comment - View article - View full comments

Quoting: scaineEh? FSR still works serious magic at both 900p and 720p upscaled to 1920x1080. As I said earlier, I'm playing Cyberpunk at 900p upscaling to 4K. There's definite degradation, but it's still stunning AND it plays at 60fps too.

It is not possible for it to look stunning, as the game's TAA is already kind of crappy in native 1440p.

View this comment - View article - View full comments

Quoting: Purple Library GuyAnd isn't FSR sort of . . . more broadly applicable? 'Cause, like, doesn't DLSS have to be "trained" on a per game basis? Whereas, doesn't FSR not have to do that? So in theory, FSR would work with any game, whereas DLSS would work on (any game whose devs have made the effort to "train" DLSS on their game).

DLSS >= 2.x is a generic temporal upsampler: One version works for all current and future games, as long as they provide it with the data it needs (previous frames, motion vectors and perhaps other things). When a game has proper TAA, it already uses this data by itself, so DLSS implementation efforts are within scope for a lots of devs.

Thing is FSR is completely useless for everyone without 4k display, as it looks just terrible with lower resolutions. It's pure postprocessing, so it's easy to implement. But what is it good for when you can use it everywhere, but don't want to regardless...

Though I really hope Intel's XeSS (basically the same as DLSS 2.x, but open source) beats DLSS so we can leave annoying vendor locks behind without compromising on quality (unlike FSR)...

View this comment - View article - View full comments

For whatever reason it didn't work in Wine (no Proton runtime) in RDR2 with the Nvidia shim libs only in system32 folder (+native override), I had to copy them into RDR2 main folder. Anyone have an idea why it is that way? Doesn't seem to be required when running Lutris-/Wine-GE.

The DLSS implementation in RDR2 is pretty bad though. If somebody wants to see how good DLSS can look, e.g. Doom Et. is the way to go (I'd also replace the version shipped by the game with the 2.2.6 DLL, as it shows much less smearing artifacts).

View this comment - View article - View full comments

I could copy and paste my usual NV driver situation rant from another site here, but to keep it short: Way too sucky, hello Windows...

View this comment - View article - View full comments

I guess she really wants her money back (or what she thinks to be hers, the one thing she hasn't forgotten about).

View this comment - View article - View full comments

Quoting: Leopard

Quoting: aufkrawallMemory leak (or what would be the appropriate term) with VKD3D-Proton is finally fixed.

Vkd3d master has a workaround for it, so are you sure if driver really fixed it or it is just vkd3d workaround?

https://github.com/HansKristian-Work/vkd3d-proton/commit/403d1f97434b6dbbdb3c8ab9391d6903846fd8d6 [External Link]

Good point, though RAM usage also stays low when using latest 2.4 release that doesn't include this commit.

According to vulkaninfo, this driver also includes VK_KHR_wayland_surface extension.

View this comment - View article - View full comments

Memory leak (or what would be the appropriate term) with VKD3D-Proton is finally fixed.

View this comment - View article - View full comments