What needs to be done to get jME 3.1 final out?

Ali_RS · November 23, 2016, 1:30pm

Of course , we all are interested. That will be great. Thanks.

Vortex · December 9, 2016, 2:07pm

I have tested 3.1-beta2-b001-SNAPSHOT and all is working fine.

Thanks a lot.

Pesegato · December 12, 2016, 4:51pm

Almost…

Mee too!

nehon · December 12, 2016, 7:00pm

^ that was exactly the point of separating the SDK and the engine. This is a SDK issue and that should not impair the engine release.

pspeed · December 12, 2016, 7:16pm

Speaking of… I’m on tap to do a beta 3 release but @Momoko_Fan has some concerns about the bullet native builds, I think. (At least he did last time I chatted with him.)

I don’t know if anyone can help dig into that but his concern was that they seem like they are not really getting rebuilt, I guess. At least that’s what I remember from the conversation. He changed something in one of the C files, rebuilt, and ended up with the same output.

Vortex · December 12, 2016, 9:56pm

I have created another thread for the SDK discussion:

pspeed · December 12, 2016, 10:30pm

Apparently this is only an issue with the new 3.2+ builds… so not a show stopper for 3.1 which still requires that all natives are built and uploaded manually on each platform.

If I have time, I will tag beta 3 this evening… though I did hope someone would have time to narrow down the ‘attachment nodes broken when loading from j3o’ issue on another thread.

Ali_RS · December 13, 2016, 4:44am

Offering my two cents,
Maybe @erwincoumans can help with build problem. He is working on bullet library and is very active on github erwincoumans · GitHub.