protonscr

GOALS

protonclosed appid 2753000Game compatibility - Unofficial
ValveSoftware/Proton#9872 · opened 2026-06-13 by clem691 · updated 2026-07-17 · 2 comments · github · game page · search this game
Cclem691 2026-06-13 github

Compatibility Report

  • Name of the game with compatibility issues: GOALS
  • Steam AppID of the game: 2753000

System Information

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-2753000.zip

Symptoms

i launch the game "GOALS" in low end mode and i just get a black screen forever (high end worked but my gpu is too old for it

Reproduction

just launch the game with recent proton versions and see that the "low-end" option will just load the game and get a black sreen right after the loading screen

Jjhonsnake 2026-07-17 github

Adding an NVIDIA RTX 50-series data point with a full root-cause analysis, since this reproduces differently than the Intel/low-end report above.

Symptom

Launcher updates → launches Game.exe (UE 5.7.4) → black screen, process hangs forever (has to be killed). UE5 initializes fine; it dies during PSO precompilation.

Root-cause chain (from PROTON_LOG=1 VKD3D_DEBUG=warn)

vkd3d-proton: vkd3d_validate_vertex_input_signature: No input layout element found for VS input semantic ATTRIBUTE1.
LogD3D12RHI: Error: Failed to create pipeline state with combined hash 60DF58866BAF86FE, error 80070057.   (E_INVALIDARG)
seh: Exception 0xc0000005    (inside Goals.exe, immediately after the failed CreatePipelineState)
err:sync:RtlpWaitForCriticalSection "loader.c: loader_section" wait timed out ... (dozens of threads, 60s loops)

So there are actually two problems stacked:

  1. vkd3d-proton / NVIDIA: CreateGraphicsPipelineState returns E_INVALIDARG for a vertex shader whose input signature references ATTRIBUTE1 with no matching input-layout element. Native D3D12 on Windows and RADV/AMD accept this (the game runs fine on Steam Deck); only NVIDIA + vkd3d-proton reject it. The failing thread is UE5 PSOPrecompilePool #0.
  2. Game bug: GOALS dereferences the null ID3D12PipelineState on failure → 0xc0000005, and the crash happens while the Wine loader lock is held, so everything deadlocks on loader_section and the process hangs on black instead of exiting.

Notes

  • With GE-Proton11 (older vkd3d) 4 PSOs failed with this exact error; with Proton Experimental (vkd3d-proton 3.1.0, build 3dfc6f07d0953b1) only 1 still fails — recent vkd3d already fixed most of them, one remains.
  • Not quality-dependent: the game's launcher forces low quality after each crash (-GoalsForceQualityLevel=0) via its reliability system; the failing PSO reproduces at every quality level, forced-low or default.
  • Ruled out as cause: super-ultrawide 5120×1440, gamescope, NVIDIA Streamline/DLSS-G (disabling the interposer doesn't change it), UE5 PSO-precache cvars (the game re-forces them on).

System

  • GPU: NVIDIA GeForce RTX 5080 (GB203, DeviceId 0x2c02)
  • Driver: 610.43.03 (nvidia-open)
  • OS: CachyOS, kernel 7.1.3-2 (linux-cachyos-nvidia-open), KDE Plasma / Wayland
  • Proton: Experimental — vkd3d-proton 3.1.0 (3dfc6f07d0953b1)
  • Engine: Unreal Engine 5.7.4, D3D12 RHI, FL 12_2, Shader Model 6.7

Full PROTON_LOG=1 VKD3D_DEBUG=warn log available on request. This is very likely best tracked upstream in vkd3d-proton (VS input-signature validation returning E_INVALIDARG on NVIDIA where RADV/native accept it).

Cclem691 2026-07-17 github

Replying to https://github.com/ValveSoftware/Proton/issues/9872#issuecomment-5005829764

hello and thank you for the share, first i didn't see on the front page of the game that they DIDN'T supported proton 11 YET but they were working on it so i think there is our response !

Proton versions

Launch options

Error codes