I'm a beginner with construct but I don't think it has much to do with construct itself - it's the way you're implementing your particle effect. The thing is you're going to have to keep all of those frame images inside your video memory in order for them to be played on demand.

All I can think of is to reduce the size of the image directly like you mentioned, reduce the amount of frames being used, or render your particle effects inside construct. Can't you resize them inside of an image editing program? Even construct's built-in one would work.

Also, I'm pretty sure the amount of colors in the image is really only important in png compression. When the image is inside video memory it's in raw bitmat format. Someone correct me if I'm wrong.

Edit: Nevermind. I'm too slow. lol

Actually I figured out what it was. My hotspot was way off center and that was causing it to do weird stuff. Thanks for trying to help though.

Hey, just wanted to pop in and say thanks for the great plug-in!

Hello, I'm having a little trouble with the physics engine. I'm using several copies of a single sprite object for my terrain. I have it set to immovable and the collision mask set to the bounding box. Now this works fine if all of the sprites are the same size. However, the results get wonky if I have terrain sprites of different sizes all over the place. The collision mask will still exist but it wont be anywhere near the sprite.

<img src="http://i46.tinypic.com/23r333a.png">

Using the bounding box works great for the platform movement though. Is this a bug? Should I just make a different sprite for each size of terrain I want?