Hi!
I recently started on a project where I need access to a 3D engine that works on both a computer and android. Of course, jME popped up as the ideal alternative.
Since I need access to the computer version today however, I'm wondering how I should go about doing this.
My qualms lie within how the libraries differ. Searching the forums I could find little to no information on this, so I thought I'd register instead and post a question.
As I understand it, JME3 is in an alpha state, and I'd be better off starting the project in JME2. If I decide to do this, would it be painful to later on move to JME3, or could I expect that the transition will be easy enough to make it worthwhile to work in JME2 for the time being?
I'm expecting to make use of, among other things, StandardGame with its states, shadows, reflections, multiple inputs, particle engines and more. I'm also expecting to at some point define some additional input systems that may somehow use the existing input base in JME under com.jme.input. Will I be in trouble, or should I go along with using JME2 and transition later?
Thanks!
Linus
Many things are very similar in jme2 and jme3 but other things are very different. In any case I'd suggest you design your game engine in a way that makes it easy to exchange the graphics engine. This also makes your code generally more reusable. Also, you can advance your engine in other parts and "wait" for jme3 to bring performance/features that are not available in jme2. Still, jme2 could be everything you need so I suggest you start using jme2.
Cheers,
Normen
linusmartensson said:
I recently started on a project where I need access to a 3D engine that works on both a computer and android.
normen said:
Still, jme2 could be everything you need so I suggest you start using jme2.
If he wants Android he's going to need jME3 :D
sbook said:
If he wants Android he's going to need jME3 :D
d'oh
Wella ctually I already moved to jme3 if you understand that tehre are some huge interface changes in the progress of jme3 you ca already buidl working stuff with it.
JMe2 - Jme3 i guess is painfull, cause the cahnges in Renderstate, Supportet Formats, Animations and pretty much everthing else except quaternions and scene graph.
At least I found it easyser to restart from sratch than converting m stuff. Also this way only you ca make use of some jme3 only stuff, like background thread model loading.
So if you don't need a already fisniehd engine and are flexible I suggest to use jme3 from start at the cost of a higher maintance untill jme3 is kinda finsihed.