You could use 2 ImageComponents per Texture object and double buffer them.
That brings your ImageComponent needs down to 2. In Java 3D 1.1.* we will
copy the image data each time you do a set on the ImageComponent, so you
will still incur that cost. We hope to resolve that issue in the 1.2 API.
Doug Twilleager
Java 3D Team
> X-Accept-Language: en
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [JAVA3D] Animated textures
> To: [EMAIL PROTECTED]
>
> Sorry if this is repetitive, I posted it a couple of weeks ago and
> didn't get an answer:
>
> Is there a faster / more efficient way to do animated textures than to
> create new ImageComponent and Texture objects every time a texture image
> changes? I can't find any documentation that says Java 3D does / doesn't
> support animated textures.
>
> -Jeremy Smoler
>
> ===========================================================================
> 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".
