Ghost of Tsushima - GPU stops rendering frames
I can't reproduce the issue. The initial cutscene plays and finishes just fine without a GPU hang.
RTX 3090, 580.76.05.
All Settings on Very High.
Proton Experimental Bleeding Edge, so vkd3d-Proton 334e778136f2c3430c3319e0ba73f29d6329f902.
Do you have vsync on or off?
I have this in some games when enabling vsync (mostly UE5 games)
Do you have vsync on or off? I have this in some games when enabling vsync (mostly UE5 games)
No matter what settings I used, including disabling vsync, enabling it, going all the way down to quarter rate, there was no change in behaviour.
I also want to reiterate that the problem is consistently triggered on Proton Experimental, as well as the latest GE-Proton, but equally as consistent is how much further into the scene I can get if I drop down to Proton 9.0-4. It gets all the way to the one character challenging one of the Mongols to a duel or something (I can't really tell because it locks up again once the second character strides out of the pack).
Vsync is pretty trivial to implement for vkd3d-Proton and almost certainly not cause for an issue like this.
Vsync is pretty trivial to implement for vkd3d-Proton and almost certainly not cause for an issue like this.
Wouldn't be the first time or last Nvidia had freezes with Vsync in dx12 games. Would be silly to dismiss the thought instead of asking to verify
I found this post on the NVIDIA forums where this user appears to be having much the same problem as me, at least as far as symptoms go. The main difference is they report getting the bug to go away with repeated loads while I have had no such luck.
The description of the issue happening "when something is loaded for the first time" seems to coincide with what I've seen/recorded too.
Just to test, have you rolled back drivers to the previous 575? I was running arch a few days ago and had some major issues with the 580 series on my 5070 laptop GPU. Im more inclined to think this is Nvidia shenanigans than it is vkd3d as the nvidia forums report a number of games getting broken on 580 series drivers
@daruuuna
I found this post on the NVIDIA forums where this user appears to be having much the same problem as me, at least as far as symptoms go
Xid 13 is basically the Nvidia version of a GPU segfault as far as I know. It could be caused by a lot of different reasons so online reports like that are unlikely to be the same exact issue unless it's also about the same game.
Just to test, have you rolled back drivers to the previous 575? I was running arch a few days ago and had some major issues with the 580 series on my 5070 laptop GPU. Im more inclined to think this is Nvidia shenanigans than it is vkd3d as the nvidia forums report a number of games getting broken on 580 series drivers
Work has been very busy so I'll try this on the weekend and report back with results.
Alright, so after downgrading nvidia nvidia-utils lib32-nvidia-utils to cached versions of 575.64.05-X and linux linux-headers to cached versions of 6.15.9.arch1-1 I can confirm that the issue as detailed in the OP appears to have been resolved? Not only did I not experience a crash at the same moment as in my recording, but I got to gameplay in the intro (with the horses and stuff) AND it was on Proton Experimental as opposed to 9.0-4.
Later (maybe tomorrow? real life is still quite busy) I will do some more testing/playing the game further, maybe try and re-upgrade to latest and see if the problem still persists just to sanitycheck myself. As it stands, the GPU stayed pegged at around 100% usage thanks to having ingame settings set to high, and I had no issues.
What can I take away from this?
Exactly simillar issue. Resolved by downgrading to 575.64.05:
- In my case affects 4070 Ti Super
- I have 5070 Ti as well, thsi card is not affected. Plays well
- Confirmed as many times as I do downgrade/upgrade. The issue always comes back
- Both nvidia proprietary and open drivers are affected (I use CachyOS that provides these modules, not an installer)
- In game options don't make difference
So, Nvidia is to blame, most likely. In my case it stops everywhere in the game, in different saves, etc.
Welp, for the time being I've switched over to using the DKMS drivers to allow for keeping the kernel up to date. I'll check to see if the problem persists whenever the next numbered version drops, but it does appear that this is an NVIDIA problem and not a vkd3d problem.
Software information
Game: Ghost of Tsushima DIRECTOR'S CUT
Ingame settings: Any (Quality preset ranging from Very High to Medium, DLSS both On and Off, FSR Framegen has never once been turned on - no change in behaviour no matter what setting is adjusted)
System information
My apologies if this is not the right place to post this, but after a few days of Googling I found https://github.com/HansKristian-Work/vkd3d-proton/issues/2253 which matched part of the output of my Proton logs, so I figured I might as well post this here.
When attempting to play Ghost of Tsushima, the GPU appears to simply cease drawing frames to the screen. This occurs after a (gradual) rise in GPU usage reaching up to 100% after getting off the main menu (which is rendered in-game) and into the opening scene. Here, you can see the GPU usage graph from my PC from two separate instances of this issue:
https://imgur.com/LGu2U6s
https://imgur.com/9jV91bo
The first image shows an initial dip in GPU usage as I transition from the main menu to the New Game screen (there is a short loading screen between the two). After selecting difficulty/language options, the scene transitions on the fly to show character models entering the frame. At this point, the GPU usage increases as more character models appear onscreen, eventually reaching 100%, at which point new frames cease to be drawn to the screen. The computer doesn't crash, audio continues to play, and it's possible to kill the process and get back to the desktop. The rest of the computer functions as normal (i.e., it's not a total system hang). When switching to Proton 9.0-4 in Steam, I can get about 1 or 2 minutes further into the scene before this happens again.
Here is a video capturing this in action: https://mega.nz/file/yMgChSYK#r8jNIlLhNIZKav-q8JhW8kulju9NJrlySCsesToshdg
Here is the Proton log:
steam-2215430.log
The logfile stops being written to after the GPU seems to hang (at line 31,991). The following lines seem to be written after I click out of the fullscreen program, and everything from line 31,997 occurs after I kill the process. As far as I can tell, there's nothing helpful in the Proton logs because of this.
I ran dmesg -w as you can see in the video, and the error shown as the GPU hangs is:
NVRM: Xid (PCI:0000:2b:00): 13, pid=16003, name=GhostOfTsushima, Graphics Exception: channel 0x0000006e, Class 0000c7c0, Offset 00000000, Data 00000000After some more Google-fu I found this entry regarding NVRM Xid 13.
I've been tearing my hair out over the last day or two trying to figure this out and I'm about at my limit of understanding as a simple end-user. I just finished playing another fairly graphically-intensive game just recently (Death Stranding 1) at maximum settings with similarly high GPU usage and have not run into this problem. Combine that with the fact that the system remains usable even after this issue repeatedly appears and I wonder if it's got to do with GOT itself instead of a wider hardware problem...
If this is the wrong place to find help for this, please point me in the right direction.