Hi,

I actually got some problems to understand clearly the controller system :

To have physics interaction , an actor (static or dynamic) have to have the world physics controller attached


But when there is an actor attached, it's not possible to move it manually (i.e with a RelativeTranslation on the node).

So here is the question, if I need to have a static actor like a SimplyCube, that interact physically and can also be moved manually, what is the best methods ?

I've looked for the way it's done in the NanoConcept source, but I haven't succeeded at loading a simple xnb object.

I'm also looking at the simplest way to raise en event when a specified physical object is touched by any other object. There is plenty of methods intersects but that are much more complicated to use. Will a simple event be available for the release ?

Best Regards,
Thomas B.

Hello,



When a PhysicsActor is attached to a node, it overrides at each update the node pose. The best way to move "manually" an actor for now it's to apply force (keep a reference to PhysicsActor.Base and cast to IDynamicActor).

We are looking for a better solution to provide some kind of "static" actor (a controllable physics shape) in the release version.



If you have encountered problems with NanoConcept, please feel free to make a specific post, we may help you (and maybe correct some problems).



There is an "filtered event" on PhysicsWorld class to get collision notifications between two actors. You can also use physics raycast to easily pick an actor in the physics world. The NanoConcept demo 2 that is coming soon will demonstrate these methods.

Regards

Thanks, works perfectly.



Still got some problems with that,
I first tried to keep the PhysicsActor sent by the World.AddActor methods,
then casted the PhysicsActor.Actor to a IDynamicActor but the Actor seems to be null.

I also tried the World.Base.AddActor that actually give me a usable Actor but not a PhysicsActor that I need
as a node Controller.
I probably missed something, thanks for your help.

Regards,
Thomas B.

It's the good way but there are some "hidden" behaviors that could make the problem complicated. PhysicsActor is the class that bind the physics actor to a SceneNode. Basically, it's an INodeController that gets the actor position in the physics world to update the node position in the graphical world.
As we want the physics actor to be initialized with the node position, we create it on the node first update. The algorithm is :
- node is created with a position
- PhysicsActor is created and attached to the node
- First Update : underlying actor is created in the node position
- Other updates : node position is overridden by the actor position

So to apply force on the underlying actor, you must wait the actor creation. There is a bool properties "IsActorCreated" that keeps the creation status, so if you keep a reference to the PhysicsActor, you should be able to add force as soon as this property is true.

An other approach (which could be "cleaner"), is to subscribe to the filtered event ActorAddedFiltered on the PhysicsWorld that will be raised when the actor is created.

In the release version, there will be a third way with an "ActorCreated" event directly on the PhysicsActor class (it's hidden in the beta).

Regards