From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97059] Tahiti+DRI3+Unity+Blender corruption
Date: Sat, 18 Mar 2017 03:12:26 +0000 [thread overview]
Message-ID: <bug-97059-502-MSxqthJoDH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97059-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 514 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97059
--- Comment #14 from Fabian Maurer <dark.shadow4@web.de> ---
The opengl calls blender make are faulty, since a trace doesn't render properly
on windows with proprietary AMD drivers either.
Though I still want to ask, could we get rid of the random contents? Under
windows it's just black instead of drawing random images. To me at least that
seems like the better approach.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1331 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-03-18 3:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 11:02 [Bug 97059] Tahiti+DRI3+Unity+Blender corruption bugzilla-daemon
2016-07-23 11:02 ` bugzilla-daemon
2016-07-23 11:05 ` bugzilla-daemon
2016-07-25 10:01 ` bugzilla-daemon
2016-07-25 12:50 ` bugzilla-daemon
2016-07-25 19:16 ` bugzilla-daemon
2016-07-26 3:02 ` bugzilla-daemon
2016-07-26 3:30 ` bugzilla-daemon
2016-07-26 4:00 ` bugzilla-daemon
2016-07-26 4:41 ` bugzilla-daemon
2016-07-26 5:58 ` bugzilla-daemon
2016-07-26 6:24 ` bugzilla-daemon
2016-10-17 11:32 ` bugzilla-daemon
2017-03-18 2:28 ` bugzilla-daemon
2017-03-18 3:12 ` bugzilla-daemon [this message]
2017-10-04 15:39 ` 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-97059-502-MSxqthJoDH@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