All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 26 Jan 2017 01:37:12 +0000	[thread overview]
Message-ID: <bug-98784-502-tANVAfXs7r@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98784-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98784

--- Comment #15 from Michel Dänzer <michel@daenzer.net> ---
Thanks for raising the issue with Croteam.

(In reply to Germano Massullo from comment #14)
> I've just double checked and we definately set GL_DRAW_FRAMEBUFFER to 0
> (default back buffer) before clear.

When I look at the trace from comment #10 in qapitrace, I see a bunch of
glBindFramebuffer(GL_DRAW_FRAMEBUFFER, ...) calls in frame 0, the last one
being

 glBindFramebuffer(GL_DRAW_FRAMEBUFFER, 31)

After that, there are no glBindFramebuffer calls for a long time.
GL_DRAW_FRAMEBUFFER isn't set to 0 before frame 777, after which the flickering
stops, and the window contents start looking as expected.

I've now also confirmed this with running glretrace in gdb and setting a
breakpoint at _mesa_BindFramebuffer.

I'd definitely like somebody else to confirm the above though, to make sure I'm
not missing anything.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2083 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

  parent reply	other threads:[~2017-01-26  1:37 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
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 [this message]
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-tANVAfXs7r@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.