Hi Raj, >Hi: > >My problem is related to the one described by Dave Yazel >but taken to the EXTREME. > >I use Geometry ByRef simply because I want to conserve memory and not >because I EVER intend to dynamically update my coordinates. I currently >use clearCapabilityIsFrequent but I am not sure how much the benefits are.
If you don't intend to change the data you should not set the ALLOW_REF_DATA_WRITE capability, in which case the IsFrequent bit has no effect. >The question that I have is: If I do Geometry ByRef, and if I can >guarantee that I will never ever update the geometry, is there any >way that I could get this info. onto Java3D so that Java3D can exploit >this fact for efficient rendering? >A method such as setCapabilityNeverEver(..) would be nice :) The default capability for everything in Java3D is 'NeverEver'. If you don't set the ALLOW_REF_DATA_WRITE capability for your Geometry Java3D will assume (actually it will enforce) that you will never change the data. Rgds Paul ---------------------------------------------------------- Paul Byrne Email : [EMAIL PROTECTED] Sun Microsystems Phone : (650) 786 9926 Visualization Software Group Fax : (650) 786 5852 ---------------------------------------------------------- =========================================================================== 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".
