While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Marvel Rivals team issue a statement on recent bans for Steam Deck and macOS players
- The Awesome Games Done Quick Humble Bundle is a good deal not to be missed
- Valve set Palworld back as Steam Deck Playable but with multiple listed problems
- Funded in 5 minutes - the open source modular mini computer 'Pilet' is on Kickstarter
- GPD WIN 4 handheld plans to support Valve's SteamOS in 2025 (updated: nope) [updated]
- > See more over 30 days here
Recently Updated
- While Palworld enjoys a resurgence Valve dropped the rating to Steam Deck Unsupported
- GPD WIN 4 handheld plans to support Valve's SteamOS in 2025 (updated: nope)
- Valve confirms a public beta of SteamOS is coming as 'SteamOS expands beyond Steam Deck'
- Discord Canary on Linux breaks Wayland screen-sharing support for now
- Wireless HORIPAD for Steam gets a firmware fix for the Steam Deck OLED
View PC info
Awesome! Thanks!
For the record, 396.24 seems to take care of the performance regression, but... And there is a big but... I see flashing water textures over the dirt trails, in Crow's Perch. With __GL_NextGenCompiler=0, everything works fine.
@cRaZy-bisCuiT
Thank you very much! Since these instructions are truly plain and simple - and among the clearest I hitherto found on the web - I actually followed them already last weekend when trying to get dxvk running in a vanilla Ubuntu 16.04.
Wine-prefixing (wine 3.6 staging), dxvk-extraction and game-installation into that new prefix worked quite fine.
Dxvk also seems to run, since I can activate the Dxvk-Hud (with version, fps, memory etc.), but as soon as a game attempts to access DX11, I end up with a system freeze of the kind described under doitsujin's dxvk/issues/251.
So is there anything else I have to do? Copy some dlls or change something in winecfg?
Is Mesa 17.3.3, which I am running, the troublemaker, what other AMD-driver ought I to use? What AMD-driver do you employ, Biscuit?
PS: Since this is @Shmerl's Witcher-Thread, and I do not wish to spam it with general Dxvk-travails, I may try running Witcher3 on my system and then post results. Yet I shall have to re-download the entire game from GOG overnight.
View PC info
I wanted to provide an update on my efforts to get the Witcher 3 running on Fedora 28 (just upgraded). I was able to successfully get everything working with Wine Staging 3.7 and DXKV 0.42, but there was a specific step that I performed that might help others.
I'm not sure how many people dual boot, but I no longer use Windows so I was unable to install the Witcher 3 on Windows and simply copy over the files. What I ended up needing to to is this:
1. Create a new wine prefix (Wine Staging 3.7)
2. Run the GOG installer for the Witcher 3 (note that at the end of the installation it also installs a C++ redistributable package - which I believe it what causes the problems I was experiencing).
3. Copy the entire Witcher 3 directory and all it's files to a location outside the prefix.
4. Delete the wine prefix.
4. Create another new wine prefix (Wine Staging 3.7)
5. Move the Witcher 3 directory into the new "clean" wine prefix
6. Setup DXVK (I simply copied the DLLs to c:/windows/system32)
7. Use winecfg to set d3d11.dll and dxgi.dll to "native".
8. Run the game.
I think the key was creating a new "clean" wine prefix without the C++ restributable package, and to only have the Witcher 3 data files in that prefix.
Hope this helps others!
View PC info
Are you using GOG classic installer or Galaxy enabled one? I've always used the classic installer and never had this issue.
View PC info
Yup! I was using the Galaxy enabled installer, although I chose specifically to not install the GOG Galaxy client (customized the installation process). That explains the problems I was having...
Man, what a silly mistake. Do you think I should reinstall using the classic installer? Everything appears to be working at this point.
View PC info
I don't think you need it now, but keep it in mind for future installations.
Alright, following cRaZy-bisCuiT's instructions one by one in a new Wine 3.6-staging prefix, into which I installed TW3 GOTY via the classic GOG installer (i.e. not Galaxy), the Witcher starts and the menu with background campfire animation looks fine at 60fps.
Yet, alas, as soon as I commence e.g. 'Blood and Wine' I see this:
![](file:///home/galland/Bilder/Dxvk_Witcher3_Testrun_2018-05-04 11-28-10.png)
(disabling all TW3 post-processing options doesn't help either)
No crashes or freezes this time, I can exit via menu, change settings and restart as I like.
Both dxvk-hud and console info put out:
AMD RADV TONGA (LLVM 5.0.0), Driver: 17.2.8, Vulkan: 1.0.42
But console output starts with this warning and produces stacks of errors as these:
WARNING: radv is not a conformant vulkan implementation, testing use only.
[...]
err: D3D11Device::CreateGeometryShaderWithStreamOutput: Not implemented
[...]
err: D3D11Device::CreateBuffer: D3D11_BIND_STREAM_OUTPUT not supported
[...]
../../../src/compiler/spirv/spirv_to_nir.c:2737 WARNING: Unsupported SPIR-V capability: SpvCapabilityImageCubeArray
So I suppose something must be amiss or I should switch from AMD RADV to another driver.
Any advice, help, hint would be most welcome.
Much obliged.
View PC info
View PC info
Yep, your Mesa is too old.
View PC info
I'm usign Mesa 18.0.1 and Wine-staging-nine 3.6 (is the official Manjaro/Arch package). Game worked perfectly with my previous card (Radeon 7850), but when I tried with my new baby all I got is a black screen, my monitor saying "Out of range" and music and voices running in the background. Using alt-tab worked and the game seemed to work too, but not showing anything.
Any advice? Thanks in advance.
I haven't tried with DXVK (now that I think about it, I haven't even tried any Vulkan based game).
Note:
I already searched bugs.winehq.org and bugs.freedesktop.org without luck
Thank you very very much, thus I got it working! Sometimes it is these basic things amateurs ( not to say 'noobs' ) like me need to be pointed at straight away, and which should be included in the beginners' tutorial lyr3 intends to write.
Console and dxvk-hud now sport: AMD RADV TONGA (LLVM 6.0.0), Driver: 18.1.99, Vulkan: 1.0.68
Dxvk-hud indicating around 50-60 fps on High graphics settings (Nvidia hair-works off)
and between 25-40 on Ultra.
(wine having been updated to 3.7-staging)
Not bad at all for my venerable Radeon R9 380X and an Intel i5-2500K!
PS: After some fruitless and frustrating fiddling with building mesa myself yesterday evening (always some dependency and library amiss, troubles when building gallium, after patching that further errors...) I finally resorted to one Oibaf's Updated and Optimized Open Graphics Drivers on launchpad - which (comprising both mesa 18 and llvm 6.0) got it going in no time.
View PC info
I solved!
To run the game I had to set a virtual desktop into Winecfg.
Then I tried DXVK and it's absolutely impressive!
Installed dxvk-bin from AUR, lauched setup_dxvk64 into the right wine-prefix, removed the virtual-desktop from Winecfg and everything worked so well that I'm speechless! :D
View PC info
Interesting, I've never needed to use virtual desktop. But may be in-game fullscreen / borderless setting affects it.
View PC info
This may be useful to you: https://www.gamingonlinux.com/wiki/Building_Mesa_from_source
View PC info
It's strange even to me, honestly, and I can't find the source of the problem, but... it works now and this is what counts! ;)
Exactly the same happenend when I tried ELEX. Using normal wine-staging-nine lead to artifacts and application crash, when run fullscreen (I had game resolution set to 720p, my monitor is 1080p, because my old gfx card couldn't handle the game).
Then tried DXVK (remember: game resolution still set to 720p) and the game crashed when run in fullscreen. Set the virtual desktop, game worked like a charm. Then I set game resolution to 1080p, still running fine into a virtual desktop.
Finally I removed the virtual desktop and the game worked flawlessy (has some graphics artifacts, here and there, but it's ok for me).
I suspect the resolution change was the problem: maybe interactions with my window manager or so. I have an old DXVK (0.42) so there are bugs that where fixed into latest git.
View PC info
View PC info
Would love to know if anyone has come up with a work around.
View PC info
There was some discussion in Khronos internally. You can follow this issue. They however are looking for feedback from game developers who can explain how stream output is used usually, so Khronos could decide how to better match it Vulkan. I'm not 3D graphics developer, so I can't comment on that, but may be you know someone who can answer their question?
View PC info
Thanks for the response, I actually found that thread via google and it was certainly interesting (although way over my head). Does wine3d still have significant performance problems with the Witcher 3 or are things better now with Wine Staging 3.7?