This has been our #1 headache with running applets in the plug-in.
The user has to manually change it. I heard rumors that in a future
release of the plug-in that it would pick a memory size based on
what the machine actually has available. What a concept....
In a memory intensive API like Java3D this will be a critical improvement.
Trying to walk a non computer geek through changing the value over the
phone has proven to be no fun..
The old #1 problem was getting users to install Java3D in the right
place. The Java3D team did a great job fixing that.
-- John
"Durga.Banda" wrote:
>
> Hai All,
>
> When I am executing the following Code I am getting the following error
> java.lang.OutOfMemoryError <<no stack trace available>>
>
> How can optimize this code and Improve the Performance.
>
> /***********
>
> TransformGroup ballStickTransGrp = new TransformGroup();
> Transform3D translate = new Transform3D();
> Appearance app = new Appearance();
>
> for(int i = 0; i < 24000; i++)
> {
> v3f.x = 0.0f;
> v3f.y = 0.0f;
> v3f.z = 0.0f;
>
> translate.setTranslation(v3f);
>
> TransformGroup transformGroup = new TransformGroup(translate);
> transformGroup.addChild(new Sphere(0.5f,
> Sphere.GENERATE_NORMALS, 10, app));
>
> ballStickTransGrp.addChild(transformGroup);
> }
>
> ***************/
>
> Thanks and Regards
> Ravi Sankar
>
> ===========================================================================
> 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".
===========================================================================
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".
