Chien, I'm using an IndexedTriangleArray with ByRef and UCIO bits and specified as below:
IndexedTriangleArray ita = new IndexedTriangleArray ( vertCoordsFloat.length / 3, IndexedTriangleArray.COORDINATES | IndexedTriangleArray.NORMALS | IndexedTriangleArray.TEXTURE_COORDINATE_2 | IndexedTriangleArray.BY_REFERENCE | IndexedTriangleArray.USE_COORD_INDEX_ONLY, vertIds.length ); ita.setCapability(GeometryArray.ALLOW_REF_DATA_READ); ita.setCapability(GeometryArray.ALLOW_REF_DATA_WRITE); ita.setCoordRefFloat( vertCoordsFloat ); ita.setCoordinateIndices( 0, vertIds ); ita.setNormalRefFloat( vertNormalsFloat ); ita.setTexCoordRefFloat( 0, vertTexCoordsFloat ); When the code flow passes thru' the above block there appears to be a memory bloat with a magnitude that is a significant percentage of the geometry size (and much more than the indices array size). Just wondering if Java 3D is unrolling some arrays or if the UCIO bit has any effect for the above combo. Are you aware of any issues related to the above ? TIA 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".