Re: [JAVA3D] Attribute change performance Issue.

[Norihito Hiruma]

Everyone is grateful. > From: Kevin Rushforth [mailto:[EMAIL PROTECTED]] > > Have you tried updating the material without detaching/reattaching the > entire scene? It is possible that the overhead of making a large > scene graph with a large number of Shape3D nodes live is taking > most of the time. Why detach viewplatform before the color change? The reason is repress to screen renewal run twice. The screen renewal is run twice when do not detach viewplatform. I don't know why it is. Many CAD users dislike the screen flash, so I repressed it. Is this way correct or not? I don't know. > From: Doug Gehringer [mailto:[EMAIL PROTECTED]] > Your program has exposed a performance problem with Java3D 1.2. > If there are too many shapes with the same appearance the performance can suffer due to an n^2 algorithm. > In your case there are 10,000 shapes with equivalent appearances, so the slowdown is more severe. > The problem is being addressed, it won't be fixed for 1.2.1 beta, but it should be fixed for the final release of 1.2.1. Thank you for recognizing it with the issue. I expect next Java3d, and wait. (At first, I think there was a problem in my code.... ) > This is another problem. > When making many changes to the scene graph outside of a behavior there is no way for Java3D to know when you are done and Java3D will probably update before you are ready. > Stopping/starting the renderer or detaching/attaching the scene graph can fix the problem, but both have unnecessary overhead. > A better way is to use > Behavior.postId(). The idea is to set up a behavior which can be triggered when the edits need to happen. > The edits happen in the processStimulus() method for the > behavior. > This way Java3D can hold off on updating the display until after processStimulus() has returned. > > See the updated Test.java for an example of this. Search for "updateBehavior". Thank you very much. You gave us very good information. I try it soon. May I think about the countermeasure which code use Update behavior is permanent way? Or, should I think that it is temporary countermeasure? - [EMAIL PROTECTED] =========================================================================== 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".