Proton icon indicating copy to clipboard operation
Proton copied to clipboard

The Hurricane of the Varstray -Collateral hazard- (416380)

Open ryliejamesthomas opened this issue 4 years ago • 5 comments

Compatibility Report

  • Name of the game with compatibility issues: The Hurricane of the Varstray -Collateral hazard-
  • Steam AppID of the game: 416380

System Information

  • GPU: RX 570
  • Driver/LLVM version: Mesa 21.1.4
  • Kernel version: 5.12.15-arch1-1
  • Link to full system information report as Gist: https://gist.github.com/ryliejamesthomas/c0befc162b953a6bd888038d5a363057
  • Proton version: 6.3-5

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

steam-416380.log

Symptoms

Game launches, seems to work fine (get audio, keyboard input works) apart from the screen being completely black.

Same issue is experienced by every Linux user I can find.

ryliejamesthomas avatar Jul 16 '21 19:07 ryliejamesthomas

Game now stops and closes as soon as it launches.

ryliejamesthomas avatar Jul 16 '23 06:07 ryliejamesthomas

Can't open the game on OLED deck with latest Experimental build. steam-416380.log

Launching it with PROTON_USE_WINED3D=1 %command% makes this pop up before crashing, dunno if it's a game problem or a dxvk and wined3d problem.

download

Update: Can replicate op behavior by downgrading to proton 5.13-6, 6.3-8 crashes silently on my end, so it seems like the regression happened between 6.3-5 and 6.3-8

waspennator avatar Feb 15 '24 04:02 waspennator

Followup: If you use Protontricks to install d3dx11_42, not only does it stop the crashing, but also finally gets the screen rendering.

download (1) steam-416380.log.txt

waspennator avatar Feb 15 '24 15:02 waspennator

Extra follow up doing a comparison between logs, curious if these 2 messages in the first log (Running with protons built in d3dx11_42 file) mean something since they doesn't show up if you use protontricks to install d3dx11_42.

706.550:0130:0134:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 00606748, src_data_size 132, pump 00000000, img_info 20F7F54C, hresult 00000000 stub! 706.550:0130:0134:fixme:d3dx:D3DX11CreateTextureFromMemory device 229C0E28, data 00606748, data_size 132, load_info 20F7F578, pump 00000000, texture 20F7F540, hresult 00000000 stub.

waspennator avatar Feb 16 '24 17:02 waspennator

Update, problem seems to be resolved with proton Experimental, game seems to load up and work ingame now.

waspennator avatar Oct 23 '24 05:10 waspennator

Thanks for the update. Did a quick test and played through five stages with no problems, also using experimental.

ryliejamesthomas avatar Oct 24 '24 06:10 ryliejamesthomas

Apparently the game seems to run at the monitors refresh rate if you play it in windowed mode (on my oled deck it runs at 90 fps), if I set it to full-screen it runs at 60 capped.

The problem is fixed in windowed mode if i set "DXVK_FRAME_RATE=60 %command%" as a command and I dont notice any framepacing problems with it in windowed or fullscreen mode, pcgamingwiki also says the game is supposed to run at 60 fps by default, so maybe it needs a dxvk cap.

waspennator avatar Dec 30 '24 21:12 waspennator