WineHQ

Witcher 3 Wild Hunt

Latest GOG release (1.31 or GOTY)

Application Details:

Version: GOG
License: Retail
URL: http://www.thewitcher.com/
Votes: 15
Latest Rating: Gold
Latest Wine Version Tested: 4.7-staging

Maintainers: About Maintainership

Link GOG.com store page

Test Results

Selected Test Results

What works

Installs without issues. I use the gog-galaxy-wine snap program to download the offline package of this game, and then run the installer on plain wine.

The game starts on vanilla DirectX 11 (OpenGL), but the performance will never be good when switch to the Vulkan based DXVK.

So far, the game runs fines, without great problems

What does not

Using OpenGL default translation (WineD3D) it will occur some graphic glitches, and lack of post-processing effects.

Workarounds

Installing the last branch of DXVK fix some graphic issues, and implements some advanced graphics settings (NVidia post-processing effects)

What was not tested

Not so much.

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

Tested on a Clevo Laptop with a 7th Generation Intel Core i7 that contains an integrated Intel HD 630 GPU, and a discrete Nvidia 1050 TI, like on previous test.

The reason for a new report has the launch of a stable version of primus_vk that finally fix the lack of Vulkan support on hybrid GPUs.

On NVidia Optimus laptops install primus_vk from https://github.com/felixdoerre... , once installed bumblebee and the NVidia drivers from your official distro repository.
It is also recommendable to copy the pvkrun script (now bundled on primus_vk 1.0 stable) to /usr/bin and mark as executable. This will set the primus_vk variables to primusrun command automatically, making more simple to start Vulkan based games on NVidia cards:
$ pvkrun wine witcher3.exe


The same command can be used on Steam client, like:

pvkrun %command%

Playing on integrated graphics (Intel HD) will be a nightmare.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentDebian GNU/Linux 9.x "Stretch" x86_64May 10 20194.7-stagingYes Yes YesGoldNosferatu Arucard 
ShowArch Linux x86_64Apr 13 20194.1-stagingYes Yes YesSilverabcdefg 
ShowDebian GNU/Linux 9.x "Stretch" x86_64Jan 07 20194.0-rc4-stagingYes Yes YesGoldNosferatu Arucard 
ShowUbuntu 18.10 "Cosmic" amd64 (+variants like Kubuntu)Nov 05 20183.19-stagingYes Yes NoBronzemstfa 
ShowArch Linux x86_64Jun 23 20183.10-stagingYes Yes NoSilverMehmet Akif TASOVA 

Known Bugs

Bug # Description Status Resolution Other apps affected
43133 The Witcher 3: ambient occlusion distortions NEW View
43786 The Witcher 3: textures flicker in some places when you move (derivatives after discard) NEW View
43816 The Witcher 3: white outline on vegetation during rain at nighttime UNCONFIRMED View
43861 The Witcher 3: Movement problems UNCONFIRMED View
44315 Buffer maps cause CPU-GPU synchronization (Guild Wars 2, The Witcher 3) NEW View
45989 The Witcher 3 flickers horribly and has artifacts UNCONFIRMED View

Show all bugs

HowTo / Notes

Maximizing performance

Currently with wined3d, The Witcher 3 is still affected by CPU-GPU buffer maps synchronization issue (bug #44315). It severely degrades performance.

Using dxvk instead of wined3d is the best course of action, since it performs very well, and also provides perfect rendering, as long as your Vulkan driver supports VK_EXT_transform_feedback extension.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Graphical glitches with SSAO
by Christian Widmer on Wednesday July 25th 2018, 17:18
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-
RE: Graphical glitches with SSAO
by Shmerl on Wednesday July 25th 2018, 17:50

by Storm Engineer on Tuesday June 12th 2018, 10:18
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!
RE:
by Storm Engineer on Tuesday June 12th 2018, 10:19
Wrong button, clicked Comment instead of Reply...
Game jsut won't run
by Storm Engineer on Thursday April 19th 2018, 18:17
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.
RE: Game jsut won't run
by Shmerl on Thursday April 19th 2018, 19:31
You should be starting the game from the directory where the binary (witcher3.exe) is located. It won't work otherwise.
RE: Game jsut won't run
by Storm Engineer on Monday May 7th 2018, 12:59
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)?
RE: Game jsut won't run
by Kai Krakow on Tuesday May 15th 2018, 17:46
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.
RE: Game jsut won't run
by Kai Krakow on Tuesday May 15th 2018, 17:50
BTW: Please try running with "WINEDEBUG=-all" as generating all those fixme messages (even when hidden) hurts performance a lot.
RE: Game jsut won't run
by Storm Engineer on Tuesday June 12th 2018, 10:19
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!
RE: Game jsut won't run
by Storm Engineer on Tuesday June 12th 2018, 10:11
I'm using Staging. Are your patches cherry-picked from Staging too? If so, shouldn't using staging have the same result?
RE: Game jsut won't run
by Storm Engineer on Monday May 7th 2018, 13:16
Well darn, set all graphics and post-processing to Low, gained maybe 1-2 FPS so still unplayable. :(

I have GeForce GTX 750 Ti.
Patches?????????????
by Storm Engineer on Saturday April 14th 2018, 8:20
HOWTO says I need to build wine with limited patches... bot _WHAT_ patches? Because it doesn't say that...
RE: Patches?????????????
by Shmerl on Saturday April 14th 2018, 22:47
Because there are none needed at present. I can remove that from the howto, it's reflecting the situation from the past.
RE: Patches?????????????
by Storm Engineer on Thursday April 19th 2018, 18:19
Thanks!

I got confused thinking I'm missing something. :)
Gamepad
by jontis on Sunday September 17th 2017, 18:22
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
RE: Gamepad
by Shmerl on Sunday September 17th 2017, 18:25
I can make into a howto if you think it's useful, though I don't have a controller to test it.
RE: Gamepad
by jontis on Monday September 18th 2017, 17:36
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!
Next set of performance issues will probably be addressed when
by mazzy on Tuesday September 12th 2017, 14:54
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.
RE: Next set of performance issues will probably be addressed when
by Shmerl on Tuesday September 12th 2017, 15:34
Mesa freeze bug is very game breaking though, so I consider it unplayable with Mesa, at least in Velen.
RE: Next set of performance issues will probably be addressed when
by Nick Stefanov on Tuesday September 12th 2017, 17:26
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.
RE: Next set of performance issues will probably be addressed when
by mazzy on Wednesday September 13th 2017, 18:59
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
RE: Next set of performance issues will probably be addressed when
by Nick Stefanov on Thursday September 14th 2017, 3:56
I can achieve 60FPS only in inventory window.
RE: Next set of performance issues will probably be addressed when
by mazzy on Thursday September 21st 2017, 15:51
What are you using to track your FPS? Also what resolution?
Fix for dark textures coming?
by mazzy on Friday September 1st 2017, 15:12
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)
RE: Fix for dark textures coming?
by mazzy on Friday September 1st 2017, 15:51
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.
RE: Fix for dark textures coming?
by Shmerl on Friday September 1st 2017, 15:58
What cutscene issue?
RE: Fix for dark textures coming?
by mazzy on Friday September 1st 2017, 17:41
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.
RE: Fix for dark textures coming?
by Shmerl on Saturday September 2nd 2017, 21:09
I see. I never had this issue with Mesa though.
RE: Fix for dark textures coming?
by mazzy on Tuesday September 5th 2017, 14:30
No I think it was an issue with the blob driver only... Was occurring in several games though
RE: Fix for dark textures coming?
by Nick Stefanov on Thursday September 21st 2017, 18:17
For FPS I use glxosd. I play at 1920@1080 but in lower resolutions there isn't any benefit.
MaxVersionGL registry setting breaks other games
by Gabriel Doru on Sunday July 23rd 2017, 18:57
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
RE: MaxVersionGL registry setting breaks other games
by Shmerl on Sunday July 23rd 2017, 19:45
It is needed, unless you are using Wine staging, which includes a patch that makes it not required anymore.
RE: MaxVersionGL registry setting breaks other games
by Gabriel Doru on Monday July 24th 2017, 3:19
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!
RE: MaxVersionGL registry setting breaks other games
by Shmerl on Sunday July 23rd 2017, 19:46
I recommend installing each game in its own Wine prefix, which this very issue illustrates. It makes managing them separately easier.
Game does not start at all there
by gojul on Saturday July 8th 2017, 1:18
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 ?
RE: Game does not start at all there
by gojul on Saturday July 8th 2017, 1:58
Forgot to say, here's my system :

Intel Core i7 4790
32 GB RAM
NVidia GeForce 1070 w/ 375.66 driver
RE: Game does not start at all there
by Shmerl on Saturday July 8th 2017, 23:17
Not sure, that looks like some new issue to me. May be it's some regression in Nvidia driver?
RE: Game does not start at all there
by Shmerl on Saturday July 8th 2017, 23:18
Try to disable CSMT. I noticed that staging CSMT is crashing quite a number of games lately.
RE: Game does not start at all there
by gojul on Sunday July 9th 2017, 6:01
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.
RE: Game does not start at all there
by mazzy on Wednesday July 12th 2017, 14:03
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
RE: Game does not start at all there
by Igor Zinovyev on Thursday July 20th 2017, 15:26
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
RE: Game does not start at all there
by Shmerl on Thursday July 20th 2017, 15:31
Try adding this staging patch: wined3d-Copy_Resource_Typeless
RE: Game does not start at all there
by Shmerl on Thursday July 20th 2017, 15:32
Also, try doing it with Wine master.
RE: Game does not start at all there
by Igor Zinovyev on Thursday July 20th 2017, 16:43
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!
RE: Game does not start at all there
by Shmerl on Thursday July 20th 2017, 16:52
Yes, that's usually the case. I put it all in a script.
RE: Game does not start at all there
by Dmitry on Saturday August 26th 2017, 14:47
it didn't start for me, until i cd to /bin/x64/ folder
Looking good on 2.11
by mazzy on Tuesday June 27th 2017, 19:31
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
RE: Looking good on 2.11
by Shmerl on Tuesday June 27th 2017, 19:48
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.
RE: Looking good on 2.11
by mazzy on Wednesday June 28th 2017, 0:04
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
RE: Looking good on 2.11
by Shmerl on Tuesday June 27th 2017, 20:36
Can you please also test this save: bugs.winehq.org/attachment.cgi?id=58570

And check whether ground there looks very dark?
RE: Looking good on 2.11
by mazzy on Wednesday June 28th 2017, 15:58
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
RE: Looking good on 2.11
by Shmerl on Wednesday June 28th 2017, 19:47
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.
RE: Looking good on 2.11
by Philipp on Sunday July 2nd 2017, 18:15
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.
RE: Looking good on 2.11
by Shmerl on Sunday July 2nd 2017, 18:17
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.
RE: Looking good on 2.11
by Philipp on Monday July 3rd 2017, 1:04
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?
RE: Looking good on 2.11
by Philipp on Monday July 3rd 2017, 1:05
Oh, sry, the download is password protected: witcher
Will be available for one month.
RE: Looking good on 2.11
by Shmerl on Monday July 3rd 2017, 1:14
Better open a bug here: bugs.winehq.org/enter_bug.cgi?product=Wine

And add that save as attachment.
RE: Looking good on 2.11
by Philipp on Monday July 3rd 2017, 11:19
Reported. Let's hope someone can reproduce and figure out what's wrong.
RE: Looking good on 2.11
by Shmerl on Monday July 3rd 2017, 11:21
Thanks!
About CSMT and staging
by Shmerl on Thursday June 15th 2017, 11:12
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).
RE: About CSMT and staging
by Shmerl on Thursday June 15th 2017, 11:14
I.e. phrase "Same, but using staging wine with CSMT enabled" is somewhat misleading when referring to that registry setting.
RE: About CSMT and staging
by Shmerl on Thursday June 15th 2017, 11:17
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.
RE: About CSMT and staging
by Filip Frackiewicz on Wednesday June 28th 2017, 6:43
Please note that you can turn CSMT off and on with winetricks these days so you don't need to go registry diving :)
Separating registry setting into separate howto
by Shmerl on Wednesday June 14th 2017, 20:22
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!
RE: Separating registry setting into separate howto
by Shmerl on Wednesday June 14th 2017, 20:23
Alternatively, you can just remove the first howto, and rely on the one for custom built Wine as is.
Please add this howto
by Shmerl on Tuesday June 13th 2017, 20:55
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
Please update the the registry settings howto
by Shmerl on Tuesday June 13th 2017, 20:50
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
Please add this as a howto
by Shmerl on Tuesday June 13th 2017, 20:43
Please remove resolved associated bugs
by Shmerl on Sunday June 11th 2017, 20:13
I.e. duplicates.
RE: Please remove resolved associated bugs
by Igor Zinovyev on Monday June 12th 2017, 2:54
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.
Low framerate
by Shmerl on Thursday March 23rd 2017, 21:28
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).
RE: Low framerate
by Shmerl on Thursday March 23rd 2017, 21:32
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.
Small fix for the registry HOWTO
by Shmerl on Friday February 10th 2017, 12:19
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
RE: Small fix for the registry HOWTO
by Igor Zinovyev on Friday February 10th 2017, 12:26
Is that for winetricks? How do you add that to the registry?
RE: Small fix for the registry HOWTO
by Shmerl on Friday February 10th 2017, 12:33
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).
RE: Small fix for the registry HOWTO
by Shmerl on Friday February 10th 2017, 12:35
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
Another bug
by Shmerl on Thursday February 9th 2017, 23:34
Another bug
by Shmerl on Tuesday January 31st 2017, 13:26
Affecting bug
by Shmerl on Monday January 23rd 2017, 23:22
Please add this bug to the list: bugs.winehq.org/show_bug.cgi?id=42292
Bug link
by Shmerl on Monday January 16th 2017, 22:54
Please also add link to bug bugs.winehq.org/show_bug.cgi?id=39180
HOWTO for OpenGL 4.5 usage
by Shmerl on Monday January 16th 2017, 22:44
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.
RE: HOWTO for OpenGL 4.5 usage
by Igor Zinovyev on Tuesday January 17th 2017, 1:39
For some reason I can't add a HOWTO either.
RE: HOWTO for OpenGL 4.5 usage
by Shmerl on Monday January 23rd 2017, 23:23
May be some Wine admins can help? I had no issues with howto's in other games.
Back