Give Java3D 1.3.2 a try:
Andrew Donaldson wrote:
Hi Bill and others,
Thanks for having a look at this.
I tried changing the BoundingSphere to MAX_VALUE, POSITIVE_INFINITY,
-1.0, 0.0 and 1.0, all of which produced no noticeable difference.
We have also now tested on:
- Windows 2000, Matrix G450, Java 1.4.2_05, Java3D 1.3.1 OpenGL
- RedHat Enterprise WS4, ATI Radeon X600, Java 1.4.2_09, Java3D 1.3.1
which also produce the fault.
Our previous testing was all with Nvidia cards, all of which had the
It is good to see it happening with Nvidia, ATI and Matrox OpenGL
implementations on both windows and linux.
This problem is affecting our production of Tropical Cyclone
warning graphics, which can be issued at any time now that we are in
the cyclone season here. Any help fixing it is appreciated.
I will look into what is involved in removing the scalar maps,
I expect it won't be fun :)
Bill Hibbard wrote:
I found one little bit of dumbness in the AmbientLight:
the BoundingSphere is created with a radius of 2000000.0
(looks like a throwback to McIDAS and Vis5D). You might
experiment with changing:
new BoundingSphere(new Point3d(0.0,0.0,0.0), 2000000.0);
new BoundingSphere(new Point3d(0.0,0.0,0.0), Double.MAX_VALUE);
new BoundingSphere(new Point3d(0.0,0.0,0.0),
in the createSceneGraph() method of
Please let us know if either change solves your problem.
I doubt either will fix the problem because your test
program should be well within the 2000000.0 radius of the
current BoundingSphere, but nothing about this problem
makes sense so its worth a try.