I'm trying to implement some code that needs to render a scene several times before allowing behaviors to modify the scenegraph. I noticed the stopBehaviorScheduler routine. The docs mention this is a heavy-weight routine. Would calling this routine be more expensive then calling the stopEnable on each behavior in the scene? Or is there some nicer way to pause the behavior engine. I'm working on combining J3D with an openGL spherical projection library. I've gotten it to work fine for one pass. For larger screen spaces it wants multiple views so it can sphericaly project those together. In openGL you just render the same scene multiple times. So I'm trying to replicate this. Basically I need to render a frame between 1-4 times without the scenegraph changing. My JNI calls are inside the canvas's preRender and postRender methods. So any action I do to stop scenegraph updates needs keep the system rendering frames, ie I can just stop the whole rendering system. I will be playing with this over the next few weeks but I thought I'd check to see if anyone had some insight into how this might work. BTW, I've gotten J3D to work with an Elumens Dome. This work is to make it support the larger displays they sell. -Alan Hudson =========================================================================== 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".
