Hi all, not a big deal, but I posted the content of my presentation of FlyingGuns at JavaOne2003
https://sourceforge.net/docman/display_doc.php?docid=21208&group_id=99381
Hi all, not a big deal, but I posted the content of my presentation of FlyingGuns at JavaOne2003
https://sourceforge.net/docman/display_doc.php?docid=21208&group_id=99381
LOL! I particularly liked this slide:
So much for shattering Java preconceptions eh? :
Cas 
This was a Java-insider conference and I wanted to be honest! And you shouldn’t quote this site w/o the many other, positive ones!
Smoothness was and is difficult with Java3D, bc. frametime may unexpectedly vary. I suppose it has to do with the strongly multithreaded nature of Java3D. This has nothing to do with performance!
Sound in Java3D was hell! Never got it to work properly! I think there are many unfixed bugs there. The first steps are easy, but sometimes sound doesn’t stop anymore …
Memory leaks - yes. Many large primitive arrays. Sometimes we lost 10MB whenever reloading the terrain although bringing down the 3D engine completely. Still COULD be us… but we never fixed that. Don’t ‘Start a new game’ too often in FlyingGuns…
The unexpected issues have always been unexpected. Doing simple things sometimes brought performance down. I.e. the overlay system.
This presentation was made to glorify Java! See, in CONTRAST to common prejudices, even a flightsim is possible and can be done in a straight-forward way. And Java gives UNIQUE benefits. These are the points that should be mentioned 
When I talk to non-Java people, I NEVER mention the issues!