From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26735] New: r600: rendering artifacts
Date: Wed, 24 Feb 2010 13:04:21 -0800 (PST) [thread overview]
Message-ID: <bug-26735-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26735
Summary: r600: rendering artifacts
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: edwintorok@gmail.com
I have tested the open source radeon drivers on my ATI Radeon HD4650.
First of all many thanks for the work on this driver, KMS works like a charm
[1], and no 3D app has crashed (fglrx tends to deadlock lately).
Now to some rendering artifacts I noticed in blender (and some games, like
Heroes of Newerth beta).
To reproduce on Debian unstable x86-64:
1. Install blender 2.49.2 (apt-get install blender)
2. Open the attached test.blend
3. Switch to textured mode (press ALT-Z)
4. There are 3 noticable artifacts here (see screenshot1_r600 attached):
- the floor tiles at the bottom have an L shaped whiteish stain on them, that
shouldn't be there
- the spotlight has black stripes, instead of just lighting an area
- the blender interface has a black/grey thing at the bottom that it shouldn't
5. Press P to start the game engine
6. Move the mouse around to move the spotlight. See the black stripes moving
along with it, there shouldn't be any black stripes at all!
See screenshot2_r600 vs screenshot2_swref
To get the reference renders you can either use fglrx, or Mesa's software mode
(which will be very slow, but will get nice renders). These images aren't
perfect either (there is some aliasing), but much better than the r600 ones:
LIBGL_ALWAYS_SOFTWARE=1 blender
System info:
$ glxinfo|grep OpenGL
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV730 9498) 20090101 TCL DRI2
OpenGL version string: 2.1 Mesa 7.8-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
Linux 2.6.33-rc8-00189-g9f3a628 (compiled by me, .config attached)
mesa from git (compiled by me, mesa_7_6_1_rc1-5145-g2f5beb4)
with this patch applied:
http://cgit.freedesktop.org/~andrem/mesa/commit/?h=r600-
test&id=6ee755760d124c85bdfd121fd491f68fccca84f7
>From Debian unstable/experimental packages:
Xorg 7.5
xserver-xorg-video-radeon 6.12.99+git20100201.a887818f-1
libdrm1-radeon, libdrm2: 2.4.18-2
libgl1-mesa-dri: 7.7-3 (but see below, I used my own build instead)
If you need more info, just ask.
[1] I had to download© R700_rlc.bin to the proper place, and thanks to some
help on #radeon fix a missing libdri.so, but everything else worked
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-02-24 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 21:04 bugzilla-daemon [this message]
2010-02-24 21:04 ` [Bug 26735] r600: rendering artifacts bugzilla-daemon
2010-02-24 21:04 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:05 ` bugzilla-daemon
2010-02-24 21:10 ` bugzilla-daemon
2010-02-24 21:21 ` bugzilla-daemon
2010-02-24 21:57 ` bugzilla-daemon
2010-02-25 9:17 ` bugzilla-daemon
2012-11-02 16:26 ` bugzilla-daemon
2012-11-06 10:27 ` 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-26735-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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).