>
>
> I think the statements about minimum state
>required to implement features that are scattered through the spec are
>aimed more at people implementing the spec than people using an
>implementation, but I may be very wrong about that.
>
>Tom
>
>
No, you are correct, but knowing about the
On 0, John Manko <[EMAIL PROTECTED]> wrote:
[snip]
> Also, according to 1.4 specs:
>
> The state required for clipping is at least 6 sets of plane equations
> (each consisting of four double-percision floating-point coefficients)
> and at least 6 corresponding bits indicating which of these
>
On 0, "Eric G. Miller" <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 22, 2002 at 04:11:44PM +0930, Tom Cook wrote:
> > Hi all,
> >
> > This may be a mesa bug or it may be a manifestation of my ignorance of
> > opengl. If the latter then I apologise
On Sun, Sep 22, 2002 at 04:11:44PM +0930, Tom Cook wrote:
> Hi all,
>
> This may be a mesa bug or it may be a manifestation of my ignorance of
> opengl. If the latter then I apologise for OT posting.
>
> I am playing with clipping planes in an effort to do some fancy stuf
Tom Cook wrote:
>Hi all,
>
>This may be a mesa bug or it may be a manifestation of my ignorance of
>opengl. If the latter then I apologise for OT posting.
>
>I am playing with clipping planes in an effort to do some fancy stuff
>in 3D graphics. My problem is that mesa a
Tom Cook wrote:
>Hi all,
>
>This may be a mesa bug or it may be a manifestation of my ignorance of
>opengl. If the latter then I apologise for OT posting.
>
>I am playing with clipping planes in an effort to do some fancy stuff
>in 3D graphics. My problem is that mesa a
Hi all,
This may be a mesa bug or it may be a manifestation of my ignorance of
opengl. If the latter then I apologise for OT posting.
I am playing with clipping planes in an effort to do some fancy stuff
in 3D graphics. My problem is that mesa appears to only let me define
a client clipping
7 matches
Mail list logo
