dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91656] [APITRACE] [bisected] Pillars of Eternity glitch in maps
Date: Thu, 17 Mar 2016 17:12:00 +0000	[thread overview]
Message-ID: <bug-91656-502-Rzy2WGoxZI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91656-502@http.bugs.freedesktop.org/>


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

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

Nicolai Hähnle <nhaehnle@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #16 from Nicolai Hähnle <nhaehnle@gmail.com> ---
For what it's worth, a comment in the hack posted on the forum says

"PoE tries to read from and render to a texture at the same time when rendering
the minimap. This happens directly after clearing the fbo to (0, 0, 0, 0) so
bind a dummy texture with that value instead."

So this was either a PoE bug (so-called "feedback loop") or possibly a driver
bug related to clearing a currently bound texture that was fixed recently. In
any case, this seems to be fixed now, so closing this report.

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

[-- Attachment #1.2: Type: text/html, Size: 2479 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:[~2016-03-17 17:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 10:06 [Bug 91656] Pillars of Eternity glitch in maps bugzilla-daemon
2015-08-16 11:13 ` bugzilla-daemon
2015-08-16 16:39 ` bugzilla-daemon
2015-09-13 11:41 ` bugzilla-daemon
2015-09-27  7:46 ` bugzilla-daemon
2015-09-27 22:03 ` bugzilla-daemon
2015-09-30 13:53 ` bugzilla-daemon
2015-10-04 20:21 ` bugzilla-daemon
2015-10-05 20:15 ` bugzilla-daemon
2015-10-06  4:44 ` bugzilla-daemon
2015-10-06 12:19 ` bugzilla-daemon
2015-10-06 14:45 ` bugzilla-daemon
2015-10-17 17:29 ` bugzilla-daemon
2015-10-30 15:04 ` bugzilla-daemon
2015-10-30 19:27 ` bugzilla-daemon
2015-11-18 17:50 ` [Bug 91656] [APITRACE] [bistected] " bugzilla-daemon
2015-11-18 17:50 ` [Bug 91656] [APITRACE] [bisected] " bugzilla-daemon
2016-03-17 14:40 ` bugzilla-daemon
2016-03-17 17:12 ` bugzilla-daemon [this message]

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-91656-502-Rzy2WGoxZI@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