All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91656] Pillars of Eternity glitch in maps
Date: Sun, 16 Aug 2015 10:06:25 +0000	[thread overview]
Message-ID: <bug-91656-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 91656
           Summary: Pillars of Eternity glitch in maps
           Product: Mesa
           Version: git
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: christoph.rabel@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

There is a regression/graphical glitch when playing Pillars of Eternity. When I
use the ingame map, it is partly "dark/black".

You can find a screenshot here:
http://images.akamai.steamusercontent.com/ugc/439450977393999113/19DF4F643F0C4BB058665F056DBC4600D669ED7B/

The map looks fine with regular Ubuntu drivers (10.1.3), I checked a couple of
days ago with a reinstall (my harddisk broke). After an "upgrade" to oibaf
repository, the glitch appeared.

The glitch was not there mid-June with 10.6(?) or so. I used oibaf then too,
but didn't play for a month. It was probably introduced about June 15 or later.
(Maybe a bit earlier, I don't upgrade the beta drivers every day). It was there
when I started playing again July 18th.

My card is a Radeon 4870:

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.0-devel
(git-28ed1e0 2015-08-14 trusty-oibaf-ppa)

If you need me to test something or need further information, please feel free
to ask. (Enable debug output somehow?) I have browsed PoE logfiles and
/var/log, but couldn't find anything that looked even vaguely related. No
errors when loading the map or displaying it.

(Btw.: Congrats to Mesa 11!)

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

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

             reply	other threads:[~2015-08-16 10:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 10:06 bugzilla-daemon [this message]
2015-08-16 11:13 ` [Bug 91656] Pillars of Eternity glitch in maps 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

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@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.