Java3D slower with 2 CPUS

[java3d-interest]

Any Java3D MT Gurus left on the forum?

I have scenes with animated Textures using imagesUpdaters, and on a Thinkpad T61p (dual core) on Win XP, these scenes run more slowly than normal until I force Windows to set the Java3D app process affinity to ONLY ONE CPU.

I know this has been raised before: http://forums.java.net/jive/message.jspa?messageID=224347.

Did anyone ever investigate possible causes, solutions?

I want to try resolve this before releasing Java3DWorkbench, version 2.0.

Thanks.
[Message sent by forum member 'mcneillk' (mcneillk)]

http://forums.java.net/jive/thread.jspa?messageID=303780

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@...
For additional commands, e-mail: interest-help@...

[java3d-interest]

Hi

I haven't problems with Java3d and dual core before. Actually they work fine so far.

But T¨61 uses NVidia vcard, and some applications fails to use multi thread in OpenGL in this cards. I think it should not happen with Java3D, as it uses a single thread for rendering, but you can try to disable OGL multi-thread support on NVidia control panel :

NVidia Control Panel
Advanced Configurations
Global Settings
Threaded optimization - set is as OFF
[Message sent by forum member 'aces' (aces)]

http://forums.java.net/jive/thread.jspa?messageID=303804

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@...
For additional commands, e-mail: interest-help@...

[java3d-interest]

Thanks for the suggestion; however, the multi-threaded support had no effect on the problem.

I did find a solution using property

"j3d.threadLimit=2"

This causes the frame rate to become normal again.

One strange issue remains: there is a case where I DO NOT need to change this value: it's when I am using an SWT_AWT frame that I configure in an Eclipse Workbench View. Whereas, using "plain AWT" or using an SWT_AWT frame that I configure with the SWT API, the problem is present!

This leads me to believe that the Thread (or perhaps GC) inherited from the Eclipse Workbench View may have been configured in some special way in order to be more multi-core friendly...
[Message sent by forum member 'mcneillk' (mcneillk)]

http://forums.java.net/jive/thread.jspa?messageID=303910

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@...
For additional commands, e-mail: interest-help@...