From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63520] New: r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected)
Date: Sun, 14 Apr 2013 07:29:44 +0000 [thread overview]
Message-ID: <bug-63520-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1651 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63520
Priority: medium
Bug ID: 63520
Assignee: dri-devel@lists.freedesktop.org
Summary: r300g regression (RV380): Strange rendering of light
sources in Penumbra (bisected)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: pj_beers@hotmail.com
Hardware: x86 (IA32)
Status: NEW
Version: 9.0
Component: Drivers/Gallium/r300
Product: Mesa
Created attachment 77936
--> https://bugs.freedesktop.org/attachment.cgi?id=77936&action=edit
Bad rendering screen 1
Since mesa-9.0, light is rendered incorrectly in the Penumbra games (Overture,
Black Plague, Requiem). I find it hard to describe so I've included two good
and two bad screenshots from two scenes to illustrate the problem. For, fixing
this bug would mean rendering of light sources as in the "good" screenshots.
I've bisected (between mesa-8.0 and mesa-9.0) and the first bad commit is
134a0a5ff88851c971fb95863317f640b5b9fa3a , r300/compiler: Use the smart
scheduler for r300 cards. I then checked out current master and reverting this
commit fixes the problem in master.
I compiled mesa with the following options:
--with-dri-drivers="radeon,swrast"
--with-gallium-drivers="r300,swrast"
--enable-gallium-llvm
--enable-texture-float
--enable-gallium-g3dvl
--enable-glx-tls
--enable-motif
--enable-xvmc
My system is Slackware 14.0 with kernel 3.7.6, libdrm-2.4.42 and
xf86-video-ati-7.1.0.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3135 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
next reply other threads:[~2013-04-14 7:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 7:29 bugzilla-daemon [this message]
2013-04-14 7:30 ` [Bug 63520] r300g regression (RV380): Strange rendering of light sources in Penumbra (bisected) bugzilla-daemon
2013-04-14 7:30 ` bugzilla-daemon
2013-04-14 7:31 ` bugzilla-daemon
2013-04-14 7:32 ` bugzilla-daemon
2013-04-29 21:17 ` bugzilla-daemon
2013-04-29 21:18 ` bugzilla-daemon
2013-04-29 21:19 ` bugzilla-daemon
2013-05-11 11:42 ` bugzilla-daemon
2013-05-11 11:45 ` bugzilla-daemon
2013-05-11 11:46 ` bugzilla-daemon
2013-05-11 11:47 ` bugzilla-daemon
2013-05-11 11:48 ` bugzilla-daemon
2013-05-11 11:49 ` bugzilla-daemon
2013-05-11 11:49 ` bugzilla-daemon
2013-05-11 11:50 ` bugzilla-daemon
2013-05-11 11:51 ` bugzilla-daemon
2013-05-11 11:51 ` bugzilla-daemon
2013-05-11 12:00 ` bugzilla-daemon
2013-05-20 14:48 ` bugzilla-daemon
2013-05-20 15:06 ` bugzilla-daemon
2013-05-21 20:29 ` bugzilla-daemon
2013-05-21 20:34 ` bugzilla-daemon
2013-06-16 3:23 ` bugzilla-daemon
2013-06-25 21:10 ` bugzilla-daemon
2013-07-01 12:41 ` bugzilla-daemon
2013-07-01 14:55 ` 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-63520-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).