Forts (410900)

[DenisBY]

See screenshot: https://i.imgur.com/2c2n3VZ.png My sysinfo Maybe related to issue https://github.com/ValveSoftware/steam-for-linux/issues/5644 because during checking files integrity in Steam it downloads 0 bytes

[ElricleNecro]

I am also having this issue, after a few minutes of playing a game. My sysinfo.

[kisak-valve]

Forts using vulkan renders everything transparent and dark

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7362. @tristanjl posted on 2023-12-19T00:19:32:

Compatibility Report

• Name of the game with compatibility issues: Forts
• Steam AppID of the game: 410900

System Information

• GPU: AMD 6800XT (Also occurs on steam deck. Does not occur Linux Mint with RX580)
• Video driver version: Mesa 23.3.0
• Kernel version: 6.6.6-200.fc39.x86_64
• Link to full system information report as Gist: https://gist.github.com/tristanjl/532ae312c789750630d0eeb5001470a9
• Proton version: Tested Experimental, 8.0-4, 7.0-6

I confirm:

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

steam-410900.log

Symptoms

When vulkan rendering is enabled, everything in the game looks darker and transparent When captured in render doc, the output pixel value is approximately 1/4 the alpha is should be. Due to blend modes, this is then multiplied through the colour, hence why everything looks dark When debugging the shader in render doc, the pixel value result appears to be the correct value - but it does not match the actual pixel value. In testing a debug build, it renders correctly run from wine directly (including wine used by proton). It also appears correct when disabling Vulkan (which uses OpenGL)

Reproduction

Go to Options -> Video Ensure 'Enable Vulkan' is checked Restart the game Notice that everything appears transparent and darker

[tristanjl]

Also, I have encountered 2 crashes calling steamworks api functions when running under proton (no issue under windows)

This happens with multiplayer - when you host a lobby and then either:

Quit hosting - application exits on SteamGameServer_Shutdown() Player joins the game - application exits on SteamGameServerNetworking()->AcceptP2PSessionWithUser( pCallback->m_steamIDRemote );