Hello. I have been working with java3d for about 2.5 years now. I am actually coding a 2d/3d compositing (video, images) application with sound in Java. This application embeds a 'universal' tree api that can see java3d plugged in to render 3d images. Java3d is also used in the software for visualisation. It is also used for a 3d painter that is in a plugin of the application. I also work in a company doing simulators. After some demos of java3d i did to them they wanted to know more in order to replace Inventor for rendering. Also, i had utilities in the pipe for them, to do automatic imaging and positionning systems for railway track recognition (from running videos) Along that, i have some landscape stuff done to stress the API with zillion polygons.
My application is actually not pushing the 3d side, waiting for a definite solution about java3d. Depending on what happens in the next weeks (months, if something encouraging takes place, even slowly), i'll switch to an other (open source, this time) tree graph api, or stay java3d. For the train company, researches on java3d stopped. The way that SUN let the API down reminded them stories with Microsoft, and they did not want to play with guys like that anymore. Thus, java is now completely excluded. I only have one thing to say to sun: bravo, you're really smart. This just thrown lots of discredit on the whole java world and yourself. You're now seen as unreliable as Microsoft. It was not easy to do, but you achieved it. :( (okay, that makes more than one thing, but i now feel better) I would like, as most of us, the scenegraph API to be open source, with a central 'authority'. Scenegraph API should be seperate from the rendering layer (jogl as a reference implementation). Everything should be open source, but still, someone, only an organisation or company, should handle the SPECS. What is important in Java3d is that it is a spec. Preferably, Sun should keep on maintaining the spec, giving authority to an other entity to release the reference implementation. Having Java3d as an official sun spec will help in keeping (restoring, actually. see my small rant) its weight for imposing it to stupid project managers. (yeah, you know some, i bet.) I loved java3d for its simplicity and power. It let me do what i needed with very good performances, and easily. I would preferably switch to a java3d compatible api, in order not to loose too much time, thus xith3d for the moment. Best luck to you, for the benefit of all. =========================================================================== 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".
