From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31830] [bisected] broken shadows in Unigine Sanctuary and Lightsmark
Date: Wed, 26 Jan 2011 02:17:15 -0800 (PST) [thread overview]
Message-ID: <20110126101715.9E68D13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31830-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31830
--- Comment #8 from Pavel Ondračka <drakkk@centrum.cz> 2011-01-26 02:17:15 PST ---
Created an attachment (id=42516)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42516)
screenshot of the problem
(In reply to comment #7)
> Created an attachment (id=42514)
View: https://bugs.freedesktop.org/attachment.cgi?id=42514
Review: https://bugs.freedesktop.org/review?bug=31830&attachment=42514
> Disable instruction rewriting in the scheduler
>
> I think this bug is actually in the scheduler, and it is just being exposed by
> the reg rename pass. I have been able to track down a few instructions that
> the scheduler is converting from vector to scalar that change how the shadows
> are rendered. However, these conversions look valid too me, so I'm really not
> sure what the problem is. I think this patch fixes Lightsmark, but I'm not
> sure what the shadows are supposed to look like. Can you try this patch on
> Lightsmark and Sanctuary. Thanks.
Hi, this patch doesn't help neither. I tested it alone and also with the first
patch. Concerning how the penumbra shadows should look, you don't get the right
behavior with RADEON_DEBUG=noopt? I've attached screenshot comparing bad and
good shadows. Don't know how to help you more, I still have the debug patches
you've sent me when we were debugging sanctuary before the "enable rename_reg"
patch was committed, maybe I could use them again to identify the failing
shader?
--
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
next prev parent reply other threads:[~2011-01-26 10:17 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 ` [Bug 31830] [bisected] broken shadows in Unigine Sanctuary and Lightsmark bugzilla-daemon
2011-01-23 8:33 ` 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 [this message]
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=20110126101715.9E68D13004F@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).