https://bugs.winehq.org/show_bug.cgi?id=41551
Bug ID: 41551 Summary: Homeworld Remastered: OpenGL failed to load Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: adonai@xaker.ru Distribution: ---
Created attachment 55883 --> https://bugs.winehq.org/attachment.cgi?id=55883 access violation with gl version 3.3
Homeworld Remastered hangs right after start with this line in logs: err:wgl:X11DRV_wglCreateContextAttribsARB Context creation failed (error 1)
When exporting MESA_GL_VERSION_OVERRIDE=3.3 game starts but I see Access Violation error a bit after (attaching dump for that).
Details: Archlinux
OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.2.0 / 4.7.6-1-ARCH, LLVM 3.8.1) OpenGL core profile version string: 4.1 (Core Profile) Mesa 12.0.3 OpenGL core profile shading language version string: 4.10 Resolution: 2560x1440, dpi 109, color depth 24 Desktop environment: KDE cmd exec line: wine HomeworldRM.exe -dlccampaign HW2Campaign.big -campaign Ascension -moviepath DataHW2Campaign -mod compatibility.big
https://bugs.winehq.org/show_bug.cgi?id=41551
Oleg Chernovskiy adonai@xaker.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adonai@xaker.ru
https://bugs.winehq.org/show_bug.cgi?id=41551
Behem0th grantipak@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |grantipak@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=41551
Ben Parsons 9parsonsb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |9parsonsb@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #1 from Oleg Chernovskiy adonai@xaker.ru --- Looks like the game requests OpenGL 3.3 Compatibility Profile. Took me 5 days of debugging with +relay,+wgl to get to this.
Alas Mesa supports only 3.0 compatibility profile, and decision not to increase it was accepted long ago.
If only there was something that can be done to circumvent this...
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #2 from Oleg Chernovskiy adonai@xaker.ru --- [EDIT]
As it turns out there is something that can be done.
Patch for WGL attributes: http://www.gearsongallium.com/?p=3599
https://bugs.winehq.org/show_bug.cgi?id=41551
Martin Dederer martin@martindederer.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |martin@martindederer.com
--- Comment #3 from Martin Dederer martin@martindederer.com --- (In reply to Oleg Chernovskiy from comment #2)
[EDIT]
As it turns out there is something that can be done.
Patch for WGL attributes: http://www.gearsongallium.com/?p=3599
Is this change going to be incorporated into wine?
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #4 from Oleg Chernovskiy adonai@xaker.ru --- (In reply to Martin Dederer from comment #3)
Is this change going to be incorporated into wine?
In fact, it advertises OpenGL Compatibility Profile where it shouldn't exist. This may raise some concerns.
This patch is part of a custom patchset by pontostroy. I don't know of their upstream status.
Can someone from wine team reply here?
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #5 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Oleg Chernovskiy from comment #4)
(In reply to Martin Dederer from comment #3)
Is this change going to be incorporated into wine?
In fact, it advertises OpenGL Compatibility Profile where it shouldn't exist. This may raise some concerns.
This patch is part of a custom patchset by pontostroy. I don't know of their upstream status.
Can someone from wine team reply here?
There isn't much to say here. Obviously we don't want that kind of hacks in Wine.
You can try to force Mesa to return a compatibility profile context with MESA_GL_VERSION_OVERRIDE=4.1COMPAT or something like that; more likely than not the game really requires GL compatibility features unsupported by Mesa and will thus crash.
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #6 from Martin Dederer martin@martindederer.com --- Thanks for the clarification. Homeworld Remastered does have stability issues (i.e. it crashes after a couple of minutes of gameplay) when hot wiring the respective function with pontostroy's patch.
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #7 from Oleg Chernovskiy adonai@xaker.ru --- (In reply to Matteo Bruni from comment #5)
There isn't much to say here. Obviously we don't want that kind of hacks in Wine.
You can try to force Mesa to return a compatibility profile context with MESA_GL_VERSION_OVERRIDE=4.1COMPAT or something like that; more likely than not the game really requires GL compatibility features unsupported by Mesa and will thus crash.
Just as I thought. Thanks for your reply.
Thanks for the clarification. Homeworld Remastered does have stability issues (i.e. it crashes after a couple of minutes of gameplay) when hot wiring the respective function with pontostroy's patch.
Strange, I don't experience this, what graphics card/kernel/mesa stack do you use? For me it was pretty stable with this patch.
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #8 from Martin Dederer martin@martindederer.com --- (In reply to Oleg Chernovskiy from comment #7)
(In reply to Matteo Bruni from comment #5)
There isn't much to say here. Obviously we don't want that kind of hacks in Wine.
You can try to force Mesa to return a compatibility profile context with MESA_GL_VERSION_OVERRIDE=4.1COMPAT or something like that; more likely than not the game really requires GL compatibility features unsupported by Mesa and will thus crash.
Just as I thought. Thanks for your reply.
Thanks for the clarification. Homeworld Remastered does have stability issues (i.e. it crashes after a couple of minutes of gameplay) when hot wiring the respective function with pontostroy's patch.
Strange, I don't experience this, what graphics card/kernel/mesa stack do you use? For me it was pretty stable with this patch.
I tried to reproduce the crashes i experienced back then to no avail.
These are the system details.
Graphics card: HD Graphics 400 (Celeron J3160) Kernel: Linux 4.4.0-64-generic x86_64 GNU/Linux Mesa stack:
$ glxinfo | grep OpenGLglxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Cherryview) OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 11.2.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 11.2.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions:
https://bugs.winehq.org/show_bug.cgi?id=41551
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins@gmail.com
--- Comment #9 from Linards linards.liepins@gmail.com --- Still present at wine-3.11 64-bit prefix; Fedora 28 x64
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #10 from Ben Parsons 9parsonsb@gmail.com --- (In reply to Linards from comment #9)
Still present at wine-3.11 64-bit prefix; Fedora 28 x64
What Graphics driver are you using? This might be fixed on recent mesa due to the recent improvements to COMPAT profiles by Valve
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #11 from Linards linards.liepins@gmail.com --- (In reply to Ben Parsons from comment #10)
(In reply to Linards from comment #9)
Still present at wine-3.11 64-bit prefix; Fedora 28 x64
What Graphics driver are you using? This might be fixed on recent mesa due to the recent improvements to COMPAT profiles by Valve
Hi Ben,
When enabling Vulkan and using Wayland session, I have GFX characteristics, found in attachments for Doom 2016 reported (https://bugs.winehq.org/show_bug.cgi?id=45451).
I assume it should be generally same for OpenGL and X.ORG.
Does not seems to have positive effect. Maybe there is some switch/extra config I am missing?
https://bugs.winehq.org/show_bug.cgi?id=41551
Oleg Chernovskiy adonai@xaker.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #12 from Oleg Chernovskiy adonai@xaker.ru --- Looks like it is finally resolved with Mesa 18.2.0 implementing Compatibility Profile 4.4.
I'll play a bit but so far everything is working. If something bad happens I'll reopen this.
https://bugs.winehq.org/show_bug.cgi?id=41551
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTOURBUG CC| |joseph.kucia@gmail.com
--- Comment #13 from Józef Kucia joseph.kucia@gmail.com --- Nothing was fixed in Wine.
https://bugs.winehq.org/show_bug.cgi?id=41551
--- Comment #14 from Ben Parsons 9parsonsb@gmail.com --- (In reply to Oleg Chernovskiy from comment #12)
Looks like it is finally resolved with Mesa 18.2.0 implementing Compatibility Profile 4.4.
I'll play a bit but so far everything is working. If something bad happens I'll reopen this.
Are you able to get the launcher to work?
https://bugs.winehq.org/show_bug.cgi?id=41551
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=41551
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #16 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
https://bugs.winehq.org/show_bug.cgi?id=41551
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Oleg Chernovskiy from comment #12)
Looks like it is finally resolved with Mesa 18.2.0 implementing Compatibility Profile 4.4.
I'll play a bit but so far everything is working. If something bad happens I'll reopen this.