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: Sat, 25 Aug 2018 17:17:55 +0000 [thread overview]
Message-ID: <bug-107581-502-iPuzO1walQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107581-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1824 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107581
Matthew Vaughn <nethershaw@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nethershaw@gmail.com
--- Comment #17 from Matthew Vaughn <nethershaw@gmail.com> ---
I've been following this issue since it was reported and I would like to
contribute if I can. Since the bug status is currently "NEEDINFO" I will
endeavor to provide corroborating details and offer my platform for
investigation and testing.
I can begin by validating everything discussed in the comments so far. The
issue presents itself on my platform exactly as Benjamin documented. My
platform only differs slightly:
OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.26.0, 4.18.4-gentoo, LLVM
6.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-rc4
The patches Timothy provided apply and build perfectly, and with the suggested
environment variables set while running NMS I can also exactly reproduce
Benjamin's result. World assets render correctly; the game is playable; the
galaxy map "clouds" are not visible; there appear to be significant artifacts
in the semi-transparent background textures of most UI elements (conversation
dialogs and the tab menu).
My first attempt at reproducing the problem and using the proposed patches was
done on Mesa 18.2.0-rc4 built from source, but I have no problem in principle
with testing further against the current 18.3.0 development branch.
I am happy to test additional patches and gather any additional information
upon request. Thank you for starting the work.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3228 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
next prev parent reply other threads:[~2018-08-25 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 12:46 [Bug 107581] Graphics Not Rendered Due to Missing 4.5 COMPAT Profile bugzilla-daemon
2018-08-15 12:55 ` 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 [this message]
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-iPuzO1walQ@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).