When I first started using Java3D I used v. 1.1.2.  It worked well and I was
impressed with yet another Java product. I upgraded to v. 1.1.3 and things
still worked well. I am creating a product for my company and was beginning
to feel that I could rely on Java3D to do the job for me. When v 1.2 beta
came out I decided to wait until it was out of the beta stage. Well, it's
out of the beta stage but v 1.2 so full of crippling bugs that I have
finally decided to go back to v 1.1.3. I'd rather deal with the previous
versions problems (such as garbage collection) than with the poor
performance and frequent crashes v 1.2 has to offer. I've decided to see if
the next upgrade will work better and have retreated to a wait and see
attitude re. Java3D in general. Now I'm also considering alternatives like
Magician.

Dear Java3D team, My program relies heavily on allowing the user to
manipulate the scene. And this is the area in which v 1.2 is falling so
short.

I routinely receive errors like

java.lang.IndexOutOfBoundsException: Index: -1, Size: 2
        at java.util.ArrayList.RangeCheck(ArrayList.java:491)
        at java.util.ArrayList.get(ArrayList.java:307)
        at
javax.media.j3d.RenderBin.findOrderedCollection(RenderBin.java:3061)
        at javax.media.j3d.RenderBin.findEnvironmentSet(RenderBin.java:3449)
        at javax.media.j3d.RenderBin.insertRenderAtom(RenderBin.java:2867)
        at
javax.media.j3d.RenderBin.processGeometryAtoms(RenderBin.java:2398)
        at javax.media.j3d.RenderBin.processMessages(RenderBin.java:974)
        at
javax.media.j3d.StructureUpdateThread.doWork(StructureUpdateThread.java:83)
        at javax.media.j3d.J3dThread.run(J3dThread.java:256)

or

java.lang.NullPointerException
        at javax.media.j3d.RenderBin.processTransformChanged(RenderBin.java,
Compiled Code)
        at javax.media.j3d.RenderBin.processMessages(RenderBin.java,
Compiled Code)
        at
javax.media.j3d.StructureUpdateThread.doWork(StructureUpdateThread.java,
Compiled Code)
        at javax.media.j3d.J3DThread.run(J3DThread.java:256)


Since these exceptions are generated in v 1.2 but not in v 1.1.2 or v 1.1.3
and since they don't trace back to a line in my code, they look to me like
errors in Sun's code. But how can I work with a buggy API when the source
code isn't even provided so that I can see where the errors are occurring?

I like Java and want to be able to use it and sincerely hope that the next
upgrade is an improvement.

Raffi

===========================================================================
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".

Reply via email to