Skip to content

The problem with the proton experimental and/or proton hotfix #8651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NorfLoud opened this issue May 3, 2025 · 7 comments
Open

The problem with the proton experimental and/or proton hotfix #8651

NorfLoud opened this issue May 3, 2025 · 7 comments

Comments

@NorfLoud
Copy link

NorfLoud commented May 3, 2025

Your system information

  • Steam client version (build number or date): 1745876290
  • Distribution (e.g. Ubuntu): Alt Workstation K 10.4
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs:

steam-logs.tar.gz

  • GPU: AMD Radeon RX 6700 XT

Please describe your issue in as much detail as possible:

Games that used to run without compatibility mode have stopped running. I noticed on May 3rd that this problem is widespread with my games.
I purchased the Spartan game on May 1, installed it and launched it, it worked, but could this game somehow affect the settings of the entire steam and proton?

Steps for reproducing this issue:

  1. When I start the game without forced compatibility mode, I get an error message:
Failed to initialize graphics.
Make sure you have DirectX 11 installed, have up to date
drivers for your graphics card and have not disabled
3D acceleration in display settings.
InitializeEngineGraphics failed

or

Failed to create the D3D9 Device! This can happen if the desktop is locked. Exiting...

I get the same error message if I use forced compatibility mode "proton experimental" or "proton hotfix".
2. If you try to run protontricks, there will be no icons for the games, and when you try to open the prefix of the game, you will receive an error message:

Protontricks was closed due to the following error:

Traceback (most recent call last):
  File "/usr/lib/python3/site-packages/protontricks/cli/util.py", line 159, in wrapper
    return cli_func(self, *args, **kwargs)
  File "/usr/lib/python3/site-packages/protontricks/cli/main.py", line 277, in main
    proton_app = find_proton_app(
  File "/usr/lib/python3/site-packages/protontricks/steam.py", line 848, in find_proton_app
    tool_app = find_steam_compat_tool_app(
  File "/usr/lib/python3/site-packages/protontricks/steam.py", line 609, in find_steam_compat_tool_app
    appinfo_sections = [
  File "/usr/lib/python3/site-packages/protontricks/steam.py", line 609, in <listcomp>
    appinfo_sections = [
  File "/usr/lib/python3/site-packages/protontricks/steam.py", line 531, in iter_appinfo_sections
    raise SyntaxError(
SyntaxError: Invalid file magic number. The appinfo.vdf version might not be supported by the current version of Protontricks - please check for updates.


=============

Please include this entire error message when making a bug report.
Log messages:

Found Steam directory at /home/user/.local/share/Steam
Using default Steam Runtime at /home/user/.local/share/Steam/ubuntu12_32/steam-runtime
WINETRICKS environment variable is not available. Searching from $PATH.
Found 1 Steam library folders
Currently logged-in Steam user: <user_name>
Found 1 Steam shortcuts running using Steam compatibility tools
Using 'yad' as GUI provider

The solution that I found:

Use forced compatibility mode GE-Proton8-32 or GE-Proton8-20. With this mode, the games start.

@kisak-valve kisak-valve transferred this issue from ValveSoftware/steam-for-linux May 3, 2025
@nocs13
Copy link

nocs13 commented May 3, 2025

I also have issue relate to Proton experimental and hostfix. I not sure that it related but i cannot open new issue so i drop here screenshot. I suspect that proton use wine predefined as WIndows XP, which is incompatible to directx11.

this issue appeared after 30 Apr. Before I was able play without issue.

Image

@JHDude
Copy link

JHDude commented May 3, 2025

I would like to mention that I also have this issue, and provide a little more information. The problem seems to be most likely to occur with Unreal Engine games, at least for me. Coral Island, Void Crew, and R.E.P.O. are all non-functional with the error message shown above about DirectX unless run with Proton 8. I have not had time to check further titles.

@NorfLoud
Copy link
Author

NorfLoud commented May 3, 2025

I tried running different games and made a new archive with logs:
steam-logs-2.tar.gz
Something started, something didn't.

@NorfLoud
Copy link
Author

NorfLoud commented May 3, 2025

I would like to mention that I also have this issue, and provide a little more information. The problem seems to be most likely to occur with Unreal Engine games, at least for me. Coral Island, Void Crew, and R.E.P.O. are all non-functional with the error message shown above about DirectX unless run with Proton 8. I have not had time to check further titles.

I didn't have any problems with the UE game (robocop rogue city). There were problems with games on other unknown engines and with the game on unity.
Specifically, which version of proton did you manage to launch the games with?

@NorfLoud
Copy link
Author

NorfLoud commented May 3, 2025

I also have issue relate to Proton experimental and hostfix. I not sure that it related but i cannot open new issue so i drop here screenshot. I suspect that proton use wine predefined as WIndows XP, which is incompatible to directx11.

this issue appeared after 30 Apr. Before I was able play without issue.

As far as I know, steam uses a modified valve version of wine, and it's called proton. They're working on it.
Have you tried running your game with forced compatibility mode?
For example with Proton 8.0-5? Alternatively, use the ProtonUp-Qt utility to add other versions of proton, for example, try GE-Proton8-32.

@imbrianj
Copy link

imbrianj commented May 3, 2025

Kingdom Come Deliverance 2 (CryEngine) worked Thursday, black-screen or only splash screen Friday. Tried Proton Experimental, GE, 9, 8 - none seem to work - most failing either at the splash screen or before the Warhorse video logo at a black fullscreen with game cursor. If I clear all caches, I can get to the EULA screen with game background sounds, but hitting "E" to agree to terms, the game locks and sounds stop.

Debian Trixie
Gnome / Wayland
AMD Ryzen 9 7950X3D
AMD Radeon RX 7900 XTX
Proton 9.0 Build ID: 17797868

Edit: my issue was with Mesa 25.0.4. Downgrading to 25.0.3 solved the issue for me.

@JHDude
Copy link

JHDude commented May 3, 2025

I would like to mention that I also have this issue, and provide a little more information. The problem seems to be most likely to occur with Unreal Engine games, at least for me. Coral Island, Void Crew, and R.E.P.O. are all non-functional with the error message shown above about DirectX unless run with Proton 8. I have not had time to check further titles.

I didn't have any problems with the UE game (robocop rogue city). There were problems with games on other unknown engines and with the game on unity. Specifically, which version of proton did you manage to launch the games with?

I went with Proton 8.0-5 via the "Force the use of a specific Steam Play compatibility tool" setting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants