Open zelikos opened 5 years ago
I confirm the same issue with Intel I7 6700, 16GB Ram and Nvidia Geforce GTX 1060 (6GB) with Driver 418.56, Kernel 5.0.
On Proton 4.11-8 the game runs, but save data doesn't work at all.
Proton 4.11-8 log: steam-840720.log
I can see the problem with BCryptGenerateSymmetricKey
Currently with Proton 6.3-7, the game starts and runs, sound works, but has graphical issues, and after using PROTON_NO_ESYNC=1
, the graphical issues are fixed
Edit: just tested Proton Experimental
, there graphical issues showed up again, even with PROTON_NO_ESYNC=1
set
Hello @hasezoey, can you take a screenshot of the graphical issue? It may be worthwhile to also mention your issue to your video driver vendor.
can you take a screenshot of the graphical issue
sure
It may be worthwhile to also mention your issue to your video driver vendor.
hardware: AMD Vega 64, software: amdgpu & mesa (stock manjaro 21.1.6)
DE system: KDE Plasma Wayland & Pipewire
as a update to my previous message, it seems like the options PROTON_NO_ESYNC=1
and PROTON_NO_FSYNC=1
sometimes enable the graphic problems to go away, but not always
screenshots:
update, i got a shot where it was working:
screenshots:
Note: the screenshots are in relatively the same place, also to note is that nothing was different between the 2 starts of the game, same in-game options, same proton, same wineprefix, same save-game, same system, even same starting command
also to note is that i run this game with gamescope most of the time, to fix it starting on the wrong display and not showing that displays resolution, but the same problems exist even when not using gamescope
game scope command i use: gamescope -w 2560 -h 1440 -r 60 -f -- %command%
Edit: just to clarify, when the game run and the graphics are working correctly after save load, then it will stay working for as long as the game runs until restarted, same applies for when the graphics dont work correctly
Edit2: also, i tested Proton 6.3 rc for -8
as a update to my last post, i played the game in the recent days since posting, and all starts after that day have been working graphically, with the command PROTON_NO_FSYNC=1 gamescope -w 2560 -h 1440 -r 60 -f -- %command%
, but i noticed that the game crashes sometimes on area transition
log of crash: <too big to upload anywhere, 1.5GB - how can i truncate it? - will append if i get a lower size crash>
PS: i had already played this game last year on the same machine, but different system (Linux Mint 20.1) and with proton 5,11.GE-2-MF
, which had no graphical issues or crashes
Without a reliable way to reproduce the graphical anomaly, there's no way for a graphics dev to ponder the previous quirk.
Without a reliable way to reproduce the graphical anomaly, there's no way for a graphics dev to ponder the previous quirk.
the command was with PROTON_NO_FSYNC=1
, without it it would still happen
also, how could i truncate a proton log to be able to upload it here?
Update: tested it again, and yes when having PROTON_NO_FSYNC
unset or set to =0
, the graphical issues appear always (from my ~5 test starts) and with it being set to =1
currently, it does not happen much anymore (like 1 out of 5 starts have this issue with it set)
i also tested with Proton 6.3-8(-rc4), which behaves the same as 6.3-7 which i used for the previous posts
just tested with Proton 6.3-8-rc5
, where the graphical issues always happen, even when PROTON_NO_FSYNC=1
was set (~5 tries with and without) and with this release, the proton log is full of the following and ~250mb just by starting the game and loading a save file
# snippet from the log file
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 8 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x31314452
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x0000003c
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000018
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000020
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000028
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000024
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x0000000c
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000008
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000008
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 2 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 1 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown Skipping 3 unknown DWORDs:
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:skip_dword_unknown 0x00000000
5423.955:011c:01e0:fixme:d3dcompiler:d3dcompiler_shader_reflection_GetDesc iface 000000000E110250, desc 000000000E06F440 partial stub!
this above (varying numbers in Skipping 3 unknown DWORDs
) makes up about ~90% of the ~250mb file
Update: it seems like i need to restart my machine every time i update proton for a version to work (at least rc releases), because now (again) version Proton 6.3-8-rc5
suddenly works sometimes without any extra arguments (aside from PROTON_LOG=1
)
as a update, today i updated to latest manjaro (which just released today/yesterday) its either 21.1.7 or 21.2 (no downloads are up currently, so i dont know) and proton 6.3-8-rc7
, where everything runs stable, at least in my ~5 hours of today's playtime (no graphical issues or crashes) without any extra arguments
DualSense gamepad is not working (with and without Steam Input). However it works with Steam Input disabled on old Proton-7.2-GE-2.
Compatibility Report
System Information
I confirm:
steam-840720.log
Symptoms
Game fails to launch; Steam briefly shows it as Running, but then closes shortly after, with no game windows appearing.
Reproduction
Install, click Play