From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31830] [bisected] broken shadows in Unigine Sanctuary and Lightsmark
Date: Thu, 27 Jan 2011 01:18:41 -0800 (PST) [thread overview]
Message-ID: <20110127091841.CF73613004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31830-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31830
--- Comment #11 from Pavel Ondračka <drakkk@centrum.cz> 2011-01-27 01:18:41 PST ---
(In reply to comment #10)
> (In reply to comment #3)
> > What penumbra quality number are you using in Lightsmark? Are you seeing any
> > error messages like this:
> >
> > r300: ERROR: FS input generic 18 unassigned, not enough hardware slots.
> > r300: ERROR: FS input generic 19 unassigned, not enough hardware slots.
> > r300: ERROR: FS input generic 20 unassigned, not enough hardware slots.
> > r300: ERROR: FS input WPOS unassigned, not enough hardware slots.
> >
>
> In Lightsmark, I've been able to identify the failing shader and a few
> instruction transformations that change the way the shadows are rendered. I've
> spent a lot of time looking at this, and all the transformations in question
> appear to be correct. It's possible that above errors are the reason why the
> shadows are misrendering. The last error about WPOS also appears in sanctuary.
>
> My hypothesis is that with these kinds of errors, the behavior of a shader is
> undefined. This means that prior to the commit in question, the scenes were by
> luck being rendered correctly, or close enough so that it wasn't noticeable.
> Then, the modifications made to the shader by the reg_rename pass changed the
> state of the GPU in such a way that the misrendering became more obvious.
>
> Maybe Marek can comment on whether or not this is a plausible hypothesis.
Does this also explain the slowdown mentioned in comment 2? Because it is in
all scenes, not only the "penumbra shadows" one and it is really weird that
RADEON_DEBUG=noopt actually makes things faster.
--
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-27 9:18 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
2011-01-26 17:05 ` bugzilla-daemon
2011-01-27 8:48 ` bugzilla-daemon
2011-01-27 9:18 ` bugzilla-daemon [this message]
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=20110127091841.CF73613004E@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).