So I uncountered a weird bug / feature while testing the wine-devel 3.3 version. My FPS is locked to 30 except the inventory is locked to 60. No settings seems to unlock either of them. Limiting FPS from the game graphics menu to 30 does limit the inventory FPS to 30, but unlimited still locks them to 30 in game and 60 in inventory.

Changing from borderless/full screen/windowed, enabling/disabling VSYNC in game or from drivers does nothing.

I haven't yet tried to completely nuke my settings, but would anyone have any guess what is going on or has encountered this already?

Spoiler, click me

Also Hairworks hair "works".

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

QuoteCan you please explain how you built it? See my questions above.

That's not my video. It's from this reddit thread: https://www.reddit.com/r/linux_gaming/comments/82te09/dxvk_85d28f7_the_witcher_3_wild_hunt_nvidia/

I'll experiment with building later today. The instructions are confusing, but I suspect it needs actual binary wine-vulkan to be installed and available in the path.

In case you don't feel like building dxvk, I just created a new binary release (v0.31 which contains all the tessellation stuff and a bunch of fixes for the game (Lighting now works correctly as well).

In order to build it, you'll need wine in $PATH, but any wine will do (it's only relevant for automated tests, but since there are no automated tests at the moment, it's not used during the build process). wine-vulkan is only required for running anything with dxvk.

As for wine-vulkan, yes, you need to set up the Vulkan SDK. Just follow these instructions and see if you can get cube.exe from the SDK to run.

Quoting: YoRHa-2BIn order to build it, you'll need wine in $PATH, but any wine will do (it's only relevant for automated tests, but since there are no automated tests at the moment, it's not used during the build process). wine-vulkan is only required for running anything with dxvk.

Ah, thanks for clarifying, that makes sense. Since I was building inside a VM, it has only minimally required set of packages, and the build complained that wine wasn't found, and I wasn't sure whether it needs regular or vulkanized Wine :) May be you can update the instructions to differentiate build vs runtime requirements, since currently they say:

QuoteBuild instructions
Requirements:
wine-vulkan for Vulkan support
...

which is misleading.

Quoting: YoRHa-2BAs for wine-vulkan, yes, you need to set up the Vulkan SDK. Just follow these instructions and see if you can get cube.exe from the SDK to run.

Thanks! I'll play around with it later today, and hopefully will build dxvk master to give it a try with TW3.

Meanwhile, Vulkan patches are gradually coming into upstream Wine. Will it also depend on Vulkan SDK somehow? It sounds like somewhat extraneous requirement that shouldn't be really needed.

Quoting: FaattoriSo I uncountered a weird bug / feature while testing the wine-devel 3.3 version. My FPS is locked to 30 except the inventory is locked to 60. No settings seems to unlock either of them. Limiting FPS from the game graphics menu to 30 does limit the inventory FPS to 30, but unlimited still locks them to 30 in game and 60 in inventory.

Locked to 15,20,30,60 etc is fixed by:
swapchain fix

Reported in:
https://bugs.winehq.org/show_bug.cgi?id=44623

I just compiled wine-vulkan and downloaded the DXVK 0.31 and this is how it looks like with RX580. On menu I get fixed 60fps and then this when I try to play

@hilpara try mesa-git, some games don't work well with 17.3.x due to a bunch of RADV bugs that have been fixed in -git. You may also have to set RADV_DEBUG=nohiz.

I did try with RADV_DEBUG=nohiz. No difference. I will try with mesa-git.

..... or maby not. I don't know how to do it on Solus without breaking everything.

Quoting: hilparaI did try with RADV_DEBUG=nohiz. No difference. I will try with mesa-git.

..... or maby not. I don't know how to do it on Solus without breaking everything.

See how it can be done on Debian: https://www.gamingonlinux.com/wiki/Building_Mesa_from_source

Apply same idea to your distro.