Under the cover of night, early Monday morning, version 3.3.0 stable was birthed into the world.
I will let someone else write up a deeper post about the highlights. The full GIT changelog difference between 3.2 and 3.3 is on the github release page, found here:
The various jars have been uploaded to bintray and should be available through jcenter: org.jmonkeyengine - Maven - Bintray
Thanks 
@ItsMike54 are you interested in writing a blog post about this release?
In addition to the detailed changelog, Paul posted on GitHub, I also have a copy of Nehon’s Google doc one to keep highlighted changes (that probably would be nice for a blog post) . It doesn’t include beta-2 and stable yet, I will see if I can update it tomorrow.
Also it will be nice to announce it on JME’s Twitter page, not sure who is behind it though.
Sure I’ll try to make a new one.
I’ll need to ask Jayfella on Discord, if I can’t find him you can ask him directly.
Thanks so much 
Note, we want to include most highlighted changes that have gone to JME 3.3 in the blog post, like new Animation system, Java 11+ support, Android OpenGL ES 3 support, Gltf morph animation, tons of physics bugfixes, and … You can find them all in the google doc change log I posted above.
Awesome, thanks, do we yet have a new SDK to brag about too, or is Dark still working on it
Note, SDK is completely separated from engine releases since a long ago so it is better to not mix them, for SDK releases you can have separate blog posts.
I don’t know the exact schedule but I’m sure it will follow soonish. So huge technological upgrade there as an IDE as well as the new version of the engine bundling, it is important to get it out (but in presentable state). I’m sure it is still the first contact to the engine for many and as such it is an important piece of the ecosystem!
@pspeed Thank you so much for leading the way in this release Paul. When I say this, I think I speak for everyone here, we really appreciate the time and value you add to the community. JME 3.3 was one crazy yet fun ride, thank you so much for being the driver!
Time to edit the gradle build files for all my projects and change them to use the new stable 
@Jayfella, as I said this morning I would whip up (carefully) a new blog post announcing the new release.
So I should have an “interesting” and professional article , check the PR here.
And I have not said it yet, your awesome @pspeed! Let’s keep this engine rolling!
Thanks, @ItsMike54,
regarding this
a new animation system called Monkanim,
please remove the “Monkanim” from there, it might cause confusion with another animation system that Nehon had done before this one.
Also, you could include some more in the change log:
like bumping to LWJGL 3.2.3, supporting Morph animation, support Light Probes blending in PBR, Support Sphere Probe Area and Oriented box probe area in PBR , , Support for AmbientLight in PBRLighting, Addition of DynamicAnimControl, lot’s of physics bugfix, lots of JavaDoc improvement, …
Ok, I’ll make some changes.
EDIT: DONE!
Is there a proper introduction to the new animation system available? That could be linked to the blog post even…? As a long time jME user and forum stalker, it is quite a question mark for me too. I only know it brings Morph animations. But what else and how to convert from old to new etc.
Yes, there is one that Nehon wrote:
JME 3.3 loads it automatically by new animation system when loading a gltf models.
And for converting old models you can use this:
AnimMigrationUtils.migrate(model);
@ItsMike54 in case you like, you can also create a new blog post for this as well. Mostly you need to copy-paste what Nehon said, but please do not use the name “Monkanim”, just call it the new animation system.
Actually I always wanted to do a tutorial/video/blogpost on the new animation system but for that I wanted to iron out a few issues, but I never got around to that.
Seriously dont you think it’s time you just gave up al the rubbish, I used to be a big fan but after years and years and years of tinkering you still cant release 1 single version of the SDK that just woiks. Its embarrassing. Just basic things like android sdk selection, the stupid error that comes up about xcode when you are on a pc, even the plugin libraries sources are still wrong and dont work. WTF are you on about with STABLE?? you are having a laugh. I’ve spent 4 year writing and app in jme and got it working on android and ios and windows and linux so it is possible but nothing just works out of the box. you keep updating it and making claims about it being stable but it NEVER NEVER EVER is. I would just give it up and accpet you are not cut out for producing a complex piece of software like this and with the most basic things that still dont work on a standard install is a joke. I wrote the equivalent in UNITY in 2 weeks and everything works. I know you will delete this post but if as least 1 of you so called experts get the message I will have done my job. SERIOUSLY GUYS GIVE IT UP AS A BAD JOB!!! jme-ios some json libraries. WTF happened to the ios build. dont bother telling me it’s me who doesnt know what im doing. Ive been developing for 30 years and this is just going no where. Android sample app type doesnt even add the chooser source code so you cant run or compile it???
The SDK is a separate project.
Can I download it and give it a try? It sounds phenomenal. Is it Java-based or C based?
Maybe you can lend your experience to the totally separate SDK project and help get it working, too. Sounds like it would be no problem for you.
JME IOS support is experimental. It’s looking for someone to manage it if you want to try to fix it.
This sounds like something to with the SDK also. You may want to submit a bug to that project.
Yes Paul, I accept that you have been involved with this for a long time and have took offence by my rant but its true that the most basic errors are still there from years ago. I am talking about the SDK not the engine but unless I’m supposed build from source or integrate in Netbeans myself then the SDK is essential especially for someone coming to it new.
I’ve got 4 apps on googe play. Chatter Games is done with JME and took 4 years. I had to write most of the android stuff in Android stuido because the android integration is severely flaky. in IOS I had to write all the UI and even sounds in XCODE because JME just never worked. I even spent months compiling the bullet sources in XCODE to get it working on iOS because the ios is still is alpha for over 7 years (probably longer).
What I’m saying is, how do you expect a newbie to come to this and build your comunity when the basic standard download doesnt work without a load of messing around with it.
Create a basic game and try to select the android SDK folder, it doesnt recognise it. Maybe its the version of android sdk ive got installed but who knows.
The potentially could be an amazing piece of software but it still not stable enough to call it version 1.0 never mind 3.2.2stable.
JME-IOS.JAr is completely screwed up and has got json librraries (spelt GSON for some reason).
Why does the plugin update check still not work after over 7 years of failing?
Checkout Chatter Games. It’s shows how good JME potentially can be but you need to concentrate on basic fixes and forget new fuinctionality for a while.
The other 3 apps are on Google Play called Wavey Ball, Baileys Holem and Nice Cans all done in Unity in under 3 months. No it’s not Java but so what???
Oh, I thought you said you rewrote unity in a week. It makes more sense now.
Yes, the JME SDK will always lag Unity because it has part of one person working on it instead of a paid team. That’s why we broke it off into a separate project… hoping that having its own release cycle, etc. would attract more developers. But it’s way easier to complain about it than to fix it so that’s where we stand there.
New users can create a project from a gradle template in a few minutes and get productive. Yes, it increases the minimum level of knowledge necessary to use JME but JME was always deceptive here. JME is a Java developers tool and you must know Java already to use it. From that standpoint, the SDK (in anything short of a Unity clone) will always be a disappointment to “new users” who don’t know Java. Point-click only gets you so far.
GSON is Googles JSON library and is used by gltf support in JME.
Anyway, I know they are looking for help on the SDK. You should join that team and contribute patches and stuff.
Ok, i didnt know that GSON was Googles JSON. So fair enough.
Why are you doing it as 2 seperate projects then? If you integrated the engine into and built the SDK each time then you wouldnt necessarily need to know how to build from gradle or even know any Java to start with.
Yes, I accept it’s for pre-existing developers but why limit yourself to that? Get new people involved who can use it from day 1 without knowing anything about gradle, java or anything else. Just provide a working set of samples (which not all do) and you will grow the community much faster.
As I said, I’ve been a massive fan for years and it’s a shame that the android build in the SDK doesnt work out of the box, now iOS doesnt have a hope of working as it stands.
I can’t even add libraries in the SDK any more.
To get more people in the community the android and ios has to be nailed in the SDK then you will see massive growth. As it is, its far too niche to get any real expansion.