Bug 100629 - No mans sky renders white screen under wine in linux
Summary: No mans sky renders white screen under wine in linux
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-09 14:11 UTC by Giovanni ongaro
Modified: 2018-04-19 11:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
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. (5.45 MB, image/png)
2018-04-14 12:49 UTC, freedesktop
Details

Description Giovanni ongaro 2017-04-09 14:11:03 UTC

    
Comment 1 Giovanni ongaro 2017-04-09 14:12:33 UTC
Upon starting no man  sky under wine (no man sky  need OGL4.5 ) ingame only a white screen is displayed
Comment 2 Giovanni ongaro 2017-04-09 14:52:54 UTC
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)
Comment 3 Vladimir Usikov 2017-05-01 05:40:11 UTC
Game use OpenGL compat profile 4.5. Mesa support maximum 3.0 and no plans to up.
Comment 4 Giovanni ongaro 2017-06-17 03:46:20 UTC
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
Comment 5 Timothy Arceri 2018-04-12 22:56:08 UTC
(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.
Comment 6 Matteo Bruni 2018-04-13 17:52:01 UTC
Notice that No Man's Sky is an OpenGL game so Wine should have no effect on the game requiring compatibility profile or not.
Comment 7 Timothy Arceri 2018-04-14 00:12:40 UTC
(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.
Comment 8 freedesktop 2018-04-14 12:49:32 UTC
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.
Comment 9 Giovanni ongaro 2018-04-15 00:48:46 UTC
I tested no man sky on wine staging 3.6 and it seems to works!
Comment 10 Giovanni ongaro 2018-04-15 00:49:24 UTC
using MESA_GL_VERSION_OVERRIDE=4.5COMPAT
Comment 11 Timothy Arceri 2018-04-15 02:07:20 UTC
(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
Comment 12 freedesktop 2018-04-19 00:33:05 UTC
(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
Comment 13 Timothy Arceri 2018-04-19 01:55:50 UTC
(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.
Comment 14 freedesktop 2018-04-19 11:45:46 UTC
(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.