Hey monkeys, I just tagged the 3.2.0-alpha1 release
You can see it here Release jMonkeyEngine 3.2.0 Alpha 1 · jMonkeyEngine/jmonkeyengine · GitHub
The log could be better but as always… but you know…
It should be available soon on jcenter so you can update the version in your gradle/maven build.
Please report any issue, I’m planning to have a week cycle so alpha 2 is coming on next Tuesday.
EDIT: artefacts on jcenter: org.jmonkeyengine - Maven - Bintray
Support for opengl Instancing
And what exactly is the instanced node in previous versions of the engine then?
haha I thought it wasn’t there in 3.1…
EDIT: fixed (of course it was a test to know if you would read it…)
Well I was half hoping that it was the real implementation of it. The instanced node is known to make fps even worse.
I mean have there been any cases of anyone using it to any real gain? I remember at least two threads asking for help with it, paul commenting “uhh this is for high vertex meshes dummiez” and after much discussion the thread ending in something along the lines of the entire thing being implemented wrongly in the engine itself.
My tests a while ago also only showed fps loss so I’m not sure what’s up with that.
Cool. Its time to update libraries and test the thing out. 
Wow, I’m not already finished all planned things for shader node system 
Well you probably didn’t use it for the appropriate use case. A lot of people see this as a silver bullet but it’s far from it. Most of the time batching will be better.
It’s nice when you have many times the same complex and non animated model to draw…
Edit : about the wrongly implemented part. I don’t really know. Let’s say there has been divergences in the approach in the team but I was merely a spectator.
That’s what people always say, but wasn’t there a thread by @Ali_RS a while back when he tried to instance a forest thing? That didn’t work either.
Well anyway not really the place to discuss this. Feel free to dig up that post you’re talking about in another thread and we’ll talk about it
Why do you care you use master anyway 
I have tested the Binary Importer / Exporter (Issue BinaryExporter/Importer · Issue #770 · jMonkeyEngine/jmonkeyengine · GitHub).
And it seems the issue has been fixed. 
in 3.2.
cool
It isn’t a good option, so I would like to be based on the stable release of jME.
Well we’ll see the AST conversion of the generator for 3.3. The system is stable and I don’t want to change it before the release.
Yeah, but I think about other things in the engine
Well there is always room for improvement and if you always wait for the next change you never release.
Nice! Thanks! There is an alarming problem though. It downgrades Nifty from 1.4.2 to 1.4.1. Compared to JME 3.1. Is this intentional?
mhh? nope it’s not
I will check that out.
I checked from here:
And compared it to 3.1
It looks like a change that has never been back ported to master…