WineHQ
Category: Main Games Role Playing Games Witcher 3 Wild Hunt 1.01

Witcher 3 Wild Hunt

No Screenshot

Submit Screenshot
Good Old Games version.

Application Details:

Version: 1.01
License: Retail
URL: http://www.thewitcher.com/
Votes: Marked as obsolete
Latest Rating: Garbage
Latest Wine Version Tested: 1.7.46

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Installer, up until the vcredist_x64.exe installation section.

What does not

When running the Witcher 3 Good Old Games installer under Ubuntu 15.04, the installer crashes when attempting to install vcredist_x64.exe with a "Runtime Error (at 69:445)" message.

Witcher 3 from Good Old Games does not launch due to VCOMP110.DLL not being found. After cabextracting the DLL manually from the vcredist_x64.exe file and installing it into wine's system32 folder, a new C++ error occurs when attempting to launch the game.

Workarounds

What was not tested

Gameplay since game does not launch.

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

https://bugs.winehq.org/show_bug.cgi?id=38613

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?		RatingSubmitter
ShowFedora 21 x86_64Jul 18 20151.7.46Yes No NoGarbagejazz 
CurrentUbuntu 15.04 "Vivid" amd64 (+ variants like Kubuntu)May 23 20151.7.38Yes No NoGarbagean anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected
35092 Multiple 64-bit applications need __CxxFrameHandler implementation (Ableton Live 9.1, Adobe Cloud apps) CLOSED FIXED View
38613 Multiple games (Witcher3 Wild Hunt, Schein, The Emptiness) need vcomp110.dll CLOSED FIXED View
39180 Witcher 3 Wild hunt Wine 1.7.50 not working CLOSED FIXED View
39885 Cannot allocate more than 32gb of memory CLOSED FIXED View

Show open bugs

Comments

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

Removing old version
by Shmerl on Thursday March 9th 2017, 18:22
Steam version is really the same 1.31, so it's not very consistent to call one entry "Steam", and other 1.31.

Leave only 2 version entries, and call them "Steam", and "GOG" (the later is one currently called 1.31). That would make it more consistently focused on specifics that affect them (GOG installer, Steam client and so on).
Comment Reply
RE: Removing old version
by Igor Zinovyev on Friday March 10th 2017, 5:16
I see what you mean. The thing that's stopping me is that GOG and Steam are technically not versions, they are distribution platforms. So you could call that "version", I guess. And I think that it may be more logical to just keep the latest version as current one and merge Steam into it. I'm pretty sure that the devs try to make them more or less the same minus the distribution platform details. We can have a separate HOWTO section for both GOG and Steam if needed.
Comment Reply
RE: Removing old version
by Shmerl on Friday March 10th 2017, 9:41
The problem is, they aren't necessarily the same, and as I said, there are specifics which makes sense to highlight, such as GOG installer, Steam client itself and etc. They can make a significant difference between versions.

Look how versions are organized here for example:

* appdb.winehq.org/objectManager.php?sClass=application&iId=6019
* appdb.winehq.org/objectManager.php?sClass=application&iId=3368

That's what I meant above.
Comment Reply
RE: Removing old version
by Igor Zinovyev on Friday March 10th 2017, 10:15
Yes, I know what you mean. So if you had to choose between having two versions for Steam and GOG and having only one version for, say, 1.31 and having separate HOWTOs inside, what would you choose?
Comment Reply
RE: Removing old version
by Shmerl on Friday March 10th 2017, 10:39
I'd make two versions entries, one for Steam and one for GOG. Since they can be not just different in packaging. I think Steam version has Steam specific integration in it, which GOG version doesn't have.

In various games in the past it happened, that for example GOG version worked in Wine, and Steam one didn't (and required extra fixes). So it's in general a good practice to keep them separate in Wine DB.
Comment Reply
RE: GOG versions should be merged into one
by Igor Zinovyev on Tuesday January 17th 2017, 1:32
Why do you think that would be a good idea? Technically "GOG version" is not a version, it's just an indication that the game was downloaded from GOG.com. We can just obsolete old versions if you'd like.
Comment Reply
RE: GOG versions should be merged into one
by Shmerl on Tuesday January 17th 2017, 1:45
Yeah, obsoleting would be fine. Maintaining just one GOG version should be OK. If GOG will update the release, it can be just updated with further submissions.
Comment Reply
RE: GOG versions should be merged into one
by Igor Zinovyev on Tuesday January 17th 2017, 1:49
Done, 1.31 and Steam are the only two non-obsolete versions now.
Comment Reply
1.8.0?
by Joe Amenta on Sunday December 27th 2015, 7:21
Can someone test with 1.8.0 (which claims to have added support for d3d11) and a native msvcrt that corresponds to what Witcher 3 uses?

If that all works to some degree, I could probably try implementing this: source.winehq.org/git/wine.git/blob/93d7356:/dlls/msvcrt/except_x86_64.c#l77
Comment Reply
RE: 1.8.0?
by Oinabilac on Sunday December 27th 2015, 15:42
Just tried with 1.9 and the game doesn't recognize d11 at this point, so the launcher doesn't even start.
Comment Reply
requires dx11
by Marcin on Saturday May 30th 2015, 16:45
Game needs DirectX 11.
Implementing vcomp and msvcr110.dll doesn't make sense without dx11.
Comment Reply
RE: requires dx11
by Seegras on Wednesday December 2nd 2015, 9:47
Can you explain what this means? I got the impression that if I install DirectX11 drivers from Microsoft, it should work. But it does not, so apparently this is about (the wine) d3d11.dll, which does not return a device:

fixme:win:EnumDisplayDevicesW ((null),0,0x213edb0,0x00000000), stub!
trace:d3d11:D3D11CreateDevice adapter 0x26c8b50, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels (nil), levels 0, sdk_version 7, device (nil), obtained_feature_level 0x213f420, immediate_context (nil).
trace:d3d11:D3D11CoreCreateDevice factory 0x26c26b0, adapter 0x26c8b50, flags 0, feature_levels (nil), levels 0, device 0x213f2b0.
fixme:d3d11:D3D11CoreCreateDevice Ignoring feature levels.
Comment Reply
Back