----- Forwarded message from "From: Bill Hibbard
> 3. It cannot be used in a remote X-windows session, only on
> the local console.)
However, 1. and 3., are both good reasons, as is 2. in some
situations. Another reason is that Java3D is a bit of a memory
hog - hopefully this will be fixed with Java3D version 1.2.
I seem to remember getting Java3D to work on a remote X-windows session
one needs to make sure both ends support GLX extensions. While this is
not optimal it was not impossible.
bellenot@xxxxxxxxxxxx http://www.math.fsu.edu/~bellenot (850)644-7189 (4053fax)