So apparently this game works great by forcibly installing DXSETUP.exe
Type the following in the terminal ... change USERNAME to your username
WINEPREFIX=/home/USERNAME/.steam/steam/steamapps/steamapps/compatdata/213330/pfx wine "/home/USERNAME/.steam/steam/steamapps/common/LEGO Batman 2/Support/DirectX/DXSETUP.exe"
Name of the game with compatibility issues: Lego Batman 2
Steam AppID of the game: 213330
GPU: RX 6700XT
Driver/LLVM version: Mesa 23.04-3
Kernel version: 4.15.0-38-generic
Link to full system information report: https://gist.github.com/coreybruce/3a7dd24ead8b58d8b85b4f94f5906a58
Proton version: Proton 8.0-3 and proton Experimental
Graphical glitches on certain objects and on the logo when you use Proton 8.0-3 and proton experimental
Only way to fix it was by using GE-proton-8.9
Hello @coreybruce, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the misrendering, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Hello @coreybruce, please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the misrendering, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Certainly
Here is the log: https://gist.github.com/coreybruce/6417a04c5a4324ae42414c296c6d06fc
Is it missing gstreamer? because I noticed a gstreamer folder in the root folder of the prefix after I used GE-proton
Thanks, these look like some lines of interest from the Proton log:
err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
err:d3dcompiler:D3DCompile2 Shader log:
err:d3dcompiler:D3DCompile2 <anonymous>:250:1: W4300: Redefinition of MOTION_BLUR_SAMPLES.
err:d3dcompiler:D3DCompile2 <anonymous>:931:16: E5005: Function "log2" is not defined.
err:d3dcompiler:D3DCompile2
vkd3d:fixme:hlsl_lexer_lex Unsupported preprocessor #pragma directive at line 260.
vkd3d:fixme:hlsl_lexer_lex Unsupported preprocessor #pragma directive at line 260.
Maybe helped by https://gitlab.winehq.org/wine/vkd3d/-/commit/49b63fbeba6d0665fa8ced7d2e2dd4376c98deb9 in vkd3d 1.8 upstream.
Replying to https://github.com/ValveSoftware/Proton/issues/1865#issuecomment-1657142206
I don't have the game to check, but looking at recent reports on protondb, the rainbow flashing textures still seem to occur even up to proton 8.0-4 unless you use protontricks with "d3dx9 d3compiler_47", one report says that fixes it on deck.
Update, picked up the game on sale and tried it on my oled le 1 tb deck with Proton Experimental, the rainbow seizure graphics are still occurring.
I can confirm this game has the same issue as Lego The Lord Of The Rings with Proton 9.0-3 and the same workaround applies.
Logs:
steam-213330-lego_batman2.tar.gz
Main error lines:
777.050:0128:0168:err:d3dcompiler:preprocess_shader Shader log:
777.050:0128:0168:err:d3dcompiler:preprocess_shader <anonymous>:250:1: W4300: Redefinition of MOTION_BLUR_SAMPLES.
777.050:0128:0168:err:d3dcompiler:preprocess_shader
777.063:0128:0164:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
777.063:0128:0164:err:d3dcompiler:D3DCompile2 Shader log:
777.063:0128:0164:err:d3dcompiler:D3DCompile2 <anonymous>:2620:8: E5005: Function "tex2Dlod" is not defined.
777.063:0128:0164:err:d3dcompiler:D3DCompile2
777.063:0128:0168:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
777.063:0128:0168:err:d3dcompiler:D3DCompile2 Shader log:
777.063:0128:0168:err:d3dcompiler:D3DCompile2 <anonymous>:250:1: W4300: Redefinition of MOTION_BLUR_SAMPLES.
777.063:0128:0168:err:d3dcompiler:D3DCompile2 <anonymous>:2622:8: E5005: Function "tex2Dlod" is not defined.
777.063:0128:0168:err:d3dcompiler:D3DCompile2
777.063:0128:016c:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
777.063:0128:016c:err:d3dcompiler:D3DCompile2 Shader log:
777.063:0128:016c:err:d3dcompiler:D3DCompile2 <anonymous>:2627:8: E5005: Function "tex2Dlod" is not defined.
777.063:0128:016c:err:d3dcompiler:D3DCompile2
Specs:
Hello @ranplayer, check how the game behaves with Proton Experimental. It should have a newer vkd3d subcomponent that includes https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/366.
@kisak-valve I've just retested it with Proton Experimental (2024-10-07), but unfortunately the issue remains. I'm attaching the updated logs:
steam-213330-exp.tar.gz
It did get further, some lines of interest:
err:d3dcompiler:D3DCompile2 <anonymous>:399:8: E5013: Invalid semantic 'TEXCOORD0_centroid'.
err:d3dcompiler:D3DCompile2 <anonymous>:400:8: E5013: Invalid semantic 'TEXCOORD1_centroid'.
err:d3dcompiler:D3DCompile2 <anonymous>:400:8: E5013: Invalid semantic 'TEXCOORD2_centroid'.
[...]
err:d3dcompiler:D3DCompile2 <anonymous>:1272:34: E5017: Aborting due to not yet implemented feature: SM1 non-float expression.
Same problem here
Ubuntu 24.04.1 LTS
Gigabyte Technology Co., Ltd. B550M DS3H
AMD Ryzen™ 5 4600G with Radeon™ Graphics × 12
Proton 9.0-3
On Steam Deck, it finally launches and runs, but random objects stuck to other objects are appearing here and there with the screen constantly flashing, making it unplayable.
Rainbow seizure glitches seem to be gone from my testing now, tested it a little bit and it seems like its alright on my oled deck
proton 9.0-3x2 2024-10proton experimentalx4 2024-10proton 8.0-4x1 2024-02proton 8.0-3x1 2023-07proton 8.9x1 2023-07PROTON_LOG=1x2 2023-07WINEPREFIX=/home/USERNAME/.steam/steam/steamapps/steamapps/compatdata/213330/pfxx1 2019-03
Compatibility Report
System Information
I confirm:
Symptoms:
Starting the game crashes to desktop immediately
Reproduction
Start the game
steam-213330.log