Author
Topic: State of OpenGL ES2.0 support (Read 23745 times)

color isn't set by jPCT-AE unless you specify some vertex color, which is why it's always black. Try to set it fixed to white or something. I tried that with your code, but the result still looks kind of strange. So i've modified the shader slightly and set the light source to -20 instead of -1 (because otherwise, it's inside the cubes).

Thks for the info. I've already had this version who's working fine but I'm still undecided about the right engine for me.

In fact, I'm looking for a game engine with bone and pose animation support. I've tested jme3.0, libgdx and jPCT. All are good engine but jPCT+bone seems to be the more simple and suitable for my needs.

I've tested all of them with a modified simbad ogre3D model (I've added simple keyframe for lipsync animation). Here are the result in FPS with a Galaxy S/android 2.3.4 (Bone:"Dance" Anim + Keyframe Blending).

In addition, I've implemented my own library in C + NDK android for managing pose frame and keyframe animations natively in opengl ES 2.0 (Only one vertex shader computing Bone Position and Keyframe position at the same time).

It's working pretty well and it's fast (approx 30-35FPS) but some optimization are chipset dependent (Power VR) and It's a nightmare to deal with OpenGL graphic context (LiveWallPaper), moreover, I've got some nasty compatible issue with a few smart-phone.

So, I need to come back the right path using only android SDK. Do you think I can expect some FPS improvement with the new GLES 2.0 implementation of jPCT-AE ?

FPS most likely won't increase with ES 2.0. It might happen, if you write yourself some dedicated shaders that do only what you need. jPCT-AE's OpenGL ES 2.0 support relies on some default shaders, which might not be optimal in all cases.

Edit: You might get an increase if you would do the skinning in the shader, what Bones doesn't do. Somebody (not me... ) would have to modify Bones for that. I'm not sure, if it's worth it though. You can also try to use the libgdx-support of jPCT-AE (see the wiki)...it might help to increase vertex upload time, but i wouldn't expect too much (if anything) on a current device.

I've already ran it myself on an S2. It worked except for some texture problems with non-square textures, but that's a common issue with ES 2.0, which is why jPCT-AE already prints out a warning in this case.