Re: [JAVA3D] Attribute change performance Issue.

[Norihito Hiruma]

Thank you for making it reply to kindness. It is very much helped. Lets me reply in the sentence. > - My reading of your code seems to suggest you are using exactly the > same material colour values for all 10K objects. Is that so? > If so, why > use 10K instances of the Material object. You should just use one and > share that instance between all Shape3D instances. The more instances > you can share, the faster your application. For example, if > you have 10 > different coloured objects you only need 10 instances of the Material > rather than 10,000. Because, CAD-Entity must hold a respectively different attribute. 1 CAD-Entity will be mapping to 1 Shape3D in CAD-Application. So, each Shape3D has different Material in test program. I had tried a code which was all Shape3D refer one Material, and change that one Material. The color change time of this case was about five seconds. ( Yes, a little faster than last code, but still slow ) > - You may be stumbling on something j3d is doing with the rendering > process if it is taking so long. Have you tried calling stopRender(), > changing all the values, and then calling startRender() again? Yes, I had tried this too. ( call stopRender() -> setDiffuseColor() -> startRender() ) But the result didn't change, so I deleted the code. - [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".