Quoting: thk_msBut Wine, Dxvk, PlayonLinux,proton and Lutris; I can't get that together now. Is there a good, coherent tutorial somewhere? Best in writing?

I'm sure the first thing that will be asked by someone that can answer is: Steam or GOG? NVidia or AMD?

Ok, seems that I have 4 to 5 times more performance with Proton 3.7 than 3.16 with steam play. I have nvidia 415.27 driver version.
Does anyone has the same performance drop? That makes the game almost unplayable for Proton 3.16 (can't do combat without crash) and very pleasant in Proton 3.7 (eyes not good enough to see any difference between 50FPS and 100).
Also the savegame are in ~/Documents/The Witcher 3 with Proton 3.16 and in ~/.steam/steam/steamapps/compatdata/[Numbers]/pfx/drive_c/.../The Witcher 3 for Proton 3.7

Do you also see performance drop in regular Wine+dxvk?

Quoting: EhvisI'm sure the first thing that will be asked by someone that can answer is: Steam or GOG? NVidia or AMD?

Hello and good morning,

thank you for answering. I have a Nvidia in my PC. I haven't a steam or GOG account. Yesterday I tried to install W3 with installationdisk by PlayonLinux. The two presquenziell-Videos and the config-part of W3 works. Loading the first gameparts doesn't.
After that I tried to import the game into Lutris but it doesn't work.

Thanks, thk_ms

Quoting: thk_msI haven't a steam or GOG account. Yesterday I tried to install W3 with installationdisk by PlayonLinux.

If you bought TW3 on a disk, it's probably some outdated version. They provide a GOG key in such case, so open GOG account, get TW3 there using the key form the disk, and download that first. Then install it in Wine.

Just tried new Mesa Vulkan HUD layer with TW3 / radv. The font is broken with Mesa master, and also doesn't show framerate. But at least we are getting somewhere with a general purpose Vulkan HUD!

I thought the hud was written for Intels anv Vulkan driver and has to be customized to work with radv.

Quoting: skyrrdI thought the hud was written for Intels anv Vulkan driver and has to be customized to work with radv.

I suppose it needs some work to be usable with radv (as you can see it's not rendering fonts properly), however it's implemented as a Vulkan layer, and therefore can be loaded with any Vulkan driver.

After building Mesa master, it produced libVkLayer_MESA_overlay.so and libVkLayer_MESA_overlay.json. I added this to my hud script, which I already use for GALLIUM_HUD:

export VK_LAYER_PATH=/opt/mesa-master/share/vulkan/explicit_layer.d
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/mesa-master/share/vulkan/explicit_layer.d
export VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay VK_LAYER_MESA_OVERLAY_STATS=submit,draw,pipeline-graphics

It kind of "works" with radv. For older Mesa fonts work better:



I suppose it wasn't tested with radv much, so stats can be focused on anv now.

The HUD is now fixed in Mesa master:



A pity it has no framerate yet though.

By the way, this HUD layer should work with Nvidia blob as well I suppose.