From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30313] New: Corrupted textures with 'big' textures and at certain distances from texture
Date: Tue, 21 Sep 2010 12:11:01 -0700 (PDT) [thread overview]
Message-ID: <bug-30313-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30313
Summary: Corrupted textures with 'big' textures and at certain
distances from texture
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: gerwin_kramer@hotmail.com
Created an attachment (id=38848)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38848)
This texture is corrupted
In several 3d applications some textures are rendered wrong. If the distance to
the texture changes, the textures can be rendered correct again.
In OpenArena the textures are not or rarely distorted when the 'texture detail'
setting is at it's lowest. At the highest setting, several textures are
distorted. If i move away or towards to the texture, the texture can be
rendered correct again.
The bug is similar to https://bugs.freedesktop.org/show_bug.cgi?id=28800 , but
with some differences:
- This bug wasn't there with r300c
- It is with several apps i tested, Extreme Tux Racer, Octagaplayer, Blender,
OpenArena.
- I don't know if the WoW bug has the distance and texture detail thing.
I'm using
- ubuntu maverick with the
- xorg edgers ppa,
- so, gallium r300g driver
- kernel 2.6.35-22
- R350 agp ati radeon 9800 pro card.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-21 19:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 19:11 bugzilla-daemon [this message]
2010-09-21 19:11 ` [Bug 30313] Corrupted textures with 'big' textures and at certain distances from texture bugzilla-daemon
2010-09-21 19:13 ` bugzilla-daemon
2010-09-21 19:14 ` bugzilla-daemon
2010-09-21 19:14 ` bugzilla-daemon
2010-09-21 19:15 ` [Bug 30313] Several (big) textures are corrupted when you look at them from certain distances bugzilla-daemon
2010-09-21 19:16 ` bugzilla-daemon
2010-09-21 19:16 ` bugzilla-daemon
2010-09-21 19:19 ` bugzilla-daemon
2010-09-21 19:22 ` [Bug 30313] [r300g] " bugzilla-daemon
2010-09-21 19:25 ` bugzilla-daemon
2010-09-25 1:34 ` bugzilla-daemon
2010-09-25 12:48 ` bugzilla-daemon
2010-09-25 13:02 ` bugzilla-daemon
2010-09-25 14:05 ` bugzilla-daemon
2010-09-25 15:08 ` bugzilla-daemon
2010-09-25 16:51 ` bugzilla-daemon
2010-09-25 23:29 ` bugzilla-daemon
2010-09-25 23:38 ` bugzilla-daemon
2010-09-25 23:45 ` bugzilla-daemon
2010-09-26 13:31 ` bugzilla-daemon
2010-09-26 16:41 ` bugzilla-daemon
2010-09-26 18:54 ` bugzilla-daemon
2010-09-26 18:55 ` bugzilla-daemon
2010-09-26 18:56 ` bugzilla-daemon
2010-09-26 18:57 ` bugzilla-daemon
2010-09-26 18:58 ` bugzilla-daemon
2010-09-26 18:58 ` bugzilla-daemon
2010-09-26 19:00 ` bugzilla-daemon
2010-09-26 19:01 ` bugzilla-daemon
2010-09-26 19:04 ` bugzilla-daemon
2010-09-26 21:04 ` bugzilla-daemon
2010-09-26 21:59 ` bugzilla-daemon
2010-10-12 23:00 ` 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-30313-502@http.bugs.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.