Manfred Weiler (mdweiler@immd9.informatik.uni-erlangen.de)
Wed, 23 Jun 1999 18:30:18 +0000
On the other hand for most cases I see no need to create a (sometimes huge and
only parsely populated) transient data structure. Especially on low-end
workstations without 3D texture interpolation this structure consumes much of
the rare main memory due to the great number of "bricks". In addition to that
I guess that working with this structure reduces performance because of quite
a number of system calls (memory (de-)allocation, creating/deleting object on
the stack).
I admit that using this structure is more flexible but I think that
display lists could do the same job and the vertices and polygons that should
be drawn are stored where they will be needed.
Maybe you will object that the transient geometry can be cached between the
frames. But this leads to errors in the resulting image when the view
parameters change, so for correct images slicing has to be performed in every
frame.
So why not add a draw method to Volumizer which works totaly without transient
geometry?
Manfred.
This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 14:02:50 PST