Problem is in the title. I know it’s supposed to, after searching about the issue, but I can’ understand why mine isn’t doing that.
Here is the main code I think looking at would help:
[java]@Override
public void setSpatial(Spatial spatial) {
super.setSpatial(spatial);
behaviourOnLostTrack = spatial.getControl(IdleMovement.class);
behaviourOnSpotted = spatial.getControl(EnemyMoveAttack.class);
character = spatial.getWorldTransform();
ghost = new GhostControl(new BoxCollisionShape(new Vector3f(1,4,6)));
Node position = new Node();
position.addControl(ghost);
position.setLocalTranslation(0,.5f,.5f);
((Node)spatial).attachChild(position);
bulletAppState.getPhysicsSpace().add(ghost);
rootNode.breadthFirstTraversal(visitor);
OnEnable(spatial);
} [/java]
The ghostControl here is attached to a node that I use to position it slightly off center of the spatial itself (can detect farther in front than behind it). Does the problem lie in the parent node hierarchy? Also, what’s doing the rotation of the spatial is a call to lookAt() with a certain target in a different control attached to this spatial, in case that is useful info.
Ooh, and considering I haven’t really seen it rotate yet, when it does, will it rotate in according to the offset in position, or rather, its own center axis of rotation?