Animated Picture Collision Issue

[crusher]

There seems to be something very strange the way APO is checking for collisions. Collision detection works differently depending on if the APO background color is transparent or not. I guess this might have something to do with box/fine collision but it doesn't seem to work as it should...

The second collision problem appears when you change the hotspot location. It seems the "collision box" moves to a completely different location than the actual image.

Small example application of the problems:
http://sites.google.com/site/crushermgs/APOprob.mfa

It would be foolish to assume that this problems is not because of my own actions so I'd be glad if someone could help me here. Thanks!

[DanielRehn]

I don't believe it supports collisions at all o.0
I'll look into this!

[crusher]

What really? Heh that's strange. Well any chance it will support collisions? It would be pretty useful. My other alternative is to use a custom made "collision box" but then I'd need fastloops to check through all objects and that's way too slow.

Thanks!

[UrbanMonk]

oh, I'd be interested in this also.

I'm about to use this object for something.
I've done tests with it and it is significantly more resource intensive than regular active objects. It would be cool if it could be optimized more.

It seems odd since actives run the same speed even when you load outside images into them. 'Cept the difference with actives is that the loaded images replace the image in all the active objects and not just one instance.

[DanielRehn]

This object uses a completely different technique than the active object in order to be able to load and animate spritesheets and such.
You can't really compare them like that

I'll look into collisions!

[UrbanMonk]

Whoops. Sorry didn't mean to insult you! I'm sure it's as optimized as possible. I was only guessing.

Does it support HWA?