ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components

Other

24.28k stars 1.06k forks source link

Blockland (250340) #1343

Open vanyasem opened 6 years ago

vanyasem commented 6 years ago

Whitelist Request

Name of the game to be whitelisted: Blockland
Steam AppID of the game: 250340

System Information

GPU: GTX 1080
Driver/LLVM version: nvidia 396.54
Kernel version: 4.18.6
Link to full system information report as Gist
Proton version: 3.7-6

I confirm:

[x] that pressing the Play button in the Steam client is sufficient.
[ ] that runtime config options are necessary to run the game.
[x] that no workarounds other than the mentioned ones are necessary.

Issues

[x] I haven't experienced any issues.
[x] There are no issues left open for this game.

mallgrab commented 5 years ago

Changing shader quality in the settings crashes the game.

kisak-valve commented 5 years ago

Hello @mallgrab, 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, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

mallgrab commented 5 years ago

Nevermind I just tried using Proton 3.16-6 Beta. Does not crash when changing shaders like it used to in 3.7-6.

PrivateCaller commented 2 years ago

I'm still experiencing an instant crash when setting the shaders above Minimum on Proton 7.0-2 This issue appears to be specific to AMD GPUs, looking at ProtonDB and asking around.

System Information: https://gist.github.com/PrivateCaller/9833cc11b2fd2a351019c1e007091570 Proton Log: https://gist.github.com/PrivateCaller/8ad5aa5466d08cdd4e250166e39b499c

waspennator commented 6 months ago

Shader settings still seem to crash the game back to library on my oled deck if I set it to anything above minimum. Given that the deck is powered by AMD hardware, that's the reason why.

steam-250340.log

Seems like something happens around here.

Unhandled exception: page fault on read access to 0x00000000 in wow64 32-bit code (0x00000000).