From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71138] flashlight bug in L4D2
Date: Fri, 01 Nov 2013 23:39:27 +0000 [thread overview]
Message-ID: <bug-71138-502-9ZXrMvW0xd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71138-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71138
--- Comment #4 from yashax@windowslive.com ---
(In reply to comment #3)
> This looks like z-fighting issues. You might want to try disabling compiler
> backends via R600_DEBUG environment variable:
>
> R600_DEBUG=nollvm
> R600_DEBUG=nosb
> R600_DEBUG=nollvm,nosb
The bug still exists with these environment variables.
The bug report and my last tests were done with shader detail setting on low.
I found that the bug happens with shader detail on low and medium, but on high
and very high the bug disappears.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1429 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-01 23:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 19:48 [Bug 71138] New: flashlight bug in L4D2 bugzilla-daemon
2013-11-01 19:51 ` [Bug 71138] " bugzilla-daemon
2013-11-01 19:53 ` bugzilla-daemon
2013-11-01 19:54 ` bugzilla-daemon
2013-11-01 21:44 ` bugzilla-daemon
2013-11-01 23:39 ` bugzilla-daemon [this message]
2013-12-02 10:04 ` bugzilla-daemon
2013-12-21 16:53 ` bugzilla-daemon
2014-02-12 12:44 ` bugzilla-daemon
2014-03-14 12:45 ` bugzilla-daemon
2014-04-11 13:11 ` bugzilla-daemon
2014-04-11 17:31 ` 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-71138-502-9ZXrMvW0xd@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).