In the number 4 case the calculated values would have to be relative. You could scale the entire triangle bigger and smaller and keep the same angles. So in that case you're not truly solving the triangle.

You could also give the ball an invisible hitbox that's slightly bigger than the ball itself. You'd have to set the position of the hitbox to the position of the ball in an always event. But then you could trigger on collisions between the hitbox and bricks. (Basically this would be like using a detector.) Maybe that's less of a detour or maybe it's more.

You could also check out Deadeye's Platform School tutorials and see how he uses the offset command. I think it first appears in part 4 when he's dealing with the slopes.

Very nice addition to the series Deadeye.

I have noticed that Charlie appears to speed up when he is running on slopes. His horizontal speed remains the same, but he gains vertical speed. So his overall speed gets a boost. Is this something that should be handled by Construct or by the programmer?

must admit, IK is perfect

...but only if you can understand things like:

"Set Angle to global('AC')+acos((B.Width^2+global('C')^2-A.width^2)/(2*B.width*global('C')))"

As a rule, I don't think Quazi posts anything that's readable to humans.

Newt do those scripts work in Photoshop as well? Or Deadeye could you post your Photoshop script(s)?

Interesting. I never would have thought you could do that sort of thing.

I'm not on my Construct computer right now ...

So in other words that's just off the top of your head. Right. The only thing I can get off the top of my head is dandruff. *sigh*

Ah, thanks for the screenshot. That looks much better.

It's not done, in progress, etc etc.

Okay, so it's in progress. But something tells me this isn't what it's supposed to look like.

<img src="http://willhostforfood.com/users/stainsor/screen1.png">

keep up the good work!

Post it for us too!