dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107581] Graphics Not Rendered Due to Missing 4.5 COMPAT Profile
Date: Wed, 15 Aug 2018 12:46:17 +0000	[thread overview]
Message-ID: <bug-107581-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1705 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107581

            Bug ID: 107581
           Summary: Graphics Not Rendered Due to Missing 4.5 COMPAT
                    Profile
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: ben@xnode.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 141109
  --> https://bugs.freedesktop.org/attachment.cgi?id=141109&action=edit
Lack of rendered image

Slightly obtuse issue as it's a game inside Wine.

No Man's Sky used to work if you faked a compatibility profile. This no-longer
works as, since the last game update, it seems they are actually using some of
the COMPAT mode features. The result of this is that the game menu renders
fine, but any of the "3D" graphics in the game are either missing or just
render completely white.

e.g. the starfield during loading should be various pinkish colours, but
instead you just see a black screen. Once in-game, you should see the game
world, but instead just have a (what seems to be non-refreshing) white screen.

The game seems to be fine on Nvidia cards using their proprietary driver.

Attached is an image of the issue to see specific what I'm referring to and a
trace, from launch of the game, to a few minutes in game, to exiting the game.
Generated with APITrace (I'll attach the trace in the next comment).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3210 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-08-15 12:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 12:46 bugzilla-daemon [this message]
2018-08-15 12:55 ` [Bug 107581] Graphics Not Rendered Due to Missing 4.5 COMPAT Profile bugzilla-daemon
2018-08-15 13:38 ` bugzilla-daemon
2018-08-15 13:40 ` bugzilla-daemon
2018-08-15 16:33 ` bugzilla-daemon
2018-08-20  5:18 ` bugzilla-daemon
2018-08-20  8:08 ` bugzilla-daemon
2018-08-21  2:10 ` bugzilla-daemon
2018-08-21  7:27 ` bugzilla-daemon
2018-08-21 10:52 ` bugzilla-daemon
2018-08-21 10:53 ` bugzilla-daemon
2018-08-21 11:13 ` bugzilla-daemon
2018-08-21 12:35 ` bugzilla-daemon
2018-08-21 12:49 ` bugzilla-daemon
2018-08-21 13:05 ` bugzilla-daemon
2018-08-22  1:30 ` bugzilla-daemon
2018-08-22  9:59 ` bugzilla-daemon
2018-08-25 17:17 ` bugzilla-daemon
2018-08-26  0:26 ` bugzilla-daemon
2018-08-26 14:01 ` bugzilla-daemon
2018-08-30  0:02 ` bugzilla-daemon
2018-09-06  2:33 ` bugzilla-daemon
2018-09-10 15:36 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107581-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).