Hi Justin > to immediate mode. I think that the immediate mode requeusts are just > trying to justify the lack of vision on the part of game programmers to > change development mindsets. "We've always done it this way so you must > accommodate the way we work".
I partly agree and disagree. A big problem coming with Java3D is you don't know when rendering is actually done. Okay byRef is nice for changing geometry but still I've got very interesting flickering effects while changing camera and byRefs Geometries at the same time inside of a Behaviour node on a frame/frame basis. (Changing only one alltough doesn't result into flickering [however knows why]) And other things like multi pass rendering is nearly completly out of the way in retained mode. At least I haven't found a solution which would satisfy my needs. Orderedgroups are nice but still don't work out if you want to change states/materials or other things between passes. The only way to solve this would be to fire up the memory usage by adding more objects from the same Shape3D. EOF, J.D. -- Explore SRT with the help of Java3D (http://wwwvis.informatik.uni-stuttgart.de/relativity/minkowski) (http://www.antiflash.net/java3d/relativity (mirror) =========================================================================== 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".
