When I'm using the angle tween, how can I choose if the movement is clockwise or counter-clockwise?

Using families is a way to pick separate instances at the same time. It's pretty much the only way to connect two instances of the same object with a joint.

Ah, ok!

Thank you very much.

I'm doing a rope with physics and I'm trying to connect the pieces of it with revolute joint.

The problem is that I can't make the right piece connect to the other right piece, cause it's all the same object. So, I can't do picking.

I saw an exemple with families, made by Rojo, but I was trying do to something simplier.

So... to do the picking in this case, with all the rope pieces being the same object, just with families or do we have other option?

Ah, I see... sorry, I think I have issues with picking '.' hehe

Thank you very much for the help, this is exactly what I was trying to achieve.

Why not ? Just a Line-of-sight more. (rereading the question).

That's what i need to know

Have you tried to increase the cone of view of the cameras?

When there is more than one detecting you, the cameras don't work as they should. They don't act independently.

Hope this shows you 'picking'. And how to use 'else'.

https://drive.google.com/open?id=0B1SSu ... 3FDc0NYc00

Awesome! that's pretty much what I need. But how can I modify this to make the system work even if more than one camera is detecting the player?

Are you adding "force" or "impulse"? seems like impulse would be the right choice in this case.

I have sprites that are 'cameras' with lineofsight in my levels, to detect the player. When there is just one camera in the layout, it's fine. The problem is when there is more instances of the camera...

The detection if the player IS in line of sight works with all instances, but how can I make just the right instance of the camera detect that the player IS NOT in line of sight anymore? just inverting the condition "has line of sight" don't to the job for the right instance.

They way I've handled this is...might seem a bit of an overkill, but in my particular situation it worked fine. I have a pather object, which has the pathfinding behaviour - seperate from the real object I want to move. When I want to go someplace, the pather objects goes in that direction(NOTE: it is invisible and moves quite faster than the actual Object), updating its path frequently, and also leaving numbered nodes (set a var to nodes.cout + 1) on its trail on every now & then. Then I make the actual object follow the nodes (by updating its position by some pixels) always picking the lowest Node No, and destryoing each upon colliding with them. This way the pather can stop on every update, but as long as the actual object does not go faster than the pather, it would move quite smoothly.

Hope this makes sense.

CHeers

Ha! Thank you for the answer, it helped a lot!

That's a hell of a topic

Thank you oultrox and ashley!

Ashley , thank you for answering and posting the solution.

Indeed, that was the problem! the rotation speed. since my enemies are fast, they needed a highger rotation that ended up solving the problem. or at least that's what I think and I'm seeing, you can look it by yourself at this .capx I made with the rotation fixed! so anyone who went into this problem could get this .capx and see that actually it has a solution:

https://www.dropbox.com/s/wlbd7ugm4tch5 ... .capx?dl=0

Also, I've implemented a LOS to see that you won't be actually seeing them rotating that fast because you could adjust it manually by setting rotating object to no in their pathfinding properties.

and in this gif I'm showing the fact that my guys are following properly now. <img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt=":D" title="Very Happy">!

Thank you guys! you might want to pin this to the How do I FAQ. I didn't see something like this in that place.

Looking at this latest gif a question came to me:

How can we handle the guys entering in each other?

Bump!