GeometryInfo will by fully enhanced in 1.3. It will support
geometry BY_REFERENCE, INTERLEAVED, USE_COORD_INDEX_ONLY,
Multi-texture geometry, etc. etc. etc.
-Paul
> Delivered-To: [EMAIL PROTECTED]
> Delivered-To: [EMAIL PROTECTED]
> Date: Mon, 13 Aug 2001 12:12:49 -0700
> From: R Vegan <[EMAIL PROTECTED]>
> Subject: Re: [JAVA3D] GeometryArray vs IndexedGeometryArray
> To: [EMAIL PROTECTED]
>
> Hi Uma,
>
> Wow ! It's great news that Java3D 1.3 will have the new facility
> for treating indexed geometry. I wish this new API will be available
> soon though - the design of my application is very highly dependent
> on using indexed geometry array for memory optimization. I have
> been rewriting parts of my app. in unindexified form to accomodate
> Java3D 1.2.1 limitation.
>
> While at it, may I ask why is it that GeometryInfo does not have
> the facility to setCoordinates *ByReference* ? After all, geometryinfo
> is just a utility function ( unlike a geometryarray ) and therefore
> should not have any impact on rendering performance because of
> setting coordinates by reference. I am currently wasting a lot of
> memory whenever I want to display part of my geometry only but
> end up setting coordinates available for the whole geometry. Any
> workaround for this or is there an upcoming enhancement ?
>
> Thanks in advance
>
> Raj Vaidya
>
> ===========================================================================
> 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".
===========================================================================
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".
