From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73528] Deferred lighting in Second Life causes system hiccups and screen flickering
Date: Sun, 23 Aug 2015 12:54:21 +0000 [thread overview]
Message-ID: <bug-73528-502-TT7WiVRRFN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 782 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73528
--- Comment #42 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
(In reply to MWATTT from comment #41)
Interesting discovery, thank you for looking into that. Perhaps in this case
the problem lies somewhere else, and it's not directly the fault of single
sample fast color clear? Would it be worth one of the developers looking into
it, if there were important advantages to the disabled fast-clear method?
Please however don't make any untested changes in the mainstream branch if so.
Marek's fix just got shaders working again, I wouldn't want to go back to the
old situation. If his is the best solution, I'm certainly happy with that!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1712 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:[~2015-08-23 12:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 23:04 [Bug 73528] New: Deferred lighting in Second Life causes system hiccups and screen flickering bugzilla-daemon
2014-01-12 23:27 ` [Bug 73528] " bugzilla-daemon
2014-01-12 23:53 ` bugzilla-daemon
2014-01-15 4:10 ` bugzilla-daemon
2014-01-26 12:35 ` bugzilla-daemon
2014-02-16 12:05 ` bugzilla-daemon
2014-05-03 0:32 ` bugzilla-daemon
2014-05-23 0:36 ` bugzilla-daemon
2014-05-23 13:20 ` bugzilla-daemon
2014-05-26 3:10 ` bugzilla-daemon
2014-05-26 11:49 ` bugzilla-daemon
2014-05-26 11:51 ` bugzilla-daemon
2014-05-26 11:53 ` bugzilla-daemon
2014-05-26 11:55 ` bugzilla-daemon
2014-05-27 3:04 ` bugzilla-daemon
2014-05-27 3:08 ` bugzilla-daemon
2014-11-03 15:16 ` bugzilla-daemon
2014-11-15 21:43 ` bugzilla-daemon
2014-11-17 4:36 ` bugzilla-daemon
2014-11-17 13:13 ` bugzilla-daemon
2014-11-17 18:48 ` bugzilla-daemon
2014-11-17 22:22 ` bugzilla-daemon
2014-11-18 1:49 ` bugzilla-daemon
2014-11-18 2:14 ` bugzilla-daemon
2014-11-18 12:39 ` bugzilla-daemon
2014-11-18 16:05 ` bugzilla-daemon
2014-11-18 16:10 ` bugzilla-daemon
2014-11-26 1:17 ` bugzilla-daemon
2015-02-03 1:17 ` bugzilla-daemon
2015-02-07 13:28 ` bugzilla-daemon
2015-02-12 1:19 ` bugzilla-daemon
2015-02-26 21:24 ` bugzilla-daemon
2015-04-08 17:39 ` bugzilla-daemon
2015-07-01 13:57 ` bugzilla-daemon
2015-07-01 18:26 ` bugzilla-daemon
2015-07-02 1:45 ` bugzilla-daemon
2015-07-02 10:30 ` bugzilla-daemon
2015-07-02 10:36 ` bugzilla-daemon
2015-07-03 14:32 ` bugzilla-daemon
2015-07-04 12:30 ` bugzilla-daemon
2015-07-07 23:46 ` bugzilla-daemon
2015-07-30 16:34 ` bugzilla-daemon
2015-07-30 16:47 ` bugzilla-daemon
2015-08-23 12:54 ` bugzilla-daemon [this message]
2015-11-19 20:13 ` bugzilla-daemon
2015-11-24 11:39 ` bugzilla-daemon
2015-11-24 11:46 ` 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-73528-502-TT7WiVRRFN@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