From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares
Date: Tue, 03 Jan 2017 12:51:49 +0000 [thread overview]
Message-ID: <bug-98784-502-z3T9ZGAati@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98784-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2581 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98784
--- Comment #7 from Samuel Pitoiset <samuel.pitoiset@gmail.com> ---
Can you try with LIBGL_DRI3_DISABLE=1 ? This will use DRI2 and it should fix
the flickering.
After bisecting, the first bad commit seems to be:
commit d3d33918c79d9e87aedaf6f70ed39f75eed262a0
Author: Michel Dänzer <michel.daenzer@amd.com>
Date: Wed Aug 17 17:02:04 2016 +0900
loader/dri3: Overhaul dri3_update_num_back
Always use 3 buffers when flipping. With only 2 buffers, we have to wait
for a flip to complete (which takes non-0 time even with asynchronous
flips) before we can start working on the next frame. We were previously
only using 2 buffers for flipping if the X server supports asynchronous
flips, even when we're not using asynchronous flips. This could result
in bad performance (the referenced bug report is an extreme case, where
the inter-frame stalls were preventing the GPU from reaching its maximum
clocks).
I couldn't measure any performance boost using 4 buffers with flipping.
Performance actually seemed to go down slightly, but that might have
been just noise.
Without flipping, a single back buffer is enough for swap interval 0,
but we need to use 2 back buffers when the swap interval is non-0,
otherwise we have to wait for the swap interval to pass before we can
start working on the next frame. This condition was previously reversed.
Cc: "12.0 11.2" <mesa-stable@lists.freedesktop.org>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97260
Reviewed-by: Frank Binns <frank.binns@imgtec.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
(cherry picked from commit 1e3218bc5ba2b739261f0c0bacf4eb662d377236)
Squashed with commit:
loader/dri3: Always use at least two back buffers
This can make a significant difference for performance with some extreme
test cases such as vblank_mode=0 glxgears.
Fixes: 1e3218bc5ba2 ("loader/dri3: Overhaul dri3_update_num_back")
Cc: "12.0 11.2" <mesa-stable@lists.freedesktop.org>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97549
Reviewed-by: Jason Ekstrand <jason@jlekstrand.net>
Tested-by: Dieter Nützel <Dieter@nuetzel-hh.de>
(cherry picked from commit dc3bb5db8c81e7f08ae12ea5d3ee999e2afcbfd1)
:040000 040000 aa5cf86f1e98d023f9539a6a15654fd9754101a2
fb92ad057feeb3fbff38d808c71c7e5e1cead9af M src
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4304 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-01-03 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 17:12 [Bug 98784] Talos Principle rendering flickering garbage on start instead of Croteam logo bugzilla-daemon
2016-11-19 17:23 ` [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares bugzilla-daemon
2016-11-19 17:30 ` bugzilla-daemon
2016-11-19 17:33 ` bugzilla-daemon
2016-11-19 19:54 ` bugzilla-daemon
2016-11-20 13:59 ` bugzilla-daemon
2016-11-20 14:37 ` bugzilla-daemon
2017-01-03 12:51 ` bugzilla-daemon [this message]
2017-01-03 17:06 ` bugzilla-daemon
2017-01-05 9:52 ` bugzilla-daemon
2017-01-05 11:21 ` bugzilla-daemon
2017-01-11 10:06 ` bugzilla-daemon
2017-01-19 2:20 ` bugzilla-daemon
2017-01-19 9:49 ` bugzilla-daemon
2017-01-25 10:22 ` bugzilla-daemon
2017-01-26 1:37 ` bugzilla-daemon
2017-02-14 18:46 ` bugzilla-daemon
2017-02-15 9:27 ` 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-98784-502-z3T9ZGAati@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).