protonscr

Games do not start with proton versions higher than 3.16

protonopen
ValveSoftware/Proton#6894 · opened 2023-06-29 by al98murru · updated 2023-06-30 · 3 comments · github
Aal98murru 2023-06-29 github

Compatibility Report

  • Name of the game with compatibility issues: every game (tested on: Elder Scrolls 3 Morrowind)
  • Steam AppID of the game: every id (tested on:22320)

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.

Symptoms

No game starts (at most the launcher in morrowind is displayed), when I try to use a version of proton higher than 3.16.

Checking all the logs I get this error:

"
8663.763:0184:0188:err:wgl:X11DRV_WineGL_InitOpenglInfo couldn't initialize OpenGL, expect problems
8663.763:0184:0188:err:d3d:wined3d_caps_gl_ctx_create Failed to find a suitable pixel format.
8663.765:0184:0188:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 01193210.
"

Kkisak-valve maintainer 2023-06-29 github

Hello @al98murru, sorry, but Proton generally expects that you have a Vulkan capable GPU, and the video driver for Intel Sandy Bridge generation doesn't provide that. Most games will fail due to a lack of hardware features and it's likely your hardware is unsupportable.

Setting that aside, you're using mesa/crocus from newer mesa, not mesa (amber) / i965 userspace driver. There's a chance this is a video driver sided issue.

Aal98murru 2023-06-29 github

Hi @kisak-valve. I globally disabled vulkan from all versions of proton installed on the PC from the "user_preferences.py" file, ergo the absence of vulkan is not the problem. It worked wonders until the 23.1 version of "mesa" came out which gave this problem on every game (steam or not). By switching to Mesa-Amber, I managed to curb the problem for wine games but strangely not for proton ones (except versions 3.16 and below).

Ssimifor 2023-06-30 github

if the problem came with a driver update and was affecting things outside proton I think you should report it to mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/issues

Nothing extracted yet.