Quoting: Eike

Quoting: tmtvlI've never seen a Variable Refresh Rate setting in a game, is that a new thing?

You don't set it. The game sends the frames in the speed it can and the monitor, if VRR is enabled and all, just displays them immediately. I guess you should disable max frame rate and V-Sync, though.

Probably depends on how the driver does things. For gsync on NVidia it will just work when fps is below the monitor setting regardless of vsync (which still works if fps would exceed the monitor refresh).

View this comment - View article - View full comments

The thing that confused me is that the 400 days is not actually linear time at all. In the Halls of Eternity the timer stops, so if you would quit out there, you could wait for ... an eternity. But back in you home cave time runs quicker. And the more you decorate it, the quicker it goes. Probably goes for reading as well. So if you do it efficiently, you can easily finish the game in less than 100 days.

View this comment - View article - View full comments

I think the Linux build has been there for over a year now. It was never visible on the store page though. I was kind of waiting for it to be formally announced, but completely forgot about it.

View this comment - View article - View full comments

Quoting: gustavoyaraujoI'm not very into this... But, does it mean We will get a better performance in games we already play on proton? Any example?

No. There is no RT in proton yet.

View this comment - View article - View full comments

Quoting: CatKillerSo, yeah, hopefully Nvidia's non-beta driver and Mesa's AMD and Intel bits will expose support for the finalised extension in short order, and vkd3d will start using it.

Very nice! Thanks for reading and summarising while I had to be productive at work. :grin:

View this comment - View article - View full comments

Quoting: CatKiller

Quoting: EhvisWas anything achieved in getting the DXR to Vulkan RT mapping to be easier or didn't the notes elaborate on that?

They certainly seem to think so. They have a chart (Figure 5 in their notes) comparing the two, and they say

It is straightforward to port code between the two APIs including re-use of ray tracing shaders written in HLSL

Thanks. I hope that this is true for translation layers as well as the code itself. As I understand it, the RT work for vkd3d was never continued because of problematic differences between the two.

View this comment - View article - View full comments

Quoting: CatKillerEdit 2:
So, reading through the notes it seems that the problem was trying to have both easy mapping from DXR to Vulkan and easy mapping of Vulkan to Metal.

Was anything achieved in getting the DXR to Vulkan RT mapping to be easier or didn't the notes elaborate on that?

View this comment - View article - View full comments

Cyberpunk 2021. Which should obviously come way before Cyberpunk 2077. And so it shall be!

View this comment - View article - View full comments

These are looking pretty great! Hardware wise the results on Windows are very solid and consistently on the heels of the 3080 (except for RT, but that's really not important). The Phoronix test do show a lot of anomalies on Linux. In both directions. SOTR looks unreasonably bad while Superposition looks suspiciously good. Also quite a few differences between the different Linux drivers. Looks like there is still some work to do in getting the Linux drivers to be more consistent.

Happy to see AMD catch up though. That means I'll actually have a choice when I'm due for an upgrade.

View this comment - View article - View full comments

I'm curious what this means:

 
Fixed an issue that caused Vulkan swapchain creation to fail for full-screen windows when a G-SYNC monitor is connected.

And how it would affect things in practice.

View this comment - View article - View full comments