From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39940] New: OilRush shader water artefacts after GLSL-To-TGSI commit
Date: Mon, 8 Aug 2011 12:42:57 -0700 (PDT) [thread overview]
Message-ID: <bug-39940-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39940
Summary: OilRush shader water artefacts after GLSL-To-TGSI
commit
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: stalkerg@gmail.com
Created an attachment (id=50037)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50037)
Bug water, after GLSL-To-TGSI
After GLSL-To-TGSI commit I am detect some artefacts in OilRush game.
Plese see screenshot.
--
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:[~2011-08-08 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 19:42 bugzilla-daemon [this message]
2011-08-08 19:43 ` [Bug 39940] OilRush shader water artefacts after GLSL-To-TGSI commit bugzilla-daemon
2011-08-12 12:22 ` bugzilla-daemon
2012-08-31 21:10 ` 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-39940-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.