Witcher 3 Wild Hunt

With Wine (staging) 5.8 and dxvk 1.7 on an AMD GPU, performance is excellent, no visual glitches I could see. Performance without dxvk was unplayable.

Running the with every post-processing effects diabled, everything set to lower as possible, it's still very laggy.
I'm using dxvk-1.5.5 with wine-staging-5.5 and wine-vanilla-5.5 with same low performances.
Hardware : GPU : nvidia GT 630 (not the newest graphic card...)
CPU : AMD FX 8320
Now it depends of what you call "playable"... It's very very laggy...

I have weird graphical glitches when playing the game with SSAO. For example, the video linked in [1] (while I am using dxvk in the linked video, the issue is also present when using wined3d) shows small black shadowy things flashing on the tub. They also appear in other places, like on clothes, mostly during scripted scenes. Interestingly, they do not appear when I switch to HBAO+. Does anyone else also experience this and might have an idea if this is rather an issue in the game, a driver bug or something else?

I am using an RX 580 with mesa git on commit c3eaf8fe5746e5b29a46a076247ba072c84e2ec5, kernel 4.17.9 with the Gentoo patchset and vanilla wine on version 3.13.

[1] drive.google.com/open?id=1j9SMSaWLyVJnNj6INiO_ncxO-DlXqIR-

Likely related to bugs.winehq.org/show_bug.cgi?id=43133

I tried that, with current Staging and the performance have increased indeed, but still not enough to be playable. I'm going to try your custom patches next. Thanks for your help!

Wrong button, clicked Comment instead of Reply...

Sadly the game just won't run for no good reason.

The first time it did and worked, then second time it didn't, but running winecfg and closing it fixed it - then this repeated a few times, then it stopped running ever. I tried re-installing it, didn't help. Tried both normal wine and staging, didn't help.

Console output with Staging:
$ WINEPREFIX=/home/storm/misc/wine-prefixes/witcher3/ wine /home/storm/misc/wine-prefixes/witcher3/drive_c/GOG\ Games/The\ Witcher\ 3\ Wild\ Hunt\ GOTY/bin/x64/witcher3.exe
000b:fixme:winediag:start_process Wine Staging 3.6 is a testing version containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
002e:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0.
002e:fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
002e:fixme:dxgi:dxgi_device_init Ignoring adapter type.
002f:fixme:ver:GetCurrentPackageId (0x17fcfdc0 (nil)): stub
002e:fixme:msvcrt:__clean_type_info_names_internal (0x2431878) stub
002e:fixme:msvcrt:__clean_type_info_names_internal (0x2345768) stub

And with normal Wine:
$ WINEPREFIX=/home/storm/misc/wine-prefixes/witcher3/ wine /home/storm/misc/wine-prefixes/witcher3/drive_c/GOG\ Games/The\ Witcher\ 3\ Wild\ Hunt\ GOTY/bin/x64/witcher3.exe
002b:fixme:kerberos:kerberos_SpInstanceInit 65536,0x7f33c246c7a0,(nil): stub
002b:fixme:dwmapi:DwmIsCompositionEnabled 0x6dbd1518
0030:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ebd3de, context 0xaf6520, init_notify 0, handle 0x13efa10): stub
0046:fixme:dwmapi:DwmIsCompositionEnabled 0x6d5d3018
0048:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0cb608, context 0x958860, init_notify 0, handle 0x119fc88): stub
wine: configuration in '/home/storm/misc/wine-prefixes/witcher3' has been updated.
005d:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0.
005d:fixme:win:EnumDisplayDevicesW ((null),0,0x213f180,0x00000000), stub!
005d:fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
005d:fixme:dxgi:dxgi_device_init Ignoring adapter type.
005e:fixme:ver:GetCurrentPackageId (0x180dfdc0 (nil)): stub
005d:fixme:msvcrt:__clean_type_info_names_internal (0x2431878) stub
005d:fixme:msvcrt:__clean_type_info_names_internal (0x2345768) stub

Arch Linux 64 bit and 64 bit prefix.

Not sure if it's me doing something wrong, or it's a bug and I should make a ticket.

P.s.: I mentioned this to Shmerl already, but could not help so I'm writing here now, maybe someone else can give a tip.

You should be starting the game from the directory where the binary (witcher3.exe) is located. It won't work otherwise.

My apologies for the late reply, I missed the email. Indeed, that solved it, thank you! Never ran into this before...

Now only if I could improve FPS futher. With the same settings I got 50-60 FPS under the dual booted Win 10, and 5 FPS under Wine. I added the CSMT registry entries. Threaded optimization enabled/disabled makes no noticeable difference whatsoever (nVidia proprietary).

Is there anything else I can try (apart from lowering settings, of course)?

I'm not getting too bad results with some additional patches to wine-vanilla. While I don't have a dual-boot setup to compare results, I usually have pretty decent fps, fluctuating between maybe 20 (especially in the Blood & Wine DLC areas) to something which looks perfectly smooth (so maybe up to 60 fps). Using GTX 1050 Ti, 1080p, high-settings, nvidia proprietary. NVIDIA HairWorks works with my patches, tho with graphical glitches (hair is rendered as a layer above everything else but performance seems good). If you used staging patches in the same wine prefix before, take care of removing the csmt dll redirections from the registry. I'm using Gentoo, so wine is compiled with CPU optimizations here (by setting appropriate useflags).

You can check out my patches here:
github.com/kakra/wine/tree/patches-3.7/wined3d

I didn't rebase to 3.8 yet. There's another branch with performance patches cherry-picked from staging. Follow the instructions in the header descriptions to export patch files from the git clone which you could apply to your source package.

BTW: Please try running with "WINEDEBUG=-all" as generating all those fixme messages (even when hidden) hurts performance a lot.

I tried that, with current Staging and the performance have increased indeed, but still not enough to be playable. I'm going to try your custom patches next. Thanks for your help!

I'm using Staging. Are your patches cherry-picked from Staging too? If so, shouldn't using staging have the same result?

Well darn, set all graphics and post-processing to Low, gained maybe 1-2 FPS so still unplayable. :(

I have GeForce GTX 750 Ti.

HOWTO says I need to build wine with limited patches... bot _WHAT_ patches? Because it doesn't say that...

Because there are none needed at present. I can remove that from the howto, it's reflecting the situation from the past.

Thanks!

I got confused thinking I'm missing something. :)

I just got an xbox one controller and that required some fixes to work in the game.

What took me the longest to figure out was that two xinput dlls needed to be present in the game folder.
xinput1_3.dll was already there but xinput9_1_0.dll was not.
I got them from this repo:
github.com/kozec/dumbxinputemu

I can make into a howto if you think it's useful, though I don't have a controller to test it.

Howto for Gamepad in linux with wine.

I put two days into finding out how to make my gamepad controller work in linux with wine.
Here is my findings with what I mostly lacked in the other instructions, testing of each step to make sure it works so far.

This was done with linux mint 18.2 and wine 2.16 with an xbox one s controller. usb-id: 045e:02ea

1. Connect the controller with USB. If you can cable in, do this first to test. Just make sure that it really can communicate through the cable and not just charge.

Test:
$ lsusb

should reply with something like:
Bus X Device X: ID xxxx:xxxx
where xxxx:xxxx is your identifiying numbers for the gamepad.

A reasonably modern linux already have the xpad driver in the kernel. I use this. Others mention that they prefer xboxdrv or some drv from steam.
To test that linux picks up what the gamepad sends, install and use either of antimicro, jstest-gtk or sdl-test. Google for repos.
They give a simple representation of keypresses as the gamepad sends them.
I used antimicro:
github.com/AntiMicro/antimicro

2. Connect bluetooth. This seemed straightforward. Away with the cable and in with a bluetooth receiver in the USB port. Open Preferences / Bluetooth or do it the hard way in command prompt, push the controllers pair button and pair. Worked fine, except that it looses connection seconds after pairing. Every time. Some more googling digs up this bug:
github.com/paroj/xpad/issues/53
A parameter needs to be set and the control re-paired for the connection to hold.

Apparently, the controller exposes another api when connected by bluetooth, and for my particular controller, this is buggy.
The controller mapping in my case is wrong.
Test again with something like antimicro. The solution for now is rather hacky, and yes, I program for a living, but I will still stay with cable until this bug is sorted.
Hope you are in luck with your controller.

3. Make the controller work in wine.
Start wine's, control panel to test the gamepad.
$ wine control
if you run the game in a special wineprefix, you add that like:
$ WINEPREFIX=~.wine/... wine control

This brings up a graphical interface wher you can select "game controllers" and test the controller.
Great job, wine now picks up signals from the controller.

4. Make the controller work in your game.
This puzzled me a lot.
A few more hours of googling, some controllers don't communicate the way that the game is expected. Translation is nescessary.
People seem to prefer x360ce, which I was able to install for wine32.
github.com/x360ce/x360ce
Sadly, I use wine64 for Witcher3 and I was not able to install x360ce there, maybe because I failed to install dotnet45. They're working on it...
What I did get to work on wine64 was this:
github.com/kozec/dumbxinputemu
Drop both xinput1_3.dll and xinput9_1_0.dll into the same folder as the exe and the game receives the controller signals.

As my controller still suffers from the BT bug, I'm on cable but everything works fine there.

Good luck!

ID3D11DeviceContext::GenerateMips (msdn.microsoft.com/en-us/library/windows/desktop/ff476426(v=vs.85).aspx) is implemented... mipmaps help with LOD/performance/realism of a scene (see en.wikipedia.org/wiki/Mipmap) I would say any remaining disparity with performance on latest wine staging 2.16 is due to this not being implemented still

Until then the game remains perfectly playable on a GTX1060 3GB / AMD Ryzen 1700X / 32GB DDR4 but even still the FPS is still pretty low for this hardware.

Mesa freeze bug is very game breaking though, so I consider it unplayable with Mesa, at least in Velen.

I play the game now with GTX 1080 Ti, Intel 3770, 16GB DDR3 and proprietary driver, but performance is really slow, around 15-30 FPS, constantly changing. Yes, it's playable but it's slow.

Its strange, sometimes I'll get 60FPS and other times after playing for a while it will drop considerably... I noticed rain kills performance pretty bad so I usually just console command clear weather

I can achieve 60FPS only in inventory window.

What are you using to track your FPS? Also what resolution?

I see this patch coming through the pipe on staging:

dev.wine-staging.com/patches/181/

Which fixes a similar sounding bug in Crysis... Hopeful this will make the game finally 100% playable! (Been waiting for this to be fixed to have the best experience)

I can confirm that this has fixed the cutscene issue! The game runs flawlessly for me now on nvidia blob.

I'm sure several other issues will be fixed b/c of this.

What cutscene issue?

bugs.winehq.org/show_bug.cgi?id=43264

Basically when initiating a cutscene the textures would pop in all black... I believe this is because witcher 3 uses higher res textures during cutscenes. So when they are swapped using d3d11_deferred_context_CopySubresourceRegion which was unimplemented it failed. I dont know much about DX but thats just my theory.

I see. I never had this issue with Mesa though.

No I think it was an issue with the blob driver only... Was occurring in several games though

For FPS I use glxosd. I play at 1920@1080 but in lower resolutions there isn't any benefit.

Hi,

It appears that, at least on my system, the MaxVersionGL registry setting is breaking Red Alert 3. On the other hand, Witcher 3 (gog version) seems to be working fine without it. Is this registry setting really needed?

Thanks,
Doru

It is needed, unless you are using Wine staging, which includes a patch that makes it not required anymore.

This explains why the game works without setting MaxVersionGL. I'm using wine-staging on arch linux, one wine configuration for all my apps.

Thanks!

I recommend installing each game in its own Wine prefix, which this very issue illustrates. It makes managing them separately easier.

Hi,

Using Debian Stretch amd64 + wine staging 2.11 (official build) game does not start at all there.

Applied the registry for OpenGL 4.5 and when starting the game I got the following stack :
winedbg /mnt/misc3/wine/GOG\ Games/The\ Witcher\ 3\ Wild\ Hunt/bin/x64/witcher3.exe

Wine-dbg>run
fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll"
err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 4.5.
fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
fixme:dxgi:dxgi_device_init Ignoring adapter type.
fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x8f9d0, container_parent 0xdca50, wined3d_desc 0x213ed20, texture flags 0, wined3d_texture 0xdcae0 partial stub!
fixme:d3d11:device_parent_create_swapchain_texture Implement DXGIwined3d usage conversion.
fixme:ver:GetCurrentPackageId (0x2a9e580 (nil)): stub
fixme:msvcrt:__clean_type_info_names_internal (0x2431878) stub
fixme:msvcrt:__clean_type_info_names_internal (0x2345768) stub
Process of pid=00c8 has terminated

Exception c0000005

GOG version used.

Any idea ?

Forgot to say, here's my system :

Intel Core i7 4790
32 GB RAM
NVidia GeForce 1070 w/ 375.66 driver

Not sure, that looks like some new issue to me. May be it's some regression in Nvidia driver?

Try to disable CSMT. I noticed that staging CSMT is crashing quite a number of games lately.

Hi,

No, it's not a CSMT issue as enabling or disabling it does not have any effect.

If I switch to wine-devel at least I have an error popup, which I do not have with wine-staging.

I have this problem as well on the wine staging 2.12 with NVIDIA blob.

I've attached debug output for someone who knows what they're doing to take a look...Sorry I did debug all I wasn't sure what the best flags to use are. I can use different flags if anyone wants to see different output.

ufile.io/gp3kt

I get the same thing when trying to run on wine 2.12 without any staging patches, just the four patches specified in the HOWTO. This is what I get in the console:

err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:dwmapi:DwmIsCompositionEnabled 0x6dbd1518
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ebd3de, context 0x8b64e0, init_notify 0, handle 0x119e1d0): stub
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:dwmapi:DwmIsCompositionEnabled 0x6d5d3018
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0cb608, context 0x938730, init_notify 0, handle 0x116e7a4): stub
wine: configuration in '/home/zinigor/wine/w3' has been updated.
err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 4.5.
fixme:win:EnumDisplayDevicesW ((null),0,0x212f100,0x00000000), stub!
fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
fixme:dxgi:dxgi_device_init Ignoring adapter type.
fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x8e4a0, container_parent 0x9e5b0, wined3d_desc 0x212ed20, texture flags 0, wined3d_texture 0x9e640 partial stub!
fixme:d3d11:device_parent_create_swapchain_texture Implement DXGIwined3d usage conversion.
fixme:ver:GetCurrentPackageId (0x2b9e580 (nil)): stub
fixme:msvcrt:__clean_type_info_names_internal (0x2421878) stub
fixme:msvcrt:__clean_type_info_names_internal (0x2335768) stub

Try adding this staging patch: wined3d-Copy_Resource_Typeless

Also, try doing it with Wine master.

I managed to get it working. For me it turned out that I needed to first change to the location of the executable, so I could run it without the path, just WINEPREFIX=/path/to/prefix/ wine witcher3.exe. And voila!

Yes, that's usually the case. I put it all in a script.

it didn't start for me, until i cd to /bin/x64/ folder

I have TW3 running in 2.11 staging and everything is looking really good, but whenever a cutscene plays or there is a transition all the textures turn metallic almost like the bad guy in terminator 2... Some characters also turn black. I've tried with and without CSMT but no dice. Running NVIDIA blob drivers with a GTX 960 2GB, standard 2.11-staging. I see these FIXME around the time the problems crop up:

fixme:d3d11:d3d11_deferred_context_CopySubresourceRegion iface 0x7f1e5f948310, dst_resource 0x7f1e275957a0, dst_subresource_idx 6, dst_x 0, dst_y 0, dst_z 0, src_resource 0x7f1e26c17aa0, src_subresource_idx 5, src_box (nil) stub!

Not sure if those are relevant or not, but something to do with deferred rendering would make sense to me? Shot in the dark though

Interesting. Can you try it with just a few patches from staging that are needed for the game, instead of all of them? Some other staging patches can cause regressions sometimes. I'll give it a try with Mesa soon, but would be good to see how it works with Nvidia blob too.

Yeah I'll give that a shot, I did actually get it to run without staging I had really low fps but everything was rendered correctly, so something is causing a problem

Can you please also test this save: bugs.winehq.org/attachment.cgi?id=58570

And check whether ground there looks very dark?

Turns out nothing loads on 2.11 patched for me... Only starts a few frames then locks up so no dice on your save :( so close though. BTW here is a pic of the glitch: imgur.com/a/ahzla

Yeah, something looks weird. Feel free to pop into this thread: www.gamingonlinux.com/forum/topic/2753
It's going to be easier to discuss it there.

Wine-staging 2.11 works pretty well for me too. I've encountered a bunch of bugs, you can see most in these videos:
www.youtube.com/watch?v=cCtfSXbwovk
www.youtube.com/watch?v=Rsx4CidYMHk

But now, in Velen, I hit a major problem: The game freezes, the entire machine locks up. No such issue in White Orchard.
The bug triggers reliably when I run around in this area: witcher3map.com/v/#5/137.734/110.047
Can't post a save game here, but I'll upload one somewhere if someone wants to reproduce.

I encountered that freeze too in the area where you start in Velen. Can you please open a bug about it? When I load a checkpoint save around that place, the freeze doesn't happen.

Here's a link to the save file. Just turn left and run up to the cart. This locks up my machine every time. freeshell.de/owncloud/index.php/s/JBk7bUssFkkpWLO
Maybe someone with Nvidia graphics can try?

Oh, sry, the download is password protected: witcher
Will be available for one month.

Better open a bug here: bugs.winehq.org/enter_bug.cgi?product=Wine

And add that save as attachment.

Reported. Let's hope someone can reproduce and figure out what's wrong.

Thanks!

Actually, setting CSMT is registry is needed for regular, non staging Wine. See here: wiki.winehq.org/Useful_Registry_Keys

That's becasue initial CSMT support already landed in mainline WIne.

Staging on the other hand isn't using that registry setting, but has a special dll override for direct3d when csmt is enabled. Though it doesn't hurt to set that key anyway, especially if you want to switch between staging / non staging for your tests.

I set it for TW3 because I'm not using full blown staging, but mostly regular Wine with a few patches (which don't include staging way of dll override for CSMT).

I.e. phrase "Same, but using staging wine with CSMT enabled" is somewhat misleading when referring to that registry setting.

I'd rephrase this too:

> Make sure to use the wine staging with CSMT registry settings snippet from the HOWTO on this page.

Should probably say:

> Make sure to enable CSMT with registry settings snippet from the HOWTO on this page.

Please note that you can turn CSMT off and on with winetricks these days so you don't need to go registry diving :)

I think it's better to separate them, for more clarity, and reference the registry one from custom built one howto. There is one for registry setting already above. Just update it as needed, and remove that part from the custom wine (except for the reference to it) and it all will look neater. Thanks!

Alternatively, you can just remove the first howto, and rely on the one for custom built Wine as is.

To work around bug #42414 (intro videos don't play) install xact_jun2010 (with winetricks for example). See bugs.winehq.org/show_bug.cgi?id=42414

You need to set these settings in registry, to enable OpenGL 4.5 usage for DirectX 11 and CSMT for better performance and avoiding various corruptions.
Either set it manually in regedit, or save below snippet like witcher3_fix.reg and import it with your Wine regedit:

REGEDIT4
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"csmt"=dword:1
"DirectDrawRenderer"="opengl"
"UseGLSL"="enabled"
"MaxVersionGL"=dword:00040005

To run the game, you need to build Wine from source, applying a couple of patches from Wine staging and extra GLSL related hack patch:

* virtual heap size fix: raw.githubusercontent.com/wine-compholio/wine-staging/master/patches/ntdll-Grow_Virtual_Heap/0001-ntdll-Remove-memory-limitation-to-32GB-on-64-bit-by-.patch
* buffers pool fix: raw.githubusercontent.com/wine-compholio/wine-staging/master/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch
* sample_c_lz hack: bugs.winehq.org/attachment.cgi?id=58404&action=diff&context=patch&collapsed=&headers=1&format=raw

I.e. duplicates.

Done, thanks for working on this!
By the way, can you please post a new test result? I believe you're using something newer than wine-staging 2.4? I can't seem to run anything with wine-staging 2.9.

To avoid having low framerate, make sure you have buffer pool patch from Wine staging, and you don't have colliding CSMT and threaded dispatch (with Nvidia blob you'd probably need to set: " __GL_THREADED_OPTIMIZATIONS=0. In Mesa threaded dispatch is off by default).

The GPU though (Nvidia GeForce GT 520M) sounds pretty weak for the game, so low framerate can be simply caused by that. Official Nvidia minimum requirement if GTX 660.

Please update the registry entry, it fails to import it without a REGEDIT4 header. This one works:
_________________________________________________________


REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"DirectDrawRenderer"="opengl"
"UseGLSL"="enabled"
"MaxVersionGL"=dword:00040005

Is that for winetricks? How do you add that to the registry?

No. You can add those entries manually, but an easier way to do it, is to create a small file, for example glversion_fix.reg with the content that such HOWTO lists, i.e.:


REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"DirectDrawRenderer"="opengl"
"UseGLSL"="enabled"
"MaxVersionGL"=dword:00040005

Then, call regedit from your Wine installation, and do: Registry > Import Registry File. Find that file, in the dialog, and press "Open".

Alternatively, you can do it from the terminal like this:

wine regedit /C \glversion_fix.reg

(Use whatever prefix and other env variables you need to point to your proper Wine and installation prefix).

Sorry, part of the comment was swallowed by syntax filter. I meant something like this:

wine regedit /C some_path_to_the_file\glversion_fix.reg

Please add this one: bugs.winehq.org/show_bug.cgi?id=42347

Please add this bug to the list: bugs.winehq.org/show_bug.cgi?id=42292

Please also add link to bug bugs.winehq.org/show_bug.cgi?id=39180

I can't add a HOWTO to this version. Please add the registry setting to HOWTO note, in order to avoid posting it in each test submission.

For some reason I can't add a HOWTO either.

May be some Wine admins can help? I had no issues with howto's in other games.

appdb.winehq.org/objectManager.php?sClass=version&iId=34256
appdb.winehq.org/objectManager.php?sClass=version&iId=32185
appdb.winehq.org/objectManager.php?sClass=version&iId=34698