"uuilly" <willy.lists@[EMAIL PROTECTED]
> wrote in message
news:45365034-b72c-4076-b8c8-a3c2940ee44e@[EMAIL PROTECTED]
Aug 22, 3:15 pm, uuilly <willy.li...@[EMAIL PROTECTED]
> wrote:
[...]
....A little more info
...With this signature:
>void combineCallback(GLfloat coords[ 3 ],
GLfloat *vertex_data[ 4 ],
GLfloat weight[4], GLfloat **dataOut )
The variable "coords," that is supposed to contain the location of the
newly created point, is printing total junk. Ie: numbers that are way
too big and seemingly out of left field. So somehow I'm giving GLU
something that is causing it to puke.
>Is it a problem that I'm using GLfloats instead of GLdoubles? I was
>always under the impression that GPU's don't have double precision so
>they're no point in using them.
>Thanks,
>Willy
That's not the right signature for the combine callback, coords must be
double. There's no GPU involved here. the signature is defined by the glu
source code and requires double.
(if gpu's could do tesselation, we wouldn't need tesselation routines...
right ?).
jbw
|
