Hi, not sure what the rules are on bringing old threads back from the dead. Just a quick question. Before I purchased Construct 2, I used The Games Factor and MMF2 quite a bit.
Thinking about this, I found it odd that transparent pixels are included in collision detection, or even that a collision polygon is always needed. I loaded up MMF2, loaded in the same sprites I've used here, set up the scene in the same way, and ran it. I moved one UFO onto another, and there was no collision at all on the transparent section of the sprite, in fact, collision was pixel perfect.
Now I'm all for sticking with Construct 2. I feel it's got a better future and the features that are coming out are incredible, even it's its development stage.
My question is - Can we have it so transparent pixels are not included in collision detection? I can't see any practical use for it. If we want players to be stopped by invisible objects, can't we just have a block and make it invisible? I feel this would make a better default, that is if it's possible? Maybe it will be a lot more powerful if included with the collision polygon, or have it as a toggle. Personally I can not see how a collision polygon is better than ignoring transparent pixels altogether.