Lan, > > For the platform independence, we switched from c to java3D. > > I have never done any accurate quantity analysis on the java3d performance. > I simply address the fact with my experience. The biggest problems are > memory and speed. > > In c with Motif, OpenGL, we could handle 800x800 grids with the objects as > individuals on terrain grids, but java3D can handle 25x22 grids only with > shared objects. The reasons for such big difference includes using Shape3D > to represent the objects instead of Shape2D implemented in c because the > OrientedShape in j3d does not work well with Shared Group.
What's the problem you have with O3D ? If it is a j3d bug, please send us a bug report. >From Java 3D specification : OrientedShape3D is similar in functionality to the Billboard behavior, but OrientedShape3D nodes will orient themselves correctly for each view, and they can be used within a SharedGroup. - Chien Yang Java 3D Team. =========================================================================== 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".
