All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34217] New: [r300g] Unigine Sanctuary: no fog visible
Date: Sat, 12 Feb 2011 13:38:27 -0800 (PST)	[thread overview]
Message-ID: <bug-34217-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g] Unigine Sanctuary: no fog visible
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
               URL: http://unigine.com/download/#sanctuary
        OS/Version: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pavel.ondracka@email.cz


When doing some other testing I noticed that there should be white fog near
ground. I was quite sure it worked some time ago so I investigated this more.
However this isn't regression its just that some configuration works and some
not. The only one working configuration is Sanctuary v2.2 and shaders set to
low, then it kinda works. Sanctuary version 2.3 with all shaders settings and
2.2 version with medium and high shaders quality are broken.
I've also tried RADEON_DEBUG=noopt and RADEON_NO_TCL=1 with no luck.

Mesa: a6b7393eb8b4ef14c0d9ba8d64e57ed8ca82a9f7
GPU: RV530

-- 
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-02-12 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-12 21:38 bugzilla-daemon [this message]
2011-03-29 23:52 ` [Bug 34217] [r300g] Unigine Sanctuary: no fog visible 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-34217-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.