I am in agreement with Herkules here- Java3D is a 3d engine- it a whole lot of functionality, but not much of it really appeals to less committed programmers and there is not much in the way of simple game-oriented tutorials for it to introduce less experienced 3d programmers to how it works. What you are talking about is actually a 3d game that ships with a bunch of editing tools, it seems to me. Unlike scenegraph-oriented API’s like NetImmerse, used for Morrowind, Dark Age of Camelot, Freedom Force and many others? Sooner rather than later would be better before too many people get frustruated and give up.Īnd scenegraph-oriented APIs like Java3d are not very well suited to make games with them IMO.
#Java 3d engines software#
It would definitely spur development of software based on J3D because more people would have more satisfying results in their efforts because they will understand the good and bad practices with using the API…There’s books written on EJB-Antipatters, we need the same sort of thing with J3D.
Getting to my point: We need someone in the know who has a proven trackrecord of using the J3D technology to lay out what J3D is useful for and where it is lacking…so that developers can understand where the shortcommings and pitfalls are and won’t produce crap because the system isn’t built to support it. There have been good J3D demos, and bad ones (Just like EJB based apps). Enter J3D: Designed to model ‘universes’ with an API that can handle anything and everything imagineable, but an implementation that does a few things very well, and other things need work. IMO, J2EE attempted to do too much in design, but did very specific things well in implementation. Unfortunately, no one at first really understood the best applications for the technology, and thus made the technology look bad because it was misapplied.
#Java 3d engines series#
How can I make this comparision, you ask? Well, in J2EE’s case, they developed a whole series of technologies that was made to save the developer the trouble of figuring out persistance, managing transactions, object pooling, etc all sorts of other stuff that should help make applications run fast and stable.
Hey, not to de-rail this thread but I have to say, looking at the comments made here, I feel like the problems that exist in J2EE (specifically EJBs) are emerging in J3D.
0 kommentar(er)
