>> Er.. it's not obvious about the indexing. Because I gather from postings
>> on this list from Sun folk that the IndexedGeometry gets unfolded to
lists
>> of triangles or polygons or whatever before it gets sent to the graphics
>> subsystem. And since this has to happen, you probably pay a performance
>> penalty while waiting for the unfolding.
If its true that indexed triangle lists always get unfolded to non-indexed
ones, it still might be a performance advantage to use it, because
"unfolding" is nothing but copying some bytes around - but transforming,
clipping and lighting the same vertex three times means a whole bunch of
matrix transformations.
It always depends on the implementation. Best thing would be to have some
benchmarks on the Java3D implementation. Daniel, what does JBench say about
it?
Apropos benchmarking: Anyone knows a standard API method which I can use to
read the system timer at a higher accuracy than that provided by
System.currentTimeMillis()?? I haven't found one and therefore implemented a
small native DLL for windows which uses Windows' high resolution timer
(which has a resolution of a few nanoseconds). Works well, but isn't
portable. Does anyone know a portable way for this?
-- Julian
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
