Proton
Proton copied to clipboard
ValveSoftware
The Witcher 3 (292030)
- Rotfiends are invisible. Still present with Nvidia 396.
- The Wild Hunt hounds (battle in the elven ruins with Keira Metz) are invisible.
- When in bordered window mode (1600x900), alt-tabbing out of the window works. However, the mouse cursor occasionally reverts back to the Witcher cursor if the Witcher window is underneath the foremost window. When it does this, the Witcher window does not have focus and I can't click on the foremost window. Still present with Nvidia 396.
- Clicking to focus on the Witcher window works, but the cursor is no longer locked to the window. Minimizing the Witcher window and then bringing it back up temporarily solves the issue. Still present with Nvidia 396. However, if you click the black menu (but not on a button) when clicking to focus the Witcher window, the cursor will become locked again once you resume the game. Super weird. I don't think it worked that way before. The menu fix doesn't always work either.
- Audio occasionally becomes staticky and distorted. Restarting the game fixes the issue.
- Some buttons have weird hit boxes. For example, the slider to bet during a Gwent game requires you to click below the graphic. Still present with Nvidia 396.
Hello @StructByLightning, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, are you testing the GOTY edition?
Link. I don't think I'm using the GOTY version. I think I bought the base game first and then the expansion pass, but I don't remember for sure. Is there a way to tell? In my library it's titled "The Witcher 3: Wild Hunt".
Updated and you're right. Performance is much better, I'm staying locked at 60FPS nearly constantly now, with the occasional momentary drop to 50. I'll edit my original post as I find out which issues still apply.
My performance seems to be about 70% of what I get on windows 10. The frame rates are playable, but the frame times spike up very high every couple of seconds making navigating around the map a choppy experience. Every red tick on the graph was a moment where the game stuttered briefly.
Ubuntu 18.04 Ryzen 1700 GTX 1070 with driver 396.54
@Warrengbrn What software are you using to display these stats? Or are they built into the game?
Rotfiends are invisible because Stream Output is not supported by Vulkan. https://github.com/doitsujin/dxvk/issues/135
@ArekPiekarz Those can be enabled for DXVK via an environment variable https://github.com/doitsujin/dxvk#hud
@ArekPiekarz
/home/'user'/.steam/steam/steamapps/common/'Proton folder'
Rename user_settings.sample.py to user_settings.py and you can configure the performance hud from that file with the comments listed in the link @valeth sent.
Nvidia HairWorks worked for a week after updated Nvidia driver to 396.54 then stop working.
OS: Ubuntu 18.04 LTS Graphic card: Geforce GTX 1070 (driver 396.54) CPU: i7-8700 @ 3.70 Ghz
Is anyone else having no audio at all with TW3? I'm not sure if I've somehow mangled my audio or something but the game plays no sound whatsoever.
Fedora 28 Ryzen 7 1700 / GTX 1080 (driver 396.45) - probably not relevant but whatever pulseaudio 12.1-1, alsa-lib 1.1.6-2
Audio works fine for me on both Mint 18.3 and Gentoo..
I am suddenly having a weird issue though, last night TW3 worked fine but today it deadlocks a few seconds after loading my game.. I have to force kill it to regain control of my desktop
Doesn't do that in Wine-3.15+dxvk-0.71, but the performance is much poorer for some reason.
Log attached, freeze happens at time ~49412 where it starts loading and unloading dinput a few times. Using Proton 3.7-6 Beta steam-292030.log
Audio will corrupt occasionally, restart of game 'fixes' it. Invisible enemies are not just related to vulkan stream output not supported (https://github.com/doitsujin/dxvk/issues/135), there's also some oddities occuring when running with wined3d (some rotfiends are invisible, others are not, hounds of the hunt are invisible, in both dxvk and wined3d).
Odd keyboard inconsistencies when running with vulkan compared to PROTON_USE_WINED3D11=1 mode - I'd like someone to confirm or reject this:
~~In the game context, casting a spell is by pressing Q, once an 'alternative spell mode' is active and equipped, you hold Q to cast the alternative mode. When I run in wined3d mode, this works. When I run without it (dxvk/vulkan translation), for some reason this doesn't work. While holding the key, it just casts it normally. Tested so far is window vs fullscreen vs borderless etc, no change. (there are no ingame key bind options for changing this, unless I missed it)~~
Update: I ended up reproducing an old game bug that's still around. Reference and fix: CD Project Red forum thread on it.
Adding a 'bug' here, I don't know what it is but it's consistent (on my system): Running the game through the steam client will at some point reach a state that I thought initially was a memory leak (jittery/laggy fps that never clears). Config file settings for increasing memory/texture memory didn't make any difference. It always happens (no exceptions), during a long play session.
In an attempt to track down at least a nice error log, I then ran it with PROTON_DUMP_DEBUG_COMMANDS=1 %command%, and ran it via the run script it generates. The 'problem' was, it never occurs again. I then played about 20 (?) combined hours with it using the run script, never happens. Figuring a sneak update and bad timing on my part, I ran it in the steam client interface again, just now. 'Bug' hit about 20 minutes in.
There's an FPS drop (towards needing a restart to clear, not something you'd want to play with) due to unknown reasons that only occurs when running it through the steam client at random times (20 minutes in if you're lucky, looking to find it, or an hour or more in), that does not appear at all when running it in a terminal with the run script generated through the debug command option.
Something about what steam hooks into it, or the steam API <-> proton <-> this game? I'm clueless. (Steam Beta client, have not tested this in non-beta)
I get the staticky audio corruption bug too.
I'm not sure what my settings are but under the default plug and play I can use the normal mode and alt mode just fine.
@triffid @Tuuvimer Cheers for the responses. Seems as it may just be an issue with my setup as it now appears to happen in some other games. Maybe a bug in Fedora or something. That said, when I do get sound in TW3 it's not too staticy and I haven't gotten any major audio corruption yet.
Audio will corrupt occasionally, restart of game 'fixes' it.
It happens to me sometimes too and I noticed, it's a depends on... Steam Controller being on. When I disable Steam Controller, restart steam, launch the game, sound issue is gone and then I can enable Steam Controller again. Weirdly enough, this happens only rarely. For the most time, Steam Controller or Big Picture Mode are fine and are not causing a sound issue. So all in all, this is an easy workaround.
My experience with Witcher 3 is:
- I have in average 20% lower FPS than on Win10, which is expected by dxvk so it's all right
- lags can happen sometimes but it's a matter of hardware catching up, so that's not a software related in my case, 99% of time game is fluent and 100% playable with ultra settings on gtx 970M (Manjaro), which is subjectively comparable to windows, so it's almost like native-like experience, when one forgets stats and some minor bugs
- nvidia hairworks don't work, not a big deal in the end effect, it would be nice if it worked but it's not crucial
- some monsters are invisible, also not a big deal, they can still be easily defeated, so for me, those are high-level earth elementals (low-level ones are visible) and sirens. Maybe once or twice, I had some other rare monster being invisible. Other than that it's all fine.
- in some locations water animation glitches, so I can see straight cracks of the surface and beneath is as there was no water, but for most of the time water is rendered correctly
- the game may freeze but that happened twice for a 2-week gameplay so that's like a non-issue
In my opinion, the game is perfectly playable on Proton. There are some glitches here and there that may be ironed out with time but all in all, it's a fantastic experience.
I use neither steam controller nor big picture mode, and my sound will become gritty and echoey after several hours of gameplay (exact time varies). Simply restarting TW3 fixes it.
The sound issue is thus not related to steam controller or steam big picture mode.
@triffid, then we have different sound issues. Once the game launches with correct sound, it stays ok all the time. It would be nice to see if some kind of bugs happen more often on certain distros then others. This could tell us if the issue is with package versions. From what I saw, Ubuntu users on average have more issues with Witcher 3 than Arch/Manjaro ones but that may be a flawed observation.
- Trees shake too much in Linux
- Higher GPU fan noise in Linux compared to Windows (GPU: R9 390, FPS: locked at 30)
Regarding the staticky audio corruption issue, here is what I found:
- Playing a game session continuously for extended period of time (more than 2-3 hours for me, but I imagine this can vary depending on the machine) consistently reproduces the issue.
- Same issue can be reliably reproduced using the method above in more than one games (Witcher 3, Endless Space 2)
- Like many people mentioned before, for both games in which I found the issue, it can be reliably "resolved" (temporarily at least) by restarting the game session one way or another, until the ongoing session lasted extended period of time again.
If I am to take a wild guess, it sure feels like some kind of memory buffer overflow problem to me.
Peripheries of my machine: Ubuntu 18.04.1 LTS GeForce GTX 1080 Driver Version: 396.54 Intel i7-8700
The audio issue seems to be gone. Anyway, on Manjaro I haven't experienced the audio problem since I described it here (23 days ago). I was playing quite often recently (just finished the game) and audio was fine. There were so many Witcher 3, Steam and Proton updates so I assumed this problem was fixed during one of them.
Also, it looks like the problem was not identical to all people. For me, it was quite opposite to what was described above. The issue happened only at the beginning, but when I managed to run the game correctly, it was just fine no matter how long the game was on. But the sounds were "staticky" so the description is accurate.
So basically the only issue left for me was the lack of some monsters or even faces (rarely). The water issue was gone as well.
Once in a while game crashed after a load but as I recall games in overall were also crashy on Windows, so one crash for 2 days is not standing out ;) - everything within a norm IMO.
In general Witcher 3 runs great. Just fix the missing textures bug and all is fine.
@michaldybczak what "missing textures" bug? That description is rather ambiguous, people call literally everything "missing textures".
Invisible monsters should be fixed with Proton 3.16 if you have a Vulkan driver that supports the new Transform Feedback extension.
Missing textures aka invisible monsters (sometimes vampire faces).
Thanks for the info about when the bug will be squashed. I use Manjaro so I will rather have a driver that will support it, providing the driver support for it will show at the same time.
My $0.02 using Proton 3.16-1 beta
- Mouse sensitivity is unplayably high - moving the mouse the smallest amount possible to the left or right spins the camera almost 360 degrees (with the in-game mouse sensitivity turned down to the minimum). For reference I'm using a Logitech G502 and I've tested at 125Hz and 1000Hz polling rates and a range of DPI settings
- FPS is noticeably lower than in Windows, but still playable
- Geralt's hair doesn't render
I would have tested some more (combat, etc) but the mouse issue makes it completely unplayable. Worth mentioning that this particular issue did not occur in Proton 3.7
It won't start for me with Proton 3.16-1 beta and Nvidia 410.57. Worked quite well with older version.
Proton 3.16-1 beta works well for me and everything seems to be rendering everything correctly after patching mesa with the RADV patches for VK_EXT_transform_feedback.
Like others, however, I do get the sound going crackly sometimes. Sometimes after hours of play, sometimes only in cutscenes, sometimes only on the main menu. Relaunching the game sometimes fixes the issue, sometimes the issue just moves to another part of the game.
I haven't figured out any specific reason, or any events that cause it.
Just checked Proton 3.16-1 beta, nvidia 410.57-2, using Steam Controller (so I can't say anything on mouse sensitivity that was posted above), OS: Manjaro KDE unstable, kernel 4.18.14-1. Witcher 3 downloaded two large files after switching to Proton 3.16-1 beta so I expected some changes.
Everything seems to be correct but Sirens are still invisible, so maybe the driver is not there yet? So in the end nothing new. Sound is ok.