With v3.2.3 of the engine out, it’s time to discuss why there hasn’t been a v3.3 and what (if anything) should be done about it. Here’s my understanding…
The driving feature of v3.3 was to be the new animation system (aka
com.jme3.anim aka MonkAnim). Since @Nehon became inactive, there’s been scant activity in that area. Meanwhile, the
master branch of the repo (on which v3.3 would presumably be based) deprecates the old animation system (aka
Being satisfied with (and deeply invested in) the old animation system, I’ve avoided using the
master branch except for bug fixes. I don’t know how usable or complete it is.
Animation is central to jMonkeyEngine, and the transition to the new system looks daunting. It’s not a one-person project. It will require new tests, tutorials, and documentation. For the SDK to support it, major changes must be made there too.
- Is anyone using the new animation system?
- Has anyone successfully transitioned an existing project from the old to the new?
- Should we release v3.3.0-alpha1 out of
masteras it stands?
- Should we strip out the new animation system and release a v3.3 that’s mainly bug fixes?
- Is there some other new feature that might motivate a v3.3 release, and if so, what?
- Does anyone have both the time and the motivation to champion a v3.3 release?
Here’s an old roadmap (from 2014) that might give people ideas:
Here’s an incomplete list of issues and pull request that currently target v3.3: