edit@ R0J0hound The Prominent example doesn't seam to work https://www.dropbox.com/s/9286l0hy9pp9etk/tst.capx?dl=0

I fixed your capx: http://1drv.ms/1P1WOhr

You were doing various things wrong.

You set the joint at 0x0y of the layout(not the object).

You also have to move the object to the pathfinding object first before connecting them I think.

You had the object all on the same physics layer, so they were colliding.

I also, changed the joint type to a dampened spring, adjust the mass of the blue objects, dampened their velocities so they don't stay springy..

Also changed them to circles which should help with collisions, but might be fine either way.

..You might also want to consider putting these into a family and put the physics behavior on the family, in-case you plan to have multiple sprites/objects using physics together.

setting invisible won't draw the object, but if it is set visible and has opacity set to 0, it will still draw it even though you won't see it. Setting it to invisible is better for optimizing.

I'm unsure of the purpose of the force though.

force was just to negate gravity, but I suppose the gravity could be turned off instead. Could probably also use different type of joint if you want it more springy. I don't know what would happen if you have multiple objects trying to pass each other, etc. They would probably bump into each other and try to get around- so a circular shaped physics object would help prevent them getting stuck. You could probably stop the path movement if a physics object gets too far away, to allow it to catch up, or even perform some other operation to walk through other objects, like changing the physics group it is in temporarily.

I just tried and found a way to pull the physics object, I posted it in your other thread megatronx

You can attach the physics object to another physics object via a joint, and move one like so:

also make sure the objects don't collide with each other.

Then you would just move the object that needs to follow a path, and the physics object attached will get pulled.

edit: the 10*sprite2.mass stuff should be 100 instead of 10.

can't check for new posts anymore. just shows spam:

heh.. look at the graph on the forum main page that shows the number of posts in the last 30 days, and it has skyrocketed the last day. The forum is flooded.

— , That's why I said make a game that will sell first.

Ah cool, thanks for breaking that stuff down, I think I'm grasping the situation a bit more.

This chipmunk behavior is really great, I have had a lot of fun experimenting with it and I'm looking forward to any new progress you make with it!

Just thought I'd mention that you can do loopindex("loopheight") to get the value of a specific loop. That way you won't have to store those values in local variables.

I think the implementation of those two lines updates the two objects that collided. I don't think it relates to any joined objects in that case. At least, that is the impression I get.

A list of situations would be interesting- the only place I've ran into the problem has been when objects are colliding, but I suppose there could be other situations too.

Maybe I've ran into the problem in other situations but didn't notice it or maybe I overlooked it.

Yea, I agree, this would be a useful feature.