From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91656] [APITRACE] [bisected] Pillars of Eternity glitch in maps Date: Thu, 17 Mar 2016 17:12:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1630456013==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1BA686EA0E for ; Thu, 17 Mar 2016 17:12:00 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1630456013== Content-Type: multipart/alternative; boundary="14582347201.1dFFB5e67.2146"; charset="UTF-8" --14582347201.1dFFB5e67.2146 Date: Thu, 17 Mar 2016 17:12:00 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=91656 Nicolai Hähnle changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #16 from Nicolai Hähnle --- 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. --14582347201.1dFFB5e67.2146 Date: Thu, 17 Mar 2016 17:12:00 +0000 MIME-Version: 1.0 Content-Type: text/html changed bug 91656
What Removed Added
Resolution --- FIXED
Status NEW RESOLVED

Comment # 16 on bug 91656 from 
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.
--14582347201.1dFFB5e67.2146-- --===============1630456013== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1630456013==--