Question for the Sun folks ( and anyone who knows the internals) . We have coords, colors, texcoords and normals in a piece of geometry which we want to update often, but not always every frame: 1. If we use a geometry updator and use the set() methods on non-ref geometry, but only update the normals and coords does the texcoords and colors still get sent to the card that frame? 2. If we use a call geometry updator but don't use by-ref geometry, and within the updator we do not do any set() methods is anything sent to the card in that frame? Is it still considered "dirty"? 3. If we have all our information stored in arrays of floats and the colors in arrays of byte, will any slow translations happen during geom.setNNN() calls? In other words, is there any format like point3f(), float[], double[] etc which is most optimal for you to work with. I am especially interested in anything that is not vertexCount() dependent for speed. In other words is there any format that does not require you to "loop" through the data to transform it for display list. 4. Other than the copy caused by doing set(), is there any additional overhead in performance between using the setters and using the geometry by reference? 5. If you use the setters to frequently update the geometry does this cause a lot of memory deallocation/allocation or is the data laid down into the internal structures without allocations being neccessary? Thank you very much for your responses in advance, Dave Yazel =========================================================================== 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".
