"wayne c deprince jr." wrote:
>
> ok, sounds good.. but what about branchgroup compile optimizations? can
> more be performed on a simple branchgroup as opposed to a large
> complicated one? thanks again, wayne
Usually more optimisations can be done on a single large BG than many
small ones. This is because a BG basically acts as a block inndicating a
single chunk of optimised(able) code. When compiling the scene graph, if
the compiler comes across a BG, it does not attempt to traverse that
part of the scene graph.
Typically tricks are the removal of Transforms (flatting to remove
expensive matrix calculations for each frame), minimising rendering
context swaps (rendering everything that uses one colour, then swapping
colour and doing the next lot of geometry) and probably a bunch of other
things.
I remember someone from Sun posted a guide to making J3D 1.1 run fast.
You might be wise to check out the FAQ (URL in sig) for more
information. I vaguely remember that we've put some of this stuff there.
--
Justin Couch Author, Java Hacker
Snr Software Engineer [EMAIL PROTECTED]
ADI Ltd, Systems Group http://www.vlc.com.au/~justin/
Java3D FAQ: http://tintoy.ncsa.uiuc.edu/~srp/java3d/faq.html
-------------------------------------------------------------------
"Look through the lens, and the light breaks down into many lights.
Turn it or move it, and a new set of arrangements appears... is it
a single light or many lights, lights that one must know how to
distinguish, recognise and appreciate? Is it one light with many
frames or one frame for many lights?" -Subcomandante Marcos
-------------------------------------------------------------------
===========================================================================
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".
