Maybe it's important or maybe it's not, but although it crashes for me following Noga's directions, generally everything is working great.

The interesting(?) part is that if I add a Global variable, give it a suitable name and description, it doesn't crash, but the description is NOT visible in Event view (which it should) but it does show when accessing the variable from the system parameter selection list. So it would seem that it isn't quite rendering correctly for me, and as Kyatric pointed out, I'm one of those using an Nvidia.

In case it IS anything to do with the gfx card, I'm using the latest GeForce 285.58 driver for my card.

I just tried it with 8 copies and it worked fine. No glitches that I could see. I made sure to drag the target around for a while but they all still behaved themselves :)

I followed those steps from Noga and got the same error.

Lprez

It would make it much easier and quicker for those who can help if you save the project as a single file, upload it to Dropbox or similar, then post a link to it here.

Not a problem. Trying out things is the best way to learn, and using debug messages can be a life-saver (or brain saver) :)

If you add a new txt object and populate it with:

"FPS: " & fps & " TickCount: " & tick.Count & " DashCount: " & dash.Count

This just shows how many 'Ticks' and 'Dashes' are created when your events ask for it.

You'll see the problem instantly. When you press space, it's creating a bucket load!!!

Quick fix is to use Trigger Once as another condition on Event 8 and onwards.

Better fix is to redo that whole section for displaying ticks and dashes.

This is due to Origin points not correctly set for all your animations. For instance, the Idle anim has Origin set to bottom center, but the run right is set to center.

Also, some of the collision masks are a bit off :) Just use bounding box for now.

On opening your .capx, I noticed that the event sheet had been closed. Is this what you mean?

Just double click on it in the Project list on the right. I can edit fine.

Somebody

You want THESE from rexrainbow.

As Yann has said, there is an undocumented method to get the correct co-ordinates. In your case, change condition 2 to:

Sprite2 - Set Position to (Mouse.X(1), Mouse.Y(1))

and it should be OK.

Use Properties on left of screen: Size Make 1:1

I usually place all my events in Groups, then I can use the 'System: Set Group Active' event to enable disable everything in one go.