Steel Division 2 (919640)

[g90215]

Compatibility Report

• Name of the game with compatibility issues: Steel Division 2
• Steam AppID of the game: 919640

System Information

• GPU: GTX 760 OC 2GB
• Driver/LLVM version: NVIDIA 435.21
• Kernel version: 5.3.0-26
• Link to full system information report as Gist: https://gist.github.com/g90215/b3205234f4826c300ac27cdbe804b80b
• Proton version: 4.11-12

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-919640.log

Symptoms

Issue#1. Tree foliage textures don't appear unless zoomed right in to ground level, and even then it's hit or miss. The trunks are always visible. Issue#2. Random whole-game lockups which never recover. When it hangs, the latest line in the Proton log always contains the same deadlock: err:ntdll:RtlpWaitForCriticalSection section 0xaf31c90 "?" wait timed out in thread 004f, blocked by 0053, retrying (60 sec)

Reproduction

Issue#1. Launch the first tutorial. All trees on the map will be missing foliage. Issue#2. Lockups happen randomly. Mostly on launching and exiting the game, but sometimes in loading screens. Never during gameplay as far as I have tested.

I have tried the following: -With esync enabled the game runs smoother, although seems to hang more often. -With DV9K enabled the game runs smoother. It appears to have no effect on stability -WINED3D11 renders only the GUI, trees (albeit with glitches), buildings and units. It does not render the terrain. -Forcing Steam to use older Proton versions all the way up to 4.11-12 -Disabling Steam overlay -Fullscreen and windowed modes -Setting the CPU governor to Performance -Verified the game integrity -Disabling/enabling shader pre-caching -The latest available (435) proprietary and older NVIDIA drivers for Ubuntu -Various in-game video options (all presets, using autosettings, etc) -Both the game and my system are fully updated. -ulimit -HN is 1048576

[birdspider]

Hi, SD2 is getting OOM killed on Proton Experimental, while Proton 7.0-2 seems fine.

As in: 16 GB RAM gets full, then swap (lag - quickly saving the game mostly succeeds,) then killed by kernel. This is fine-ish in SP but I assume horrible in MP matches.

Currently I play on Proton 7.0-2 to see if it happens again, and will change to Proton Experimental in a few days to see if it is strictly reproducible.

If it is, what kind of info should I provide.

[kisak-valve]

Hello @birdspider, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the issue, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

[birdspider]

@kisak-valve this turned out to be a non-proton / non-reproducable issue

1 day after I posted this 2 mem-leak fixes landend (one in mesa, one in kernel/amdgpu) - and I couldn't reproduce this since.