next »

[Marvin Fröhlich]

By the way, we've decided to switch from jME to Xith for our engine, based on ease of use and very similar performance.

Hey, nice to hear that . Thanks for the info.

Marvin

EDIT: BTW: Which features, differences or whatever in detail were the most important things that made you most switch?

[rbivens]

Marvin-

We're already very familiar with the Java3D API, but we don't like the performance of Java3D. We like the performance of jME, but we hate the API. So, the logical choice is Xith!

rbivens

[Marvin Fröhlich]

We're already very familiar with the Java3D API, but we don't like the performance of Java3D. We like the performance of jME, but we hate the API. So, the logical choice is Xith!

Pure logic

['n ddrylliog]

Hmmmm. I went into my nvidia config tool and sure enough, it's locked at 60 Hz. I had no idea that fps could not exceed driver refresh rates, though. I have the option to change it, but only after the driver warned me that very bad things could happen to the hardware.

Based on this new info, I think I'll just leave it the way it is. 60 fps is plenty fast, and performance is excellent until I add hundreds of thousands of triangles.

Thanks Amos! (and Marvin, of course!). It's like you guys have a contest going on to see who can be the most helpful.

By the way, we've decided to switch from jME to Xith for our engine, based on ease of use and very similar performance.

Expect more questions 

Thanks again,
rbivens

You're welcome !

Great to know you did the jme-xith switch !