From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28517] [r300g] loop unrolling fails (was: Savage 2 : characters are not rendered + another corruptions)
Date: Fri, 3 Sep 2010 13:48:30 -0700 (PDT) [thread overview]
Message-ID: <20100903204830.6455D1300D0@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28517-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #34 from Sven Arvidsson <sa@whiz.se> 2010-09-03 13:48:30 PDT ---
Created an attachment (id=38409)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38409)
Screenshot of smearing in menu
(In reply to comment #33)
>
> This may be fixed now that loop unrolling is merged. Can you retest?
It is if not fixed, at least a whole lot better now! :)
Fixed:
* The model in the menu and the player character is rendered correctly as far
as I can tell.
* The horrible slowdown is gone.
Remaining problems are:
* "Smearing" in the menu (see screenshot for a better explanation) probably
because I'm still getting "radeon: The kernel rejected CS, see dmesg for more
information." errors logged in the terminal.
* Ingame, all textures seems to be white, not sure if this is related to my
problems with S3TC or something else.
So the GLSL side of things seems to have been taken care of!
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-09-03 20:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 9:58 [Bug 28517] New: [r300g] Savage 2 : characters are not rendered + another corruptions bugzilla-daemon
2010-06-13 9:59 ` [Bug 28517] " bugzilla-daemon
2010-06-13 9:59 ` bugzilla-daemon
2010-06-13 11:18 ` bugzilla-daemon
2010-06-24 8:38 ` bugzilla-daemon
2010-06-26 19:27 ` bugzilla-daemon
2010-06-26 20:25 ` bugzilla-daemon
2010-06-26 21:12 ` bugzilla-daemon
2010-07-08 19:45 ` [Bug 28517] [r300g] loop unrolling fails (was: Savage 2 : characters are not rendered + another corruptions) bugzilla-daemon
2010-08-06 6:37 ` bugzilla-daemon
2010-08-06 10:33 ` bugzilla-daemon
2010-08-06 18:27 ` bugzilla-daemon
2010-08-06 18:42 ` bugzilla-daemon
2010-08-10 5:48 ` bugzilla-daemon
2010-08-10 8:33 ` bugzilla-daemon
2010-08-10 14:51 ` bugzilla-daemon
2010-08-19 14:39 ` bugzilla-daemon
2010-08-25 8:49 ` bugzilla-daemon
2010-08-25 13:46 ` bugzilla-daemon
2010-08-25 14:20 ` bugzilla-daemon
2010-08-25 14:32 ` bugzilla-daemon
2010-08-25 15:09 ` bugzilla-daemon
2010-08-25 20:55 ` bugzilla-daemon
2010-08-26 1:20 ` bugzilla-daemon
2010-08-26 13:38 ` bugzilla-daemon
2010-08-26 21:09 ` bugzilla-daemon
2010-08-26 21:32 ` bugzilla-daemon
2010-08-26 22:41 ` bugzilla-daemon
2010-08-26 23:09 ` bugzilla-daemon
2010-08-26 23:31 ` bugzilla-daemon
2010-08-27 7:37 ` bugzilla-daemon
2010-08-30 16:08 ` bugzilla-daemon
2010-08-30 19:01 ` bugzilla-daemon
2010-08-30 19:24 ` bugzilla-daemon
2010-09-01 21:21 ` bugzilla-daemon
2010-09-03 19:19 ` bugzilla-daemon
2010-09-03 20:48 ` bugzilla-daemon [this message]
2010-09-04 6:14 ` bugzilla-daemon
2010-09-04 9:49 ` bugzilla-daemon
2010-09-04 12:12 ` bugzilla-daemon
2010-09-04 12:59 ` bugzilla-daemon
2010-09-05 20:02 ` 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=20100903204830.6455D1300D0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.