Justin,
Java3D 1.3 does support image equivalent of GeometryUpdater. Give it a try.
/**
* The ImageComponent2D.Updater interface is used in updating image data
* that is accessed by reference from a live or compiled ImageComponent
* object. Applications that wish to modify such data must define a
* class that implements this interface. An instance of that class is
* then passed to the <code>updateData</code> method of the
* ImageComponent object to be modified.
*
* @since Java 3D 1.3
*/
Charmaine Lee
Sun Microsystems
> Date: Wed, 13 Mar 2002 15:32:44 +1100
> From: Justin Couch <[EMAIL PROTECTED]>
> Subject: [JAVA3D] Animated texture management at runtime
> To: [EMAIL PROTECTED]
> MIME-version: 1.0
> Content-transfer-encoding: 7bit
> X-Accept-Language: en-us, en
> Delivered-to: [EMAIL PROTECTED]
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9)
Gecko/20020311
>
> oops... F@&%^@ mail client deciding J3D means terrain list.....
>
>
> Just evening out the quota of questions asked v answered :)
>
> I'm trying to decide on what is the most efficient architecture for my
> SVG texture system. For simple static textures, the setup is quite
> simple - parse an XML doc, throw it through Bartik to create a
> BufferedImage and then pass that to an appropriate ImageComponent2D. The
> fun stuff comes when someone decides they want to animate an SVG texture.
>
> The conundrum I have to face is how to best manage the interaction of
> Batik and Java3d for texture animation for best performance. Bartik
> seems to want to produce a "new" image for each SVG frame render.
> Essentially it has double-buffer animation system. Each time the frame
> changes, hand me the "other" BufferedImage.
>
> On the receiving end I have ImageComponent2D. I'm going to set this up
> to use ByRef images. That means I can't alter the content of the current
> image that is being rendered otherwise Bad Things Happen. Unfortunately
> Java3D doesn't have a texture equivalent of GeometryUpdater, that would
> make life so simple! I can set up a brute-force approach that will work
> using ImageComponent2D.setImage() every time the SVG renderer changes
> without much thought.
>
> My main concern is the performance impact of calling setImage() every
> frame with a new BI instance. I suspect this is going to impact
> performance quite a bit - particularly if I'm going to be running
> animated textures.
>
> --
> Justin Couch http://www.vlc.com.au/~justin/
> Java Architect & Bit Twiddler http://www.yumetech.com/
> Author, Java 3D FAQ Maintainer http://www.j3d.org/
> -------------------------------------------------------------------
> "Humanism is dead. Animals think, feel; so do machines now.
> Neither man nor woman is the measure of all things. Every organism
> processes data according to its domain, its environment; you, with
> all your brains, would be useless in a mouse's universe..."
> - Greg Bear, Slant
> -------------------------------------------------------------------
>
> ===========================================================================
> 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".
