*ping*. Anything to be done on my end? -tom
tom fogal writes:
> --- =_aa0
> Content-Type: text/plain; charset="us-ascii"
> Content-ID: <27394.131845620...@shigeru.sci.utah.edu>
>
> Hi Ian, Kenneth,
>
> Ian Romanick writes:
> > On 10/10/2011 03:30 PM, tom fogal wrote:
> > > One of
Hi Ian, Kenneth,
Ian Romanick writes:
> On 10/10/2011 03:30 PM, tom fogal wrote:
> > One of our programs which relies on shaders heavily is having
> > issues, and I have tracked it down to unexpected values in
> > gl_NormalMatrix within the fragment shader.
>
> I think we could make a more genera
On 10/11/2011 01:21 PM, tom fogal wrote:
> Ian Romanick writes:
>> Yikes! A *lot* has changed in the fragment shader back-end for i965
>> since 7.10.2. Have you at least tried 7.10.3? 7.11?
>
> I have not. To be honest, I am pretty daunted by trying a new X
> driver. I don't quite understand
Ian Romanick writes:
> On 10/10/2011 03:30 PM, tom fogal wrote:
> > One of our programs which relies on shaders heavily is having
> > issues, and I have tracked it down to unexpected values in
> > gl_NormalMatrix within the fragment shader.
> >
> > Using the attached program (patch against mesadem
On 10/10/2011 03:30 PM, tom fogal wrote:
One of our programs which relies on shaders heavily is having issues,
and I have tracked it down to unexpected values in gl_NormalMatrix
within the fragment shader.
Using the attached program (patch against mesademos repo) I did
printf-esque debugging to
One of our programs which relies on shaders heavily is having issues,
and I have tracked it down to unexpected values in gl_NormalMatrix
within the fragment shader.
Using the attached program (patch against mesademos repo) I did
printf-esque debugging to get the values of gl_NormalMatrix. Search
