Upon starting no man sky under wine (no man sky need OGL4.5 ) ingame only a white screen is displayed
those errors are displayed multiple times Mesa: User error: GL_INVALID_ENUM in glDrawElements(mode=ffffffff) Mesa: User error: GL_INVALID_ENUM in glDrawElementsInstanced(mode=ffffffff)
Game use OpenGL compat profile 4.5. Mesa support maximum 3.0 and no plans to up.
i have noticed this on mesa git 4.5 Mesa 17.2.0-devel (git-d5a9608) it states compatibility profile 4.5 Still no mans sky doest work under wine staging
(In reply to Giovanni ongaro from comment #4) > i have noticed this on mesa git > 4.5 Mesa 17.2.0-devel (git-d5a9608) > it states compatibility profile 4.5 > Still no mans sky doest work under wine staging Until recently the highest compat profile Mesa drivers supported was 3.0. radeonsi now supports 3.1. 4.5 would be referring to the core profile. You can run "glxinfo | grep OpenGL" to see what your driver supports. Anyway Wine has now switched to using Core profile for Mesa drivers so it's possible the game will now work better. Either way 4.5 compat profile is a known missing feature rather than a bug so I'm going to close this bug for now.
Notice that No Man's Sky is an OpenGL game so Wine should have no effect on the game requiring compatibility profile or not.
(In reply to Matteo Bruni from comment #6) > Notice that No Man's Sky is an OpenGL game so Wine should have no effect on > the game requiring compatibility profile or not. In that case the game using compat profile is the problem i.e. a known missing feature in Mesa rather than a bug. There are plans to start adding support to radeonsi but it's still a little while off.
Created attachment 138835 [details] No Mans sky in wine 3.6 (RX570) using MESA_GL_VERSION_OVERRIDE=4.5COMPAT Menu and load screen are working fine, but game play actually looks like that.
I tested no man sky on wine staging 3.6 and it seems to works!
using MESA_GL_VERSION_OVERRIDE=4.5COMPAT
(In reply to freedesktop from comment #8) > Created attachment 138835 [details] > No Mans sky in wine 3.6 (RX570) using MESA_GL_VERSION_OVERRIDE=4.5COMPAT > Menu and load screen are working fine, but game play actually looks like > that. Do you think you can get and apitrace [1] of this issue and upload share it from google drive or somewhere like that. [1] https://github.com/apitrace/apitrace/wiki/Steam
(In reply to Timothy Arceri from comment #11) > (In reply to freedesktop from comment #8) > > Do you think you can get and apitrace [1] of this issue and upload share it > from google drive or somewhere like that. > > [1] https://github.com/apitrace/apitrace/wiki/Steam I hope that's something you can work with. I haven't done that before. I run "wine apitrace.exe trace -a gl -v NMS.exe" inside my wineprefix. https://drive.google.com/open?id=1jC7JrN6yacNHKfbBAvoG2USI6L9qqFb7
(In reply to freedesktop from comment #12) > (In reply to Timothy Arceri from comment #11) > > (In reply to freedesktop from comment #8) > > > > Do you think you can get and apitrace [1] of this issue and upload share it > > from google drive or somewhere like that. > > > > [1] https://github.com/apitrace/apitrace/wiki/Steam > > I hope that's something you can work with. I haven't done that before. I run > "wine apitrace.exe trace -a gl -v NMS.exe" inside my wineprefix. > > https://drive.google.com/open?id=1jC7JrN6yacNHKfbBAvoG2USI6L9qqFb7 The trace is complaining when I try to run it in compat. "error: context mismatch: expected OpenGL 4.4 core, but got OpenGL 4.5 compat" You probably need to capture it with these set also: MESA_GL_VERSION_OVERRIDE=4.5COMPAT MESA_GLSL_VERSION_OVERRIDE=450 I noticed above you didn't try with the GLSL override you might want give that a go before making a new trace.
(In reply to Timothy Arceri from comment #13) > The trace is complaining when I try to run it in compat. > > "error: context mismatch: expected OpenGL 4.4 core, but got OpenGL 4.5 > compat" > > You probably need to capture it with these set also: > > MESA_GL_VERSION_OVERRIDE=4.5COMPAT MESA_GLSL_VERSION_OVERRIDE=450 > > I noticed above you didn't try with the GLSL override you might want give > that a go before making a new trace. Oh sorry, I just forgot to set GLSL when I run the trace. A new trace, both overrides where set now https://drive.google.com/open?id=1v9aBmPWPGNrBiBDu5VW7MczpsDR4cbs6
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.