From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37296] New: [r600g] lightning artifacts on frozenbyte games
Date: Tue, 17 May 2011 11:21:10 -0700 (PDT) [thread overview]
Message-ID: <bug-37296-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=37296
Summary: [r600g] lightning artifacts on frozenbyte games
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: a.heider@gmail.com
Created an attachment (id=46835)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46835)
screenshot
On a x86-64 host with a HD3870 running 2.6.39-2-generic (from ubuntu's oneiric)
and
libdrm-2.4.25 and mesa compiled for 32bit:
OpenGL renderer string: Gallium 0.4 on AMD RV670
OpenGL version string: 2.1 Mesa 7.11-devel (git-390196e)
I get lightning artifacts with r600g on a couple of games from frozenbyte.com,
most notably when using the flashlight in shadowgrounds.
Here's a apitrace capture:
http://static.hackmii.com/dhewg/shadowgrounds.apitrace.xz
When replaying it via glretrace there're some weird window resizes, but the
issue is visible when it doesn't crash :)
The issue does not exist with swrast.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-17 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 18:21 bugzilla-daemon [this message]
2011-05-18 8:44 ` [Bug 37296] [r600g] lighting artifacts on frozenbyte games bugzilla-daemon
2011-05-22 20:33 ` bugzilla-daemon
2015-11-18 20:12 ` bugzilla-daemon
2016-02-26 3:32 ` 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-37296-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 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).