Diablo IV [2344520] #7199
Labels
Game compatibility - Unofficial
Games not expected to work without issues
Regression
Confirmed working on an older version of Proton
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
A similar issue happens with Forza Horizon 4 |
|
Here are huge VRAM leak on Nvidia 3060 TI lastest stable driver, POP!_OS 22.04 |
|
I don't think it's a proton problem, per se, since there are Windows players experiencing it as well. For me, it started after the patch on October 24, 1.2.0d |
|
It is Proton problem. And it is for Nvidia only. |
|
For what it's worth, I noticed that with Diablo IV, there are two "reaping pid: 123455 --gameoverlayui" lines after I exit. When things leak, there's only one of those lines. Turning off the gameoverlay seems to help? I haven't had time to extensively test it, however. system info: https://gist.github.com/garpu/b4a05825c805bbe72285a95e80988e8d Edit: it still leaks. |
|
Seems this is the fix for Nvidia cards: |
|
I did a bunch of dungeons and ported around doing a whisper bounty. I think the PROTON_HIDE_NVIDIA_GPU trick works? I did have some swapping, but I also think the 1050ti isn't enough, even on low (regardless of the requirements.) I didn't have stuttering or the entire system slow down that happened previously. I think the longest I played was 40 minutes. (I don't have time to play longer to see.) my system RAM never went above 10GB. I think this is proof there's an issue with Diablo IV and an nvidia-based memory leak. I think it's a Blizzard problem, though, because a friend of ours (windows) has it, as well. |
|
For me, in win11 nvidia vram leak is fixed. But after all, this game run great on AMD GPU's/ |
Yes, this command let the game think we have a AMD GPU and uses optimizations for AMD and leak is fixed, because this game run on AMD card without any issue. I'm sure there is a easy fix the game optimizations to use AMD optimizations on Nvidia cards too. |
|
So this option will be harmless to AMD GPU's too, and can be added to Proton Experimental for D4 fix. |
|
Further testing (let's call it that...) this weekend, and I was able to play for 40-60 minutes at a time with no problems, other than the disconnects while porting, which is a known windows issue. I think the PROTON_HIDE_NVIDIA_GPU workaround works. |
|
Don't have the game to check, but apparently the latest battle.net update is having issues |
|
|
|
Diablo IV freezes after a few minutes of playing Issue transferred from #7414. Compatibility Report
System Information
I confirm:
SymptomsGame freezes after a few minutes. Accepts no input. Only option is to forcefully kill the game. ReproductionPlay the game. Does not seem to be triggered by any specific action or sound. Will freeze during busy fights or while completely idle in town. |
2 tasks
I get this error when I accidentally try to launch Diablo with wrong gpu that doesn't have enough vram to play the game. |
|
Getting a crash when trying to launch the game since today... Here is the relevant stack: Can't say if this issue is due to a bad deployment by Blizzard or if it's an issue to solve in Proton... FenrisDebug.txtSystem Runetime Diagnostics: https://gist.github.com/sim590/a6cbcd3751d36ce0275255ff89e0535b |
|
@kisak-valve just to be sure that my change was noticed. I mentioning here that I did put the System Runtime Diagnostics in a gist above at the end of my issue report. Hope this can be addressed soon as the new season of D4 begins tomorrow... 😺 EDIT: I just started the game now to test it and it seems that it is fixed. The game works again. I tested with GE-Proton9-5. EDIT2: I spoke to soon. It seems like it's crashing again. I did change the Proton version here and there and it's back to crashing. Sometimes, the game launches, but it crashes while logging on with the following: FenrisDebug.txt |
|
Thanks, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and test how the game behaves. |
|
I did test with kernel 6.8.7-arch1-2 (archlinux) and it is indeed not crashing at all! Thank you for pointing out the solution! |
|
Diablo 4 Korean input problem Issue transferred from #7766. Compatibility Report
System Information
I confirm:
SymptomsI can't enter Korean in Diablo 4 chat. Reproduction |
|
Hello @Sosouserf, please add |
|
steam-2344520-8.0-5.zip |
|
@Sosouserf Thank you for the logs - I'm looking into this but having trouble getting my keyboard input to Korean characters (which is what I'm assuming you are doing that broke). There seem to be several ways to get Korean keyboard input working - could you tell me which you are using so that I can have the best chance to reproduce? |
|
Gnome46 uses ibus ibus-hangul. |
|
Proton 9.0-2 updated, but I still can't enter Korean in chat. |
|
@Sosouserf Thank you for the tip! After a lot of messing around, I was finally able to reproduce the failure you reported. Thank you for reporting this regression! We will look into this and hopefully be able to fix it in 9.0 :) |
|
Hi, |
|
I'm running Diablo 4 on Proton 9.0-3 Release Candidate, but I still can't enter Korean characters |
|
I can't enter Korean in 9.0-3. Is this in development? Is this not possible in 9.0? |
|
@Sosouserf The Korean font entry should be fixed in experimental-bleeding-edge (beta branch of Proton - Experimental). I haven't had time to test this myself yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compatibility Report
System Information
Steam Deck - latest full 3.4.x release (NOT 3.5.1 preview)
I confirm:
Symptoms:
Diablo IV fails to reconnect to Blizzard servers after using the sleep/wake function. I'm not sure if this is a game issue or Proton, but the sleep/wake function on Playstation and Xbox work, so I'm reporting here for awareness.
Reproduction
Launch Diablo IV on Steam Deck
Connect to Blizzard Servers, load into game after character select
Put Steam Deck to Sleep
Wake Steam Deck back up
Your character is still in the world, with "Connecting to Diablo IV Servers" in the upper left corner
Game will fail to connect to Diablo IV servers, returns player to main menu
Game fails to connect to Diablo IV servers in main menu, application exits to desktop
Expected behavior is for the game to successfully reconnect to Blizzard servers and allow player to resume gameplay.
Note that in a normal scenario (e.g. on Playstation and Xbox), any server or client related hotfixes or patches will result in showing the player an error and exit the application. This is normal behavior when there is a server & client mismatch. The issue I am describing here is NOT a result of server/client mismatch. This issue is reproducible 100% of the time, even when using the sleep function very briefly (e.g. under 2 minutes).
The text was updated successfully, but these errors were encountered: