Open Smoukus opened 1 year ago
MasterFighterr
commented
1 year ago Any news on this? I posted to Fatshark forums after discovering the workaround. Fatshark will unfortunately be putting no resources into it, I have a feeling it is something to do with VKD3D as Halo Infinite is having issues with this as well.
alvord-industrial
commented
1 year ago As of latest game update, I am having extreme graphics glitches; either complete darkness or torn up yellow lighting Seen here:
system info: https://gist.github.com/alvord-industrial/4bb1172db56c4e3a96002244090f29a6 log: steam-1361210.log
tlneondo
commented
11 months ago Getting some graphics vertex issues, It'll load in fine, then after a minor stutter, the models on my weapon's ironsites (as well as other things appear to get messy:
Then after adjusting the Model LOD slider back and forth, it loads back in properly, only to break later.
This was tested on ProtonGE 8-15 as well as Proton 8.0.4
OS: EndeavourOS Linux x86_64
Kernel: 6.1.55-273-tkg-pds
Resolution: 2560x1440
DE: Plasma 5.27.8
WM: kwin
AMD Ryzen 5 3600 (12) @
AMD ATI Radeon RX 5700XT
Memory: 6130MiB / 15901MiB
Thermatix
commented
11 months ago I think the problem is LOD related issue, I think that somehow the graphics get stuck on the lowest LOD model.
I also want to report, since the most recent major update (Class tree update) The game has been unstable, I can get through a single game before it crashes.
Billli11
commented
11 months ago @tlneondo The look like the mesh streaming issue.known issue
Change line 57 to
disable = truein
steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini
should fix the problem.
raaffaaeell
commented
10 months ago Hello there, I'm getting this crash on the steamdeck after I click play on their launcher
` Oct 15 01:50:49 steamdeck systemd-coredump[37552]: [🡕] Process 35891 (gamescope-wl) of user 1000 dumped core.
Stack trace of thread 35925:
#0 0x0000564427a08301 n/a (gamescope + 0x5e301)
#1 0x0000564427a1a9a0 n/a (gamescope + 0x709a0)
#2 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#3 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#4 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35891:
#0 0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x0000564427a16dff n/a (gamescope + 0x6cdff)
#2 0x00005644279cc0cf n/a (gamescope + 0x220cf)
#3 0x00007f5b13239850 n/a (libc.so.6 + 0x23850)
#4 0x00007f5b1323990a __libc_start_main (libc.so.6 + 0x2390a)
#5 0x00005644279edeb5 n/a (gamescope + 0x43eb5)
Stack trace of thread 35924:
#0 0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x0000564427a40402 n/a (gamescope + 0x96402)
#2 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#3 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#4 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35895:
#0 0x00007f5b132e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
#1 0x00007f5b132ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
#2 0x00007f5b12100455 n/a (libvulkan_radeon.so + 0x100455)
#3 0x00007f5b1225c34c n/a (libvulkan_radeon.so + 0x25c34c)
#4 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#5 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35894:
#0 0x00007f5b13299f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007f5b1329c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007f5b1225c41e n/a (libvulkan_radeon.so + 0x25c41e)
#3 0x00007f5b1223998c n/a (libvulkan_radeon.so + 0x23998c)
#4 0x00007f5b1225c34c n/a (libvulkan_radeon.so + 0x25c34c)
#5 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35893:
#0 0x00007f5b13313c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x0000564427a1c607 n/a (gamescope + 0x72607)
#2 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#3 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#4 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35928:
#0 0x00007f5b13299f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007f5b1329c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007f5b134d9e11 __gthread_cond_wait (libstdc++.so.6 + 0xd9e11)
#3 0x00005644279f69d5 n/a (gamescope + 0x4c9d5)
#4 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#5 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35923:
#0 0x00007f5b13321266 epoll_wait (libc.so.6 + 0x10b266)
#1 0x00007f5b0a439579 n/a (libspa-support.so + 0x13579)
#2 0x00007f5b0a42cbe3 n/a (libspa-support.so + 0x6be3)
#3 0x00007f5b1383c26f n/a (libpipewire-0.3.so.0 + 0x4126f)
#4 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#5 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35927:
#0 0x00007f5b132e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
#1 0x00007f5b132ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
#2 0x0000564427a1de67 n/a (gamescope + 0x73e67)
#3 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#4 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#5 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 35926:
#0 0x00007f5b1330f900 __open64 (libc.so.6 + 0xf9900)
#1 0x00005644279efb05 n/a (gamescope + 0x45b05)
#2 0x00007f5b134e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
#3 0x00007f5b1329d44b n/a (libc.so.6 + 0x8744b)
#4 0x00007f5b13320e40 n/a (libc.so.6 + 0x10ae40)
ELF object binary architecture: AMD x86-64Oct 15 01:50:49 steamdeck systemd[1]: systemd-coredump@10-37550-0.service: Deactivated successfully. `
I'm running the preview branch, 3.5.1
Thermatix
commented
9 months ago The game is becoming more and more unstable with each release of dark tide, and recently the game crashed (in this particular case, I'm reasonably sure it wasn't a proton issue, comp overheated) and then got stuck on the authentication screen and wouldn't let me back in until after the game I was in had concluded, because of course the game crashes in the last section (again, reasonably sure it wasn't a proton issue, what I'm frustrated about is that the game wouldn't let me back in until it was too late).
Patola
commented
8 months ago On the Steam Deck, the game is for me consistently crashing just after the initial window, right after when it completes the "compiling shaders" progress bar. It gets completely black then after a few seconds reboot the Steam Deck. Tried regular proton, experimental, hotfix and GE and had the same issue every time.
On the other hand, on my full-AMD PC with Archlinux, the game runs smooth, no issues. Can play for hours on end.
What diagnostic data I can send to help on troubleshooting this one?
Billli11
commented
8 months ago @Patola Try running it in desktop mode.
there are open issue in gamescope's github https://github.com/ValveSoftware/gamescope/issues/993 about darktide crashing with gamescope.
Patola
commented
8 months ago Good point, I haven't tried that. Will try.
Patola
commented
8 months ago It did indeed work in Desktop mode.
raaffaaeell
commented
6 months ago The game does not start with proton 9 and latest mesa on Fedora 39
I get this message
wine: Call from 00006FFFFFC1CE87 to unimplemented function amd_ags_x64.dll.agsDriverExtensionsDX12_PushMarker, aborting
Edit: After proton beta 14, the game is back on proton 9, thanks volvo
soypat
commented
6 months ago I'm unable to play this game due to networking issues. Also getting something similar with 6 days in Fallujah. See issue: https://github.com/ValveSoftware/steam-for-linux/issues/10598
Steam networking failure on Warhammer 40k: Darktide and Six days in Fallujah
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/10598. @soypat posted on 2024-03-09T20:55:05:
Steam Beta Branch: Stable Client Steam Version: 1709846872 Steam Client Build Date: Wed, Mar 6 5:28 PM UTC -03:00 Steam Web Build Date: Thu, Mar 7 6:17 PM UTC -03:00 Steam API Version: SteamClient021
$ neofetch
...-:::::-... pato@qtpi
.-MMMMMMMMMMMMMMM-. ---------
.-MMMM`..-:::::::-..`MMMM-. OS: Linux Mint 21 x86_64
.:MMMM.:MMMMMMMMMMMMMMM:.MMMM:. Host: B660M DS3H DDR4
-MMM-M---MMMMMMMMMMMMMMMMMMM.MMM- Kernel: 5.15.0-100-generic
`:MMM:MM` :MMMM:....::-...-MMMM:MMM:` Uptime: 4 hours, 13 mins
:MMM:MMM` :MM:` `` `` `:MMM:MMM: Packages: 3188 (dpkg), 23 (flatpak),
.MMM.MMMM` :MM. -MM. .MM- `MMMM.MMM. Shell: bash 5.1.16
:MMM:MMMM` :MM. -MM- .MM: `MMMM-MMM: Resolution: 1920x1080, 1920x1080
:MMM:MMMM` :MM. -MM- .MM: `MMMM:MMM: DE: Xfce 4.16
:MMM:MMMM` :MM. -MM- .MM: `MMMM-MMM: WM: Xfwm4
.MMM.MMMM` :MM:--:MM:--:MM: `MMMM.MMM. WM Theme: Mint-Y
:MMM:MMM- `-MMMMMMMMMMMM-` -MMM-MMM: Theme: Mint-Y-Dark-Purple [GTK2/3]
:MMM:MMM:` `:MMM:MMM: Icons: Mint-Y [GTK2/3]
.MMM.MMMM:--------------:MMMM.MMM. Terminal: xfce4-terminal
'-MMMM.-MMMMMMMMMMMMMMM-.MMMM-' Terminal Font: Monospace 17
'.-MMMM``--:::::--``MMMM-.' CPU: 12th Gen Intel i5-12400F (12) @
'-MMMMMMMMMMMMM-' GPU: AMD ATI Radeon RX 6800/6800 XT
``-:::::-`` Memory: 13502MiB / 31933MiB Just ran
sudo apt update -y && sudo apt upgrade -yand still happening.
Games that previously worked (Six days fallujah) now throwing a cloud error (I assume it is related to steam) on startup screen. I am not able to play online or invite friends to my game. See images.
Warhammer 40k: Darktide also throws a network error on startup and fails to run entirely.
I've tried several other games such as Counter Strike 2, Lethal Company, Broforce, Sid Meier's Civ VI, Ready Or Not, among others in online play and they seem to work OK, no errors. This is the behaviour I was expecting.
After first startup cutscene (only option is to close it):
On loading game:
On clicking "Fireteams" or "Wargames":
On trying to invite friends:
kisak-valve
commented
6 months ago Hello @soypat, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the network issue, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please open a new compatibility report for the other game since it doesn't look like there is one already.
soypat
commented
6 months ago Done! steam-1361210.log.zip
kisak-valve
commented
6 months ago Looking at your Proton log, err:steamclient:create_win_interface Don't recognize interface name: SteamUser023 looks like the line of interest. SteamUser023 is part of SteamWorks 1.57, and support for that was added in Proton 8.0-3. Please switch to a newer Proton version and retest.
canwiz01
commented
3 months ago I am having an issue with the game crashing on the loading screen after launching that says 'Processing Inquisitorial Clearance'. Logs and system info below.
System info: GPU: RX 7800 XT Video Driver Version: Mesa 24.0.8-arch1.1 Kernel Version: 6.9.2-arch1-1 Steam Version: 1716584667 Proton Version: 9.0-1 and Experimental Full system report
kisak-valve
commented
3 months ago Hello @canwiz01, your system is configured to run the game with AMDVLK. Can you test how it behaves with mesa/RADV?
canwiz01
commented
3 months ago Switching to RADV fixed the problem, the game seems to run fine now. Thank you.
kisak-valve
commented
2 months ago Warhammer 40k Darktide crashes during play, closes steam and causes gdm to restart
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7830. @DarkeOne posted on 2024-06-12T23:47:55:
Radeon RX 7900 xtx
Mesa version 24.0.3
Kernel version: 6.8.0
System info...https://gist.github.com/DarkeOne/802f0de7400e43271614e71ba6fb59f6
Proton version:8.0.5 to 9.0, even GE 9.7
This game runs great on my system-right up until it crashes. The game freezes, screen goes black, and I'm dumped to a login screen because I think GDM crashed too (newb here). Steam also crashes as well. If I try to run the game again, it simply won't run, generating a file with an error "_object 'libgamemodeauto.so.0' from LDPRELOAD cannot be preloaded (cannot open shared object file): ignored."
It doesn't matter what Proton version I use, what graphic setting I run (low or high), it happens. Sometimes right at the beginning of a match, sometimes after two or three matches. It does this on any linux distro I run (Pop OS, Fedora KDE, Nobara)
I really like this game, and I hate Windows. Any help is appreciated. Thanks for reading!
Steam Runtime Diagnostics...
https://gist.github.com/DarkeOne/ad54eef4780002ad1929ffb43afa3302
kisak-valve
commented
2 months ago Hello @DarkeOne, the issue you've described reads like a video driver issue. I'd check if there's any hints in dmesg around the crash.
It may be worthwhile to test how the game behaves with a current release mesa from a PPA like oibaf or kisak-mesa, and if that doesn't mitigate the issue, report what you found to the mesa devs so they can ponder it from the video driver's side.
DarkeOne
commented
2 months ago I'll try a current release mesa and see what happens. Many thanks!
I checked dmesg, sadly I'm a newb and understand little. However, I did see this over and over again and something tells me even a newb knows this could be an issue.
[ 329.149588] [drm] Skip scheduling IBs! [ 329.149588] [drm] Skip scheduling IBs! [ 329.149589] [drm] Skip scheduling IBs! [ 329.149590] [drm] Skip scheduling IBs!
owainkenwayucl
commented
2 months ago Since the release of Proton 9.0-2, Darktide is exhibiting a new problem on my Steam Deck (running the "stable" SteamOS), namely after the launcher about 2/3 of the time it shows the "Building shader cache" dialog and then hangs at 0% (not the usual crashing behaviour on other platforms where it crashes after this finishes).
I've tested with Proton experimental and it has the same problem, but forcing the most up to date version of Proton 8 (8.0-5) resolves this issue. I did not have this problem with 9.0 before 9.0-2 so something fixed in that must have broken shader cache generation sometimes in Darktide.
It's not a super serious issue as you can just kill it and relaunch until it works (and the game is stable after that), or force 8.0-5 but it probably implies there's a bug that will impact other titles (I would guess in the improved d3d->vulkan stuff?) and it's reproducible with Darktide.
I do have shader precaching turned off in Steam so it's possible turning that on would fix it but oh my the storage space!
kisak-valve
commented
2 months ago Hello @owainkenwayucl, please add PROTON_LOG=1 %command% to the game's launch options. reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Taranchul
commented
2 months ago Since the release of Proton 9.0-2, Darktide is exhibiting a new problem on my Steam Deck (running the "stable" SteamOS), namely after the launcher about 2/3 of the time it shows the "Building shader cache" dialog and then hangs at 0% (not the usual crashing behaviour on other platforms where it crashes after this finishes).
Actually, I also had this problem with Proton 9.0 on my PC. My current quick & dirty solution is to rename the file shader_cache\bundled_shader_cache.hans to somethinge else. Then the cache building is replaced by an error message that you can click away without any negative effects in my experience.
owainkenwayucl
commented
2 months ago @kisak-valve sorry to be picky about this but do the logs contain any private information? (I'm thinking things like authentication with the Steam servers etc.)?
Middlepepper
commented
2 months ago @kisak-valve sorry to be picky about this but do the logs contain any private information? (I'm thinking things like authentication with the Steam servers etc.)?
hmm: #5484
From what I can see it is just your steam profile ID which can be found publicly as long as you know the Steam Username. If you Ctrl +F "Steam_SetMinidumpSteamID:" in the proton logs. you can find this ID and remove it which will remove the "private information" in the proton log.
sclu1034
commented
1 month ago I'm running into the same issue. Dropping down to Proton 8 works fine, but both stable Proton 9 and latest Proton-GE get stuck at "Building shader cache" after the launcher. Notably, while playing around with settings and startup options, I sometimes got it to run once. But a consecutive attempt right after would always fail. Presumably the game gets stuck at validating an existing cache, rather than at building a new one. So if the changes are significant enough to invalidate the cache, it will work once.
Log of a failing attempt: https://gist.github.com/sclu1034/71516d0e98b13d70f78c5f4181368e67
owainkenwayucl
commented
1 month ago For what it's worth - I've not experienced the problem with the latest two releases of Proton experimental, but not entirely sure if that's luck or not so it may be fixed?
Thermatix
commented
1 month ago So I don't know if this issue is with my computer/install or what but, I've started encountering an issue, I get to the initial screen after the intro movie and I press space to authenticate and then suddenly performance tanks to the point it affects system performance and then the game just crashes to desktop.
I think I may have forgotten to install something or forgotten something else (and I don't recall what it might be if this were indeed the case) but the game used to run perfectly fine but I have since reinstalled the OS (EndevourOS) and now I'm getting this issue.
Other games work fine without any issue (tested Cyberpunk 2077 at max settings).
I have installed the latest version of Mesa.
Same issue no matter which version of proton I'm using, so I concede It might not be a proton issue which was why I was reluctant to add this post.
Don't know what info is needed to debug.
./o. thermatix@black-tower
./sssso- ---------------------
`:osssssss+- OS: EndeavourOS Linux x86_64
`:+sssssssssso/. Kernel: 6.10.2-arch1-1
`-/ossssssssssssso/. Uptime: 5 hours, 23 mins
`-/+sssssssssssssssso+:` Packages: 1344 (pacman)
`-:/+sssssssssssssssssso+/. Shell: bash 5.2.26
`.://osssssssssssssssssssso++- Resolution: 2560x1440
.://+ssssssssssssssssssssssso++: DE: Plasma 6.1.3
.:///ossssssssssssssssssssssssso++: WM: KWin
`:////ssssssssssssssssssssssssssso+++. Theme: Breeze-Dark [GTK2], Breeze [GTK3]
`-////+ssssssssssssssssssssssssssso++++- Icons: breeze-dark [GTK2/3]
`..-+oosssssssssssssssssssssssso+++++/` Terminal: konsole
./++++++++++++++++++++++++++++++/:. CPU: AMD Ryzen 5 7600X (12) @ 5.453GHz
`:::::::::::::::::::::::::------`` GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900M
Memory: 9951MiB / 31834MiB EDIT:
So I don't know why but the game it seams refused to run with AMDVLK which I hadn't realised was a thing (The it not running with AMDVLK, not that AMDVLK exists) as I normally use the Mesa drivers but well, when I re-installed steam this time I installed them without realising (I honestly forget which one is which since I only have to this once every time I install steam...).
So I switched to the Mesa equivlents and the game started. Yay.
notpeelz
commented
2 weeks ago I've been getting very frequent GPU resets (ring gfx_0.0.0 timeout), making it nearly unplayable. I end up crashing every other match I play, and if I re-join a match in which I crashed, the crash usually occurs again very quickly (I've had it happen 6+ times in a single match). I've always had GPU reset issues with this game, but it has become so much worse lately.
I don't have this issue with any other games I play.
System info:
Taranchul
commented
2 weeks ago I've been getting very frequent GPU resets (
ring gfx_0.0.0 timeout), making it nearly unplayable.
Did you try to set Textures to Medium like suggested in the OP? It fixed the GPU resets for me completely.
notpeelz
commented
2 weeks ago Did you try to set Textures to Medium like suggested in the OP? It fixed the GPU resets for me completely.
Just tested it. I crashed within 5 minutes of joining a match.
Edit: I've set textures to "low" and I was able to play 5+ matches without crashing. Nevermind, it still crashes.
Compatibility Report
System Information
I confirm:
steam-1361210.log
Symptoms
As of latest game update (1.0.31) it freezes, and crashes eventually after selecting your character.
Workaround: It has apparently something to do with
Textures. SettingTexturestoHighwill reproduce that freeze and crash. Setting them toMediumorLowwill make the game playable again.