For me it looks like, that setJumpSpeed() has no effect and setFallSpeed() isn’t getting faster if I use values higher than 100 or so. I also played with gravity. What am I overlooking??
Well, I just wanted to migrate my projects from jME 3.0 to 3.2.4, but it seems I’m stuck with such stupid problem…
Any help appreciated…
PS: The game I wanted to migrate had gravity = 60.0f, but this makes the player fly, so now I use -0.5f. Obviously there was a change in the API.
Sorry, still using bullet-native… forgot to delete the .dll in project root.
But now complains about missing .dll. Adding jbullet didn’t do the trick. Let me see if I can track this down…
UPDATE: I forgot jme3-bullet.jar and vecmath.jar. Now all methods require different parameter values… Obviously jbullet and bullet-native are out of sync.
I moved everything around, set before gravity, after, set before physics after, set before gravity before physics, blagh blagh blagh and it shows it is set every time but it never changes the effect.
When we can reproduce that it should be an easy fix.
FYI: jme3-bullet and jme3-jbullet should be exchangeable but it goes like this:
JBULLET: jme3-bullet & jme3-jbullet (it should contain all the jars like stack alloc and vecmath!)
BULLET-NATIVE: jme3-bullet & jme3-bullet-native
You usually only interface with jme3-bullet, so nothing should change.
Edit: Looks like a serious bug, please try jbullet, because the issue stems from native code:
BetterCharacterControl uses forces to fake jumping.
Actually, you shouldn’t include both jme3-bullet and jme3-jbullet in the classpath. They contain different versions of the same classes, so if you include both you might not get the JBullet versions. My recommendations for desktop developers would be:
JBULLET: jme3-jbullet (it should contain all the jars like stack alloc and vecmath!)
BULLET-NATIVE: jme3-bullet & jme3-bullet-native
Oh I didn’t know that, I thought jme3-bullet are the abstract interfaces like RigidBodyControl and jme3-jbullet and jme3-jbullet-native provide their implementations
bullet-native:
Setting jump speed does not change anything.
Setting fall speed to 0 means no falling, 100 or so means maximum fall speed, but I want even more speed.
jbullet: Same effect.UPDATE:Have to repeat test, lib/jar is broken, see below.
Side note to jbullet: I had to add both libraries: jme3-bullet and jme3-jbullet.
Otherwise there are unresolved references.
And in my Eclipse IDE I have to add vecmath, but you were talking about libraries, not jars. For Eclipse I have to add all jars of a library.
My guess: the bug fix covers the API differences between bullet and jbullet. So same values have same effects.