[EMAIL PROTECTED] wrote:
>
> HI,
>
> [EMAIL PROTECTED] wrote:
> >[EMAIL PROTECTED] wrote:
> >> Keith wrote:
> >> >I've just committed a more comprehensive fix which allows us to skip the
> >> >offending vertices in the window transform and in FX/fxvsetup. It also
> >> >clears up a longstanding wierdness introduced into clipping (the CLIP_4D
> >> >hack/crock).
> >>
> >> I got them, but it still has the overflow/invalid float problem with
> >> xlockmore. The two run-time errors are at the end of this mail.
> >> The second error only occurs when "lament" is the first demo to start.
> >> IMHO this indicates some initialization problem.
> >> I have not found any of the demo programs to give this problem.
> >
> >
> >There's been a long-outstanding bug in Mesa with the "lament" mode of
> >xlockmore. I've been unable to reproduce it myself but it's probably
> >a subtle bug somewhere in persp_textured_triangle.
> >
> >Therefore, this bug may have nothing to do with Keith's overhaul of
> >the transformation code.
>
> 1) the persp_textured_triangle was found in the stairs mode not in lament.
> 2) I seem to have no problems with mesa up to the time when Keith's new
> code has been added to the CVS.
> 3) The xlockmore version contains a work-around by Eric Lassauge for a problem
> with textures in Mesa.
>
> Jouk
I'll download this & have a look. Are you experiencing your old problem
with gears? I take it to mean that this xlockmore problem didn't exist
in the original version (before either patch was applied to CVS) - is
this correct?
Keith
