In Java3D 1.2.1, Java3D will unindexify IndexedGeometryArray before rendering.
In Java3D 1.3, we have a new API - GeometryArray.USE_COORD_INDEX_ONLY which when
specified as a component of vertexFormat will not unindexify but use
glDrawElements() instead and this mode is acceleared on many graphics cards.
-Uma
> Delivered-To: [EMAIL PROTECTED]
> MIME-Version: 1.0
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006
> X-AntiAbuse: This header was added to track abuse, please include it with any
abuse report
> X-AntiAbuse: Primary Hostname - nuku.vosn.net
> X-AntiAbuse: Original Domain - java.sun.com
> X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
> X-AntiAbuse: Sender Address Domain - digitalsedition.com
> Date: Sun, 12 Aug 2001 18:39:39 -0400
> From: DigitalSedition Developer Relations <[EMAIL PROTECTED]>
> Subject: [JAVA3D] GeometryArrary vs IndexedGeometry Array
> To: [EMAIL PROTECTED]
>
> Hi folks,
>
> I'm looking for someone who can answer a fundamental issue - is the current
implementation of IndexedGeometryArray (in particular IndexedTriangleArray)
optmized in any way as to be able to perform faster than a regular
TriangleArray.
>
> Thanks in advance,
>
>
===========================================================================
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".
