dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31830] [bisected] broken shadows in Unigine Sanctuary and Lightsmark
Date: Fri, 21 Jan 2011 04:19:37 -0800 (PST)	[thread overview]
Message-ID: <20110121121938.4A8B213004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31830-502@http.bugs.freedesktop.org/>

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

Pavel Ondračka <drakkk@centrum.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[bisected] Unigine          |[bisected] broken shadows
                   |Sanctuary: broken shadows   |in Unigine Sanctuary and
                   |                            |Lightsmark

--- Comment #2 from Pavel Ondračka <drakkk@centrum.cz> 2011-01-21 04:19:37 PST ---
Penumbra shadows in Lightsmark 2008 2.0 are broken with the same commit. It
works fine with RADEON_DEBUG=noopt. 
BTW during bisecting I run into some interesting performance issues:

Before 8833f53e659e079e7ab74bb9197f9b44b1eeefe0: 5,66 +- 0,01 fps, shadows are
OK
mesa 8833f53e659e079e7ab74bb9197f9b44b1eeefe0: 3,69 +- 0,07 fps, broken shadows

with current mesa master (af4e2f46653cbc7ceaf1291ba22087ec5758d07f):
stock settings: 10,23 +- 0,08 fps, broken shadows
with RADEON_DEBUG=noopt: 11,73 +- 0,16 fps, shadows are OK
with register rename pass disabled: 14,35 +- 0,04 fps shadows are OK

I disabled register rename by changing r3xx_fragprog.c line 127,
{"register rename", 1, !is_r500 || opt, rc_rename_regs,    NULL},
to {"register rename", 1, !is_r500, rc_rename_regs,NULL},
I hope this is correct.

Mesa: af4e2f46653cbc7ceaf1291ba22087ec5758d07f
Kernel: 2.6.37
GPU: RV530

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2011-01-21 12:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  7:56 [Bug 31830] New: [bisected] Unigine Sanctuary v2.2: broken shadows bugzilla-daemon
2010-11-22  7:57 ` [Bug 31830] " bugzilla-daemon
2011-01-05 10:54 ` [Bug 31830] [bisected] Unigine Sanctuary: " bugzilla-daemon
2011-01-21 12:19 ` bugzilla-daemon [this message]
2011-01-23  8:33 ` [Bug 31830] [bisected] broken shadows in Unigine Sanctuary and Lightsmark bugzilla-daemon
2011-01-23  8:53 ` bugzilla-daemon
2011-01-24  9:13 ` bugzilla-daemon
2011-01-25 13:24 ` bugzilla-daemon
2011-01-26  9:11 ` bugzilla-daemon
2011-01-26 10:17 ` bugzilla-daemon
2011-01-26 17:05 ` bugzilla-daemon
2011-01-27  8:48 ` bugzilla-daemon
2011-01-27  9:18 ` bugzilla-daemon
2011-01-27 10:20 ` bugzilla-daemon
2011-01-28  8:20 ` bugzilla-daemon
2011-01-28  8:21 ` bugzilla-daemon
2011-01-28  8:22 ` bugzilla-daemon
2011-01-28  8:53 ` bugzilla-daemon
2011-01-28  9:36 ` bugzilla-daemon
2011-01-28 11:42 ` bugzilla-daemon
2011-01-28 18:56 ` bugzilla-daemon
2011-02-06  7:54 ` 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=20110121121938.4A8B213004E@annarchy.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).