|
 |
How should I specify all_intersections in an isosurface.
I tried:
isosurface {
function{....}
bounded_by {....}
max_trace all_intersections
texture{....}
}
this gives a error, a float is expected after max trace.
If I delete max_trace and only put in all_intersections, there also is an error:
isosurface component MAXTRACE>(ISOSURFACE_MAXTRACE)
ingo
--
Met dank aan de muze met het glazen oog.
Post a reply to this message
|
|
|
|
On Wed, 14 Jul 1999 21:35:48 +0200, ingo wrote:
>How should I specify all_intersections in an isosurface.
>I tried:
> isosurface {
> function{....}
> bounded_by {....}
> max_trace all_intersections
> texture{....}
> }
>this gives a error, a float is expected after max trace.
>If I delete max_trace and only put in all_intersections, there also is an error:
>isosurface component MAXTRACE>(ISOSURFACE_MAXTRACE)
This looks like a bug. I don't know why nobody's ever noticed it before.
The second method is correct, though I suspect the docs say otherwise.
Unfortunately, specifying "all_intersections" sets max trace to 199,
but later code requires (for some unknown or perhaps obsolete reason)
that max trace be ten or less.
If you feel okay with compiling the source code, you can either remove
that test from parse.c (I think that's safe, since it doesn't seem to use
the ten-element array anywhere I can find) or you can increase
ISOSURFACE_MAXTRACE in isosrf.h to 200, which will have the undesirable
side effect of making isosurface objects use much more memory.
If you don't feel okay with compiling the source code, the best you can
do is to set max_trace to 10 until the problem is fixed. That should
work for most simple objects.
Post a reply to this message
|
|
