At the end of the day (or month) it's just one data point. A difference of a tenth of a percent is not statistically significant. The only thing that these numbers are useful for is long term trends and one value doesn't change anything.

View this comment - View article - View full comments

Quoting: kaktuspalmeNice! For me personally it means I will buy more games on steam and less on PS5.

I wonder how it technically works though. Why does it need a special compositor for that and what about Kernel, DRM etc.? Are there changes too?

I was wondering about the same. Seems to me it needs support on various levels. Maybe gamescope can bypass the limitations of X11 (and Wayland?) and display it directly through Vulkan support. Not sure how it all connects together. Can't be as simple as just Vulkan support because then nvidia would have hooked it up already.

View this comment - View article - View full comments

Have a good christmas holiday!

View this comment - View article - View full comments

Same, didn't see any improvement. From what I've heard, it only improved CPU bound scenarios in DX12 a bit in some places, so nothing major. Even in DX11 I'd like some improvements because sometimes there micro stutter that even GSYNC can't fix.

View this comment - View article - View full comments

Quoting: lejimsterCouldn't believe it when I saw the size of the update being downloaded the other day. Its one of the games I meant to play, but when I first got it, Linux compat was buggy. I should have played I when it was stable. I guess I have to wait some more now.

DX11 version is perfectly stable. The issues seem to be exclusive to the DX12 version. And the only thing you miss out on is ray tracing (which is barely playable anyway) and DLSS/FSR, but you don't really need it with the DX11 build.

View this comment - View article - View full comments

Played some on both DX12 and DX11 today. DX11 gives me slightly higher fps, but it's not really noticeable and it looks exactly the same. Do have to say, the Ultra+ settings are very nice for draw distance but they are brutal on fps. I'm managing about 65 fps with it around the White Orchard area. I think this is why I have pretty stable fps and similar numbers to DX11. I hammering the GPU and not really giving it a chance to become CPU bound. As far as I understand, the real problem starts when D3D11on12 starts hitting core limits.

Honestly, I don't understand why they went the D3D11on12 route. They could have (and it's what I expected) back-ported the DX12 support from CP2077 into the game for a more solid implementation. Instead using a translation layer, that microsoft itself says not to use, and making the game cpu bound seems like a bad choice when you're trying to repair some of the reputation damage for prior releases. I imagine it would have been better received if they never put the RT in and stuck with the DX11 version that still has a good list of graphical improvements.

View this comment - View article - View full comments

Quoting: mahagrDoes anyone know how to enable raytracing and DLSS in the game? They were grayed out.

Use:
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%

But you really don't have to bother because it'll crash very quickly after enabling RT. And I've read that savegames that are saved with RT on will not load properly with it off.

View this comment - View article - View full comments

The most interesting observation was that the game uses d3d11on12 for the dx12 "port" of the game, something that microsoft says NOT to do for complex 3d software because it's not optimised at all an causes higher cpu loads. In that regard it's something similar to the RTX remix from Portal RTX that also converts the game to another API in order to make it possible to inject some RT into it. Not ideal. I'll be continuing some gameplay test tonight and see how the DX11 version runs and what the differences are.

View this comment - View article - View full comments

Well, al experimenting done I think. Ray Tracing is a no-go. Despite the terrible FPS hit, it crashes between 3-30 seconds the game becomes unresponsive (although various sounds keep on going). Without RT, performance in D3D12 mode seems good. Still locked to 60 with everything on Ultra+. The only thing I can't get working is NV Hairworks. Supposedly that can be made to work fine in DX11 by adding d3dcompiler_47.dll, but that same trick produces another lock up in DX12. So now the choice is between Ultra+ or hairworks. Now to see if there are any issues while playing.

Edit: all of this was with vkd3d-proton master from tonight. Without the fixes from today it didn't work at all.

View this comment - View article - View full comments

The good news is that several issues seem to have been fixed in vkd3d already. You should probably read issues loosely since they appear to be on the CDPR side and they "just" needed to be worked around.

View this comment - View article - View full comments