Edit: Check my comment on how I solved it. TL,DR: manually delete and reinstall the Steam Linux Runtimes

I got Forza Horizon 6 for my birthday a couple of days ago and beside some small audio issues it was working completely fine (1440p mostly high and ultra settings 60-70FPS) with GE-Proton11.1 and PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1

I’ve played it for nearly 9h already. Today the game is freezing at the first frame after the epilepsy and so on warnings.

I’ve tried different Proton Versions (Experimental, Hotfix, Official 10 and 11, GE 10 and 11), no launch args and some of the launch args that I found on ProtonDB, restarted the PC and verified the game files, all to no avail.

I’ve heard that the game was being difficult at launch, but it was working great, but now for some reason it doesn’t run anymore.

Maybe one of you wizards has some ideas, would be much appreciated.

Distro: Debian 13 with KDE

Specs:

Ryzen 3950X

64GB DDR4 3200

Asus Prime X570 Pro MB

Nvidia 2080 Super 8GB with latest 610.43 drivers (from Nvidias Repo, Not Debians)

  • ohshit604@sh.itjust.worksEnglish
    5·
    9 hours ago

    I see you got your answer but Forza Horizon 6 is stupid buggy on Linux, I had to install new drivers as well as add these launch options to my game and use ProtonGE10-26.

    VKD3D_CONFIG=skip_application_workarounds,descriptor_heap,avoid_image_buffer_aliasing %command%

    I didn’t bother with HDR as it breaks the Steam Overlay preventing custom profiles for the Steam Controller.

    https://www.protondb.com/app/2483190

    • dangrousperson@feddit.orgOPEnglish
      2·
      7 hours ago

      I tried those when I was troubleshooting, but didn’t need them at first. Really strange that it worked really well for 9h and then suddenly stopped, not sure how/what/why the runtimes got corrupted.

  • dangrousperson@feddit.orgOPEnglish
    15·
    12 hours ago

    This post in the Steam Community Forums helped me solve the issue:

    You want to manually delete the Steam Linux Runtimes and then reinstall them (probably only the latest, but I deleted all 4 of them)

    Enable show Tools in your Steam Library

    Search for runtime

    There were 4 of them installed 1.0 to 4.0

    Find the App IDs for each: right click -> properties -> updates tells you the App ID

    where ever you have your Steam games installed: for me this was ~/.steam/steam/steamapps/

    delete the corresponding appmanifest_{App-ID}.acf files

    in /steamapps/common/ delete the 4 SteamLinuxRuntime folders

    restart steam and redownload the 4 runtimes by searching for them in your library

    This fixed the issue for me

  • INeedMana@piefed.zipEspañol
    3·
    11 hours ago

    I know that it’s solved by now but I’d like to propose another approach to solving such issues

    1. Launch steam so instead of running the game it will start xterm
      https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#getting-a-shell-inside-the-container
    2. in the shell you might need to enable more debugging (Proton is just a fork of wine)
      https://gitlab.winehq.org/wine/wine/-/wikis/Debug-Channels
    3. run "$@" in the shell
    4. now you should have some output with errors that you can search internet for. Wine bug discussions will be best. At least you can find which lib/part of WINE is the error coming from and try to find solutions for the problems, not the game

    EDIT: apparently there’s also this