ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.5k stars 1.07k forks source link

Just Cause 2 (8190) #670

Open stratus-ss opened 6 years ago

stratus-ss commented 6 years ago

Using Proton 3.7-4 Beta Just Cause 2 crashes on startup with Unhandled exception: privileged instruction in 32-bit code (0x00449000).

Logs: https://gist.github.com/stratus-ss/6aa9f13c36972cfd0868834d6bce7c50 System info gist: https://gist.github.com/stratus-ss/73e90ae7dcc42caf324190ea36e979cc

I am posting this one because I have seen this error in a few other games I have tried this past weekend. It seems to me there may be a common fix, but this is the game I have put the most time into overall

ranplayer commented 3 months ago

This game is currently not working with Proton Experimental (2024/07/31), 9.0-2 and 8.0-5. I've tried it on X11/Wayland with/without DXVK. When we add the d3dcompiler_47.dll (32bits) it at least shows the splash screen, but crashes after a few seconds.

Proton logs: steam-8190-just-cause.tar.gz

Main error lines (without d3dcompiler_47):

940.072:012c:0198:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
940.072:012c:0198:err:d3dcompiler:D3DCompile2 Shader log:
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:121: W5300: Implicit truncation of vector type.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:225: W5300: Implicit truncation of vector type.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:160: W5017: Loop unrolling is not implemented.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:243: E5002: Expected literal sample index.
940.072:012c:0198:err:d3dcompiler:D3DCompile2 

Main error lines (with d3dcompiler_47):

1617.865:0128:01dc:warn:seh:dispatch_exception EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised
1617.865:0128:01dc:trace:seh:dispatch_exception  eax=0b8cf5f4 ebx=00436390 ecx=00000000 edx=0b8cf608 esi=0b8cf680 edi=0b8cf610
1617.865:0128:01dc:trace:seh:dispatch_exception  ebp=0b8cf64c esp=0b8cf5f4 cs=0023 ss=002b ds=002b es=002b fs=0063 gs=006b flags=00000213
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7978BE60 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7978BE60 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 793AC410 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 793AC410 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7997CFB0 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7997CFB0 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7A20D310 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7A20D310 returned 0
1617.865:0128:01dc:trace:seh:call_stack_handlers calling handler at 00D91C90 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_stack_handlers handler at 00D91C90 returned 1
1617.865:0128:01dc:trace:seh:call_stack_handlers calling handler at 00D91C90 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_stack_handlers handler at 00D91C90 returned 0

Specs:

jessienab commented 3 months ago

@ranplayer have you tried clearing local stored shader cache? ~/.cache/mesa_shader_cache

(I am not a dev not Valve employee but just from the non replaced .dll error maybe that might work?)

Just mentioning as I launched today with 9.0-5 and 8.0-5 without issues... didn't try experimental. X11 with DXVK, same Arch Linux, kernel 6.6.40-lts, RX580, mesa 1:24.1.3-1, Ryzen 3700X. No custom launch options.

ranplayer commented 3 months ago

@jessienab unfortunately the same problem

simifor commented 3 months ago

just cause 2 uses ceg drm, you might need to verify game files for the game to start.

legluondunet commented 3 months ago

Just tested: 1) uninstall game/Reinstall game to test with a clean install 2) Game did not launch with Proton Experimental 3) install Ge-Proton9.11 from https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton9-11, the game launched OK

Then, once time I launch the game with Ge-Proton9.11, then I can launch it with Proton too

steam-8190.log

Config:

Manjaro 24.0.5 Wynsdey Kernel: x86_64 Linux 6.6.41-1-MANJARO Proc: AMD Ryzen 9 5900HX GPU: AMD Radeon RX 6600M Drivers: Mesa 24.1.3 Resolution: 1920x1080 32 Go RAM DE: Xfce4

waspennator commented 3 weeks ago

Tried testing again on my oled, but it got stuck on updating executable.

SeongGino commented 3 weeks ago

I did have an older prefix for JC2 installed before, which still works. But trying to make a prefix from scratch w/ GE9-16 seems to be a bust atm. I'll have to look later when I get some free time to see what's up with that.