People Playground (1118200)

[lukeatthatbruhmoment]

Game: *People Playground (Steam Game ID: 1118200) (*note, it happens with any game with vulcan shaders, hl1 and hl2 work fine, same as undertale)

Proton Version: proton-8.0-5d

System Information

• GPU: NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q]
• OS: Linux Mint 22.2 Cinnamon
• Kernel: Linux 6.14.0-33-generic
• Proton Log: Attached as steam-1118200.log

Symptoms
The game fails to launch instantly and crashes when using the wined3d launch option. The crash is related to the failure to initialize graphics drivers within the wined3d path. This is a specific crash for wined3d, as the game runs fine without it.

Reproduction

1. Set the Steam Play compatibility tool to Proton 8.0-5d.
2. Set the custom launch option to: forcelgadd %command% wined3d
3. Attempt to launch the game.
4. It crashes immediately.

Actual Error Messages from Log:

• The log file confirms the wined3d option is active: Options: {'forcelgadd', 'wined3d'}
• Failed to get adapters from xrandr: no driver could be loaded.
• err:wgl:X11DRV_WineGL_Init Failed to load 'wined3d.dll'

Something to say:
I removed wined3d from my launch options, it is still used, the launch option for some reason is forcelgadd %command% wined3d when actually it is PROTON_LOG=1

steam-1118200.log

[kisak-valve]

Hello @lukeatthatbruhmoment, so that it's clear, while it's sometimes useful for troubleshooting, using the PROTON_USE_WINED3D runtime option is not considered supported and any issues with that render path would need to be reproduced with upstream wine and reported to upstream wine. Your feedback here is a non-starter for a Proton dev.

If the Proton log has wined3d when you haven't set PROTON_USE_WINED3D=1 in Steam, then that would hint that you've set that environment variable elsewhere and it's bleeding into the game's environment. Until you figure out where that is, you can either unset the variable just before you start Steam or use PROTON_USE_WINED3D=0 %command% in the game's launch options.

The force large address aware runtime option has been enabled by default for some years and shouldn't be relevant to your troubleshooting.

as a side note you're mixing the runtime flags (forcelgadd and wined3d) with the environment variables that set the flags (PROTON_FORCE_LARGE_ADDRESS_AWARE and PROTON_USE_WINED3D). forcelgadd %command% wined3d isn't coherent and at best would do nothing.

[lukeatthatbruhmoment]

Hello @kisak-valve i cannot ever remember setting wined3d ever or forcelgadd, i dont think i ever did.
could you help me fix the vulcan issue though? whenever i boot up a game using vulcan no windows pop up and the game just crashes. i will generate a new log with PROTON_USE_WINED3D=0 soon. Edit: I have generated the new log and have linked it

steam-1118200.log

[kisak-valve]

Skimming your Proton log, something seems unhealthy before the game tries to use Vulkan.

Please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[lukeatthatbruhmoment]

@kisak-valve here is the gist

[kisak-valve]

https://gist.github.com/lukeatthatbruhmoment/978aa67a879c0ba768c4dc20024cee3a#file-gistfile1-txt-L97-L111 and https://gist.github.com/lukeatthatbruhmoment/978aa67a879c0ba768c4dc20024cee3a#file-gistfile1-txt-L302-L316 are the sections to focus on. That tells us that the Vulkan render paths are broken in general as you suspected.

Blind guess, does completely closing Steam, then running steam from a terminal have an effect? The environment variables being set at https://gist.github.com/lukeatthatbruhmoment/978aa67a879c0ba768c4dc20024cee3a#file-gistfile1-txt-L772 looks irregular.

[lukeatthatbruhmoment]

no, it does not have an effect, i always run steam from the terminal since whenever i type steam in my app explorer all that pops up is my games and "Install steam" but when i run steam from the terminal it works

[lukeatthatbruhmoment]

Update: I'm downloading a new linux distro called Nobara linux. Hope this will fix my problems and will come back for another update.

[lukeatthatbruhmoment]

Update: IT WORKED!