Yeeeeehaaaaah! Well done, congrats and a big thank you to all involved 
Seriously awesome updates guys!
I am really looking forward to these performance improvements and new features.
Could you post your J3o please and tell us more about the context of the project?
Also do you have an error when trying to load it in game?
I really love the work made for this version. Congratulations to all that make this possible! I also want to mention that in this version you can try the new Nifty-Editor! I think that in the previous wasnāt availableā¦ or was it? . Anyway I hope to use the IDE soon for some side project! Great work again !
Awesome! 
ā¦very nice 
Great! I really like that you put iOS in front of all other features. 
Iām very excited about that, because yesterday I found out that the iPhone 6 zoom mode brings up new resolutions. Damnā it! So Iām really looking forward to the new rendererā¦
I donāt think I saw the new nifty editor in the features list
Iāve been porting my project to 3.1 for the performance improvements and have noticed a few things. Iām still tracking down the root cause behind a few of them but I noticed when I start my multiplier server it sets a flag on the serializer to block changes, but when I start the client it tries to register a few more jme classes and throws a runtime exception āSerializer registry locked trying to register classā. I register all my classes well before the server is started and iām not sure what changed with the serializer. I noticed that if I manually call the static method to unlock it that my server starts fine.
Thanks, that helps with the background for it. Iāll just disable the lock for now until the same instance start bug is fixed.
1 Like
Congrats on the 3.1 beta release! Its terrific to have another importer, fbx will be a wonderful addition to the capabilities of JME. But I have to ask, why get rid of the OgreXML importer? The fbx format is a proprietary format, owned by Autodesk since 2006. Has anyone taken this into consideration? Iām all for multiple importers, but to ditch an open format importer for a proprietary one seems like an unfortunate decision. If lack of developers to maintain the importer is the issue, I would gladly step forward myself to help continue supporting this format (alongside fbx of course).
I know my concern is mostly ideological, but that is primarily the reason I use JME3 over the Unity3D engine. Open source and open format vs closed source and closed format. I really donāt want Autodesk coming at me for royalties for the games I create, Iām poor enough as it is. 
(and yes, I understand that a released game technically should only use .j3o, but I get lazy sometimes )
As it currently stands, in JME, I have a fully functional blender->OgreXML exporter that supports everything I currently need and can imagine needing (skeletal animation, shapekeys, specular, bumpmapping, transparencies, I canāt think of something it doesnāt support honestly) for the forseeable future of my game development career (hobby). I beg you guys not to remove the OgreXML importer.
As for adding the fbx importer, I completely understand the desire to be able to use assets from Unity3D. Iāve had several game development buddies tell me how great the Unity 3D engine is just for its assets. Iāve rebutted with how great the JMonkey Engine is for its open sourceness (and great community!).
It will be awesome to be able to tell the Unity3D enthusiasts that we can load their content. Maybe Iāll be able to convert a few souls over to JME when the fbx format is fully supported.
The idea behind FBX is that we can potentially load things from asset stores directly without requiring the user to figure out a whole other tool suite just to do the conversion. (Blenderās Ogre exporter is not exactly user-friendly if youāve never used Blender beforeā¦ and even thenā¦)
I donāt think there are plans to remove ogre support but I guess the question is how much longer that exporter will be maintained by the blender community. Last I looked it seemed to be moved into some kind of āunofficially supportedā status or something. I know I had to go somewhere weird to get a version that worked with my Blender install or something.
Edit: in the mean time, you might want to keep an eye on xbuf and potentially test it occasionally (or offer some test models if you find issues). To me, that seems like the best hope for a fluid Blender to JME asset pipeline. Xbuf format ā A developer friendly game exchange format for 3d data
We didnātā¦ and wonātā¦
Iām so relieved to hear that, and glad it was just my misunderstanding
I had to go back to 3.0 to do Android development since for some reason it does not create what is needed for an android project and I canāt choose a target
For now I use 3.1 for desktop release only
Wait where is the features list? I guess I missed itā¦
I did some weird stuff migrating from 3.05 to 3.1 so canāt recall (and probably shouldnāt lol) all the steps I went through.
But it also didnāt allow me to target an android version either, like youā¦ canāt say if itās a bug because I kinda dildoed all the way.
In properties/android, clicking the āRun Android Target Configuration Utilityā button didnāt do anything.
After some jiggling, where I would (multiple times):
- uncheck / recheck Enable Android Development (with compile on save unchecked)
- clean and build
- resave the MainActivity file
ā¦ I was able to click that target button and from there, link to the android sdk and then choose a target and the mobile files appeared.
I have other problems with android on 3.1, but those might be simply me being an idiot, so Iāll make a post about that somewhere else.
Migrating to desktop 3.1 was a total breeze. And using tonegodGUI version from brainless-studios (thanks a LOT guys) made that lib work on 3.1 perfectly. And donāt get me started with the fact that 3.1 solved a visual glitch I had on desktop only, when using unshadedā¦ because imma gonna hoorah into everybodyās ears otherwise!
2 Likes
Do you have maven repository?