From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101596] Blender renders black UI elements
Date: Wed, 05 Jul 2017 03:22:00 +0000 [thread overview]
Message-ID: <bug-101596-502-FWPeitWm79@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101596-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101596
--- Comment #4 from Matias N. Goldberg <dark_sylinc@yahoo.com.ar> ---
+1
I get this error too.
This bug is NOT https://bugs.freedesktop.org/show_bug.cgi?id=97059 which gets
fixed by either using DRI2 or selecting Triple Buffer in Blender.
This error started after I pulled latest git; and a faster way to reproduce it
is to simply click on the Materials pane; where automatically everything starts
going wrong within Blender.
I tried debugging the problem but came out short. My guess was either in the
vertex shader's key.clamp_color would become true for the same variant where it
used to be false, or that the same would happen in the pixel shader with
clamp_color/persample_shading/ati_fs/external (i.e. test if any of
st_fp_variant_key members changed but the same variant was being used).
However all shaders appear to be using consistent settings, which leaves me
puzzled.
As Sebastian Parborg, undoing the changes "st_update_fp" fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2059 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:[~2017-07-05 3:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 12:18 [Bug 101596] Blender renders black UI elements bugzilla-daemon
2017-06-26 12:19 ` bugzilla-daemon
2017-06-26 12:19 ` bugzilla-daemon
2017-06-26 12:21 ` bugzilla-daemon
2017-06-26 22:38 ` bugzilla-daemon
2017-07-05 3:22 ` bugzilla-daemon [this message]
2017-07-05 3:33 ` bugzilla-daemon
2017-07-05 3:36 ` bugzilla-daemon
2017-07-05 3:41 ` bugzilla-daemon
2017-07-05 17:05 ` bugzilla-daemon
2017-07-05 17:53 ` bugzilla-daemon
2017-07-06 0:59 ` bugzilla-daemon
2017-07-07 23:52 ` bugzilla-daemon
2017-07-08 2:41 ` 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-101596-502-FWPeitWm79@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).