jMonkeyEngine.org

thanks for the tip. the debug shows that the scene mesh is normal, but the ghostControl still acts as though testing for collisions with a big box with length (length of the scenemodel) by width (width of the […]

There is no bounds, there is only collision shapes. Use physicsSpace.enableDebug(assetManager) to see them.

if that’s the case there must be a problem with the boundaries of the scene with which the ghostcontrol is colliding. I’m almost positive the ghostcontrol is checking for a collision with the scene’s […]

This definitely works, I tried it to create a more flexible character control in a prototype.

my intention when adding that local vector was simply to test something out. thanks for the heads up though; I’ll remove it now since it no longer serves any purpose.
I also took your advice and set the […]

Do you use native bullet? Its not working 100% yet. Also do you add the GhostControl to the player spatial?
Edit: I just see you don’t but move the spatial manually. Note that overlappingObjects is only […]

I attempted to create a second ghostControl to follow the player and record collisions, but this doesn’t seem to be working quite right.
No matter where I moved the player, the ghostcontrol would read off 2 […]

The character is actually a ghostObject and a kinematic rigid body and does its own penetration checks. So doing this yourself should not be a big issue. Note that you mix two different collision systems when you […]

Thanks for the fast reply! I thought that might be the case, so I attempted to write my own basic physics, but couldn’t seem to get proper collision detection. I tried two methods, neither of which worked […]

I suppose you are using the character? Note that it doesn’t have “normal physics” but its own simple physics simulation. So you can’t really avoid this as the character is actually off the ground and falling. […]

@monkey_scratches_head said:
Happy days …solved the above problem.

Turns out the problem was at the linking phase (after the object file were created), caused by copies of the *.a files from another compiler […]

Happy days …solved the above problem.

Turns out the problem was at the linking phase (after the object file were created), caused by copies of the *.a files from another compiler that are copied into […]

Yes, it was the subtraction of click3d twice that was doing it. Thank you!

perhaps because you were subtracting click3d twice, and you were commenting out the second occurrence while commenting out the localize, I think the double subtraction was your issue.

Ah, that is a lot more readable and works to fix the problem, thanks

Is there a reason that the other code works on a Box-shaped Geometry without the normalization?

your direction vector looks a bit funky, try using this …

Probably because when I tried last it was not that way, good that it changed then

@EmpirePhoenix: I do not know why you say that all the time, the bullet natives come with the distribution, only windows 64bit is not supported at the moment.