i30817,

There is no runtime cost associated with throwing a normal exception in this case because the user is never supposed to invoke this method. An assert is simply not appropriate in this case.

jezek2,

Please throw a descriptive exception instead of assert(false). For example:

throw new UnsupportedOperationException("TriangleMeshShape is only for static geometry, use GImpactMeshShape instead");

Gili

Hi Jezek2,

Why does TriangleMeshShape.calculateLocalInertia() contain ? Are we never supposed to invoke this method?

Thanks,
Gili

For example, I am told that the code will throw some magical exception that I may not catch or it will break continuations. The whole concept of continuations twisted the accepted workings of Threads. It's a non-standard concept as you pointed out.


I suggest introducing the usage of Future and CompletionHandler instead. This will allow users to write sequential use-cases as you described without the kind of "magic" introduced by continuations. For code:



This is essentially what you're doing with continuations but it's a lot more explicit and is still quite readable.

Gili

Looks nice, except for the use continuations. I suspect most of you probably disagree, but I am uncomfortable with the concept. I love the readability advantages of of continuations but the resulting implementation is a no-no in my books. Anyway, just my 2 cents.

Matzon,

JMonkeyEngine: http://www.jmonkeyengine.com/jmeforum/index.php?topic=9247.msg71503#msg71503
\-> "Official developer activity has been incredibly low. Also, there is no clear, cohesive future direction for the technology."

Xith3D
\-> No commercial support, decent API (but not great), and I have seen some documentation holes in the Javadoc.

Ardor3D
\-> Looks very promising but seems to be immature at this point.

Please excuse my pessimism. Both JME and Xith3d are excellent engines, I'm just pointing out the problems I've found with them. Are there any other engines I should take a look at?

Thanks,
Gili

Hi,

I'm looking for a 3D Java gaming engine that has the following features:

- Portable across Windows and Linux
- Clean API and solid documentation
- Mature (3+ years old)
- Active community
- License allows commercial use
- (Optional) Commercial support is available
- Decent performance (our environment is 2.5D... it is rather simple)

I look forward to your suggestions.

Thank you,
Gili

The issue, as far as I see it, has absolutely nothing to do with how long it takes to implement a feature. What I am saying is that we should have a schedule for what will happen in each version release. We don't actually need to estimate *when* that release will come out, but at least we will prioritize what to do in each release and work toward a common goal.

Gili

Guys....

All mature open-source Java libraries I've seen to date had one noticable thing: a schedule!

I believe that Xith3d is floating in limbo because we have no public schedule as to where we stand today, when we plan on releasing the next 2-3 releases and what elements are scheduled for each release.

Without a schedule you cannot prioritize. And without priotization, you will get nowhere fast... like has been the case for the past few months.

Just my 2 cents...

Gili

Hey guys,

This is a nonsense discussion. We can upgrade the codebase to JDK 1.5 immediately and use RetroWeaver (http://retroweaver.sourceforge.net/) to convert the classes to JDK 1.4 for Mac and other operating systems.

Hi William,

   So you're saying that Xith3D is ready for production (commercial games -- all major features implemented)? For the minor features which are missing you're saying I can call OpenGL directly and its output will integrate seamlessly with the Xith3D output. Is my understanding correct?

Thank you,
Gili

Hi,

    Before I try using Xith3D for production usage, is it missing any features that OpenGL/DirectX have? Are there any known issues with it at this time?

     As well, what is the portability of Xith3D? Has it been ported to any gaming consoles like PS2?

Thank you,
Gili Tzabari