From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 42435] Suspected loss of varyings between shaders
Date: Sat, 25 Feb 2012 22:26:24 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id ECAB6A0878
for ;
Sat, 25 Feb 2012 14:26:24 -0800 (PST)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=42435
--- Comment #14 from Claudio Freire 2012-02-25 14:26:24 PST ---
I experience a similar situation with Ironlake and Mesa 8.0.1, only with far
more complex shaders.
Apparently, in these shaders, all varyings get bogus data on the fragment
shader.
The only workaround I can find is passing that data through the built-in
varying in gl_TexCoord, although that's quite suboptimal for other drivers so I
would prefer not to.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.