From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68451] Texture flicker in native Dota2 in mesa 9.2.0rc1
Date: Thu, 19 Dec 2013 17:06:31 +0000 [thread overview]
Message-ID: <bug-68451-502-yELEBKMeG1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68451-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 928 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68451
--- Comment #45 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #44)
> Got flickering increasing in time here too. Radeon HD 5750 (Juniper PRO,
> evergreen).
> (that on a up-to-date fedora 19 x86-64, yes I did install that for all the
> gaming c++ kludge bloody hell)
Do you mean the flickering increases in time even if you stay where you are in
DOTA 2? If so, it may be a different bug. The patch fixed the flickering I was
seeing (and I think it was the same for Peter) in some specific areas (always
the same flickering intensity in a given area, it could be related to some
elements in the are like the river or towers for example).
Peter reopened this bug because the patch was not backported to mesa 9.2 but it
had been fixed for him too when applied manually.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1813 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-12-19 17:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:59 [Bug 68451] New: Texture flicker in native Dota2 in mesa 9.2.0rc1 bugzilla-daemon
2013-08-22 21:06 ` [Bug 68451] " bugzilla-daemon
2013-08-22 23:11 ` bugzilla-daemon
2013-08-23 7:56 ` bugzilla-daemon
2013-08-23 8:11 ` bugzilla-daemon
2013-08-24 12:31 ` bugzilla-daemon
2013-08-26 6:25 ` bugzilla-daemon
2013-08-26 12:52 ` bugzilla-daemon
2013-08-26 14:36 ` bugzilla-daemon
2013-08-26 19:59 ` bugzilla-daemon
2013-08-26 20:02 ` bugzilla-daemon
2013-08-26 20:03 ` bugzilla-daemon
2013-08-26 21:20 ` bugzilla-daemon
2013-08-26 21:30 ` bugzilla-daemon
2013-08-27 20:50 ` bugzilla-daemon
2013-08-28 13:28 ` bugzilla-daemon
2013-08-30 23:13 ` bugzilla-daemon
2013-08-31 7:37 ` bugzilla-daemon
2013-09-08 20:16 ` bugzilla-daemon
2013-09-12 13:40 ` bugzilla-daemon
2013-09-12 15:57 ` bugzilla-daemon
2013-09-18 20:50 ` bugzilla-daemon
2013-09-20 3:25 ` bugzilla-daemon
2013-09-20 3:32 ` bugzilla-daemon
2013-09-21 0:35 ` bugzilla-daemon
2013-10-05 16:35 ` bugzilla-daemon
2013-10-05 17:21 ` bugzilla-daemon
2013-10-05 22:29 ` bugzilla-daemon
2013-10-05 22:59 ` bugzilla-daemon
2013-10-06 11:20 ` bugzilla-daemon
2013-10-09 15:41 ` bugzilla-daemon
2013-10-09 20:27 ` bugzilla-daemon
2013-10-10 0:35 ` bugzilla-daemon
2013-10-10 11:33 ` bugzilla-daemon
2013-10-10 20:36 ` bugzilla-daemon
2013-10-10 21:08 ` bugzilla-daemon
2013-10-10 21:13 ` bugzilla-daemon
2013-10-10 21:51 ` bugzilla-daemon
2013-10-10 22:34 ` bugzilla-daemon
2013-10-13 14:34 ` bugzilla-daemon
2013-10-14 16:48 ` bugzilla-daemon
2013-10-14 17:14 ` bugzilla-daemon
2013-11-19 13:03 ` bugzilla-daemon
2013-12-19 15:19 ` bugzilla-daemon
2013-12-19 15:42 ` bugzilla-daemon
2013-12-19 16:41 ` bugzilla-daemon
2013-12-19 16:52 ` bugzilla-daemon
2013-12-19 16:57 ` bugzilla-daemon
2013-12-19 17:06 ` bugzilla-daemon [this message]
2013-12-20 5:09 ` bugzilla-daemon
2014-01-05 15:43 ` bugzilla-daemon
2014-01-05 16:51 ` bugzilla-daemon
2014-01-05 17:10 ` bugzilla-daemon
2014-01-05 17:25 ` bugzilla-daemon
2014-01-05 18:04 ` bugzilla-daemon
2014-01-05 18:51 ` bugzilla-daemon
2014-02-03 23:58 ` bugzilla-daemon
2014-02-07 19:34 ` bugzilla-daemon
2014-02-07 19:44 ` bugzilla-daemon
2014-02-08 16:41 ` bugzilla-daemon
2014-02-09 10:56 ` bugzilla-daemon
2014-03-24 22:07 ` bugzilla-daemon
2014-04-24 23:44 ` 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-68451-502-yELEBKMeG1@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).