Closed s1LenT0R closed 1 year ago
Hello @SOFACHILLAX, the Vulkan driver for the Haswell generation of Intel graphics is not spec compliant, which makes your system unsupported by Proton in general, but ignoring that, you've described an issue with Pressure Vessel setting up the Steam Linux Runtime - Soldier container environment that Proton runs inside instead of Proton itself.
Please give https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information a read and share the requested information.
VERSIONS.txt slr-app23310-t20230309T152549.log steam-23310.log
I think the "No such file or directory" here is probably about a dependency of crocus_dri.so
, rather than crocus_dri.so
itself. Error messages from low-level stuff like that are often quite misleading.
If you get another log similar to slr-app23310-t20230309T152549.log
, but also adding STEAM_LINUX_RUNTIME_VERBOSE=1
to the environment, that should give us some more clues (you should get a larger log, with debug-level lines containing D:
).
Also, please take a look at the actual files on the host system /usr/lib/dri/crocus_dri.so
and /usr/lib64/dri/crocus_dri.so
with:
objdump -Tx /usr/lib64/dri/crocus_dri.so | grep NEEDED
objdump -Tx /usr/lib/dri/crocus_dri.so | grep NEEDED
so that we can have a clearer idea of what dependencies they have.
In future please put large logs and similar large amounts of information in an attached text file or a gist to make it easier to read this issue!
(@kisak-valve, please could you use your admin powers to put the wall of text in https://github.com/ValveSoftware/steam-runtime/issues/573#issuecomment-1462182637 into a <summary>
?)
objdump -Tx /lib*/dri/crocus_dri.so | grep NEEDED NEEDED libglapi.so.0 NEEDED libdrm.so.2 NEEDED libLLVM-15.so NEEDED libexpat.so.1 NEEDED libz.so.1 NEEDED libzstd.so.1 NEEDED libsensors.so.5 NEEDED libdrm_intel.so.1 NEEDED libstdc++.so.6 NEEDED libm.so.6 NEEDED libgcc_s.so.1 NEEDED libc.so.6 NEEDED libglapi.so.0 NEEDED libdrm.so.2 NEEDED libLLVM-15.so NEEDED libexpat.so.1 NEEDED libz.so.1 NEEDED libzstd.so.1 NEEDED libsensors.so.5 NEEDED libdrm_intel.so.1 NEEDED libstdc++.so.6 NEEDED libm.so.6 NEEDED libgcc_s.so.1 NEEDED libc.so.6
It's interesting that the dependencies you list don't include libelf.so.1
. I wonder whether this means you're hitting essentially the same bug as #562?
Please could you try the client_beta
branch of "Steam Linux Runtime - soldier", which contains a fix for that issue?
If the beta branch doesn't solve this, we'll need to look at a log with STEAM_LINUX_RUNTIME_VERBOSE=1
: the ordinary log doesn't capture enough detail to understand this particular problem.
the game launched and ran without crashing, gamepad input worked straight up but i experienced heavy graphical glitches even on minimum graphics settings of which two are pretty game breaking. but i guess this is too much to ask for unless you know your way around graphics stacks and stuff...
Glad to hear it started for you.
As initially noted, your hardware is not supported by Proton in general, but if you're able to confirm that the game behaves with newer hardware, then it might be interesting for you to follow up with your video driver vendor regarding graphical artifacts.
In general, graphical artifacts and/or crashes are expected with your generation of Intel hardware.
the game launched and ran without crashing
From the Steam Runtime point of view I think this must have been the same root cause as #562, then.
In general, graphical artifacts and/or crashes are expected with your generation of Intel hardware.
any way to circumvent this through proton launch parameters to change/tweak the rendering stack eventually? sorry but i don't know a lot about all these wrapper things (the game uses directx 9.0c)
You might get lucky setting the game's launch options to PROTON_USE_WINED3D=1 %command%
to tell Proton to use Wine's DirectX to OpenGL render path, but that launch option comes with a significant performance penalty and is not considered supported by Proton. Any rendering issues with that launch option would need to be reproduced with vanilla wine and reported to the upstream wine project (and maybe your video driver vendor as well).
You might get lucky setting the game's launch options to
PROTON_USE_WINED3D=1 %command%
to tell Proton to use Wine's DirectX to OpenGL render path, but that launch option comes with a significant performance penalty and is not considered supported by Proton. Any rendering issues with that launch option would need to be reproduced with vanilla wine and reported to the upstream wine project (and maybe your video driver vendor as well).
yeah i got lucky, performance is similar compared to vulkan on this machine and the game is playable. thanks a lot for your help!
proton log excerpt:
proton experimental, gpu is Intel(R) HD Graphics 4400 (HSW GT2) mesa version 22.2.5 on kernel 6.1.12-gentoo-dist
crocus_dri.so is natively present in both 32 and 64 bit variants on my system, steam runtime doesn't seem to find it tho.