Open StructByLightning opened 6 years ago
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".
You may see better behavior with nvidia 396.51 or newer.
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 does not work.
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.
The Earth Elemental (Contract: Doors Slamming Shut) is invisible.
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:
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.
Regarding the staticky audio corruption issue, here is what I found:
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
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.
@HanFox try this PULSE_LATENCY_MSEC=60 %command%
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.
@michaldybczak You need the 396.54.09 driver for transform feedback support.
I don't get it. I need an older driver to get it to work?
It's not an older driver, it's the newest Vulkan beta driver that came out yesterday.
I thought that vulkan driver is within nvidia driver. If not, I'm not sure what package I should check on the Arch-based system. My packages are on Arch stable level.
EDIT: I checked with Arch wiki, vulkan driver for nvidia is within nvidia driver so I'm not sure where you get the number of the vulkan driver alone? Which nvidia driver will support that? If it came out yesterday then maybe it's still in arch unstable or testing so I should get it soon.
Hello @michaldybczak, nVidia has a vulkan developer series for experimental features at https://developer.nvidia.com/vulkan-driver. This driver series doesn't need to pass their internal quality control and the purpose is to get early feedback on new things before they get integrated into the mainstream driver.
So that means I just have to wait for it a little longer. I won't mess with GPU drivers by using developer driver, so I just update for the version that will come with this feature when it shows. Thanks for the info @kisak-valve.
@HanFox try this PULSE_LATENCY_MSEC=60 %command%
So far so good. Thanks @barni2000
@HanFox try this PULSE_LATENCY_MSEC=60 %command%
I also suffer from audio distortion in cinematics, but in my case this doesn't help. I don't have Pulse audio installed on my system (tried on Proton 3.7-8, as newer one is broken for me).
Hey there, don't know if I am right here. I was able to play the game without problems until recently. Only had the audio distortion problem after a couple of hours of playtime.
But now I cant even start the game. First I can see some text appearing (Witcher 3 is a trademark ...) but with a very low framerate. After that I only see the "Skip" in the lower right corner. But nothing happens. I need to kill the process in order to get out.
Any ideas? System
It won't start for me with Proton 3.16-1 beta and Nvidia 410.57. Worked quite well with older version.
FWIW, recent updates to Proton 3.16-2 and -3 fixed the problem for me.
I could launch the game before, now it wont start (but it says it is running in Steam).
This is my spec: GPU: GTX 1080 Nvidia driver: 410.66 Kernel version: 4.14.77 Proton version: 3.7 or 3.16-3
However, I can run the game via Lutris using wine-3.18-staging and DXVK 0.90.
How can I run proton via the command line to see if I can see any errors?
There is a way to enable logs for certain Steam Play games. I don't remember exactly how it is done (I did it and now I can't undo it ;p) but maybe someone hare knowns this. I only remember I had to find some proton config for the given prefix and edit something there. Alternatively, just run Steam in a terminal and then launch WT3.
For me, the game starts without a problem, although the first launch after an update is always visibly longer. I use GTX 970M and kernel 4.18, rest is the same.
@michaldybczak
I don't remember exactly how it is done ...
You shouldn't memorize everything, but one thing: use README (man, info, wiki, google ...). https://github.com/ValveSoftware/Proton#runtime-config-options
Well, it is not working with Proton. I attach the log if someone can see something in there.... steam-292030.log
It works well with wine-staging and dxvk, not with Proton.
My xorg-server version is: 1.20.2 (if it has something to do with this).
Hello @xexpanderx, 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. Additionally, does ulimit -Hn
output a high value or 4096?
@xexpanderx It is working with Proton, and past several days I'm enjoying Blood&Wine New game on Hardcore difficulty. No special settings required, game starts flawlessly from first ever run using Proton.
Your logs contains strange entries:
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "its:rules"
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 5: unknown element "its:translateRule"
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 8: unknown element "description"
18997.120:0024:0025:warn:module:load_builtin_dll failed to load .so lib for builtin L"Z:\\home\\alexsson\\.local\\share\\Steam\\steamapps\\common\\The Witcher 3\\bin\\x64\\D3DCOMPILER_47.dll": /home/alexsson/.local/share/Steam/steamapps/compatdata/292030/pfx/dosdevices/z:/home/alexsson/.local/share/Steam/steamapps/common/The Witcher 3/bin/x64/d3dcompiler_47.dll: invalid ELF header
18997.123:0024:0025:warn:module:load_builtin_dll failed to load .so lib for builtin L"Z:\\home\\alexsson\\.local\\share\\Steam\\steamapps\\common\\The Witcher 3\\bin\\x64\\PhysX3Common_x64.dll": /home/alexsson/.local/share/Steam/steamapps/compatdata/292030/pfx/dosdevices/z:/home/alexsson/.local/share/Steam/steamapps/common/The Witcher 3/bin/x64/PhysX3Common_x64.dll: invalid ELF header
Looks like your setup is somehow broken.
Hello @xexpanderx, 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. Additionally, doesulimit -Hn
output a high value or 4096?
Hi, the link: https://gist.github.com/xexpanderx/c7dccaf2d088729fa904e499f1212cc1
ulimit -Hn
1048576
BTW, @kisak-valve
do you really require WINEDEBUG=+module
?
this produces either more noise than help
WINEDEBUG=+loaddll
should produce more compact and user-frendly output.
@kisak-valve Requesting an XAudio2 label for this game... this is a Wwise title but they still use an XAudio2 context for the output stream.
Just installed The Witcher 3 and played about an hour in White Orchard. Everything worked just fine out of the box without any tweaking whatsoever. Ran quite well too at 1080p medium settings.
My specs: https://gist.github.com/Zoetrap/3f0fc6d113c5fef9cdf7d623ea5e81c8
Sound card says "Realtek" in the Steam system info (which is the built-in soundcard), but I'm actually using an external USB Interface (Steinberg UR242) for all audio. Worked flawlessly during my testing.