All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33142] New: r300g produces black textures in nexuiz with glsl offsetmapping on
Date: Sat, 15 Jan 2011 00:17:33 -0800 (PST)	[thread overview]
Message-ID: <bug-33142-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=33142

           Summary: r300g produces black textures in nexuiz with glsl
                    offsetmapping on
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: kontrollator@gmx.de


When i run stock phoronix test suite nexuiz i get black textures. I found that
this is caused by using th effects-high.cfg. when i swith to effects-normal all
textures look as they should. i found that this is caused by glsl_offsetmapping
set to 1 (aka enabled). when i change it to 0 everything is okay, when i change
it to 1 all textures are black. System is an rv410 (x700 mobility), latest mesa
/ drm / kernel from git as of today. i filed this bug against  drm, if it is
more likely a mesa problem feel free to reassign it. if you need more info
please tell me. thank you for your time.

greetings jan kreuzer

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-01-15  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  8:17 bugzilla-daemon [this message]
2011-01-15 10:41 ` [Bug 33142] r300g produces black textures in nexuiz with glsl offsetmapping on bugzilla-daemon
2011-01-18 22:44 ` 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-33142-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.