3 questions - Memory, collisions

[Yikes]

I have a few questions. First of all, I can't seem to check for one object overlapping another, if they are on different layers. Is there a way to do this, or do I have to do it the hard way and make an invisible version of the same object on the correct layer?

Secondly, if I have an object of say 16x16 pixels, and I scale it up during runtime to fill the screen, or at least to be a lot larger than it is originally. Does it still consume the same amount of memory as the 16x16 one, or does it consume more?

3. I like to keep things neat and tidy by having "always" and "start of frame" several places in my events in different groups. Does this hurt memory, and should I try to confine all actions into one "always" and one "start of frame"?

[KLiK-iT]

Yikes,.first one I have no idea! Second one,.yes just check the debugger at runtime and see if the Mbs jump up when the event happens. # 3,.never had any issues with memory running more than one always and Start of frames.

[Yikes]

That's too bad about the second one. I had some faint belief that it was better to scale objects up at runtime, than to just keep them big in the frame editor.. but it seems it's the same anyway.

[KLiK-iT]

Did the debugger Mb usage jump up when the event happened? Just curios!

[Yikes]

Yes, without any doubt :P

[nivram]

First one. Yes, you will have to put a fake on the same layer

Marv

[Yikes]

Ah, okay.. thanks Marv

[SolarB]

First one - you could also have your events like this:

Always - move object to layer with collisions

Check for collisions

Always - move object back to its original layer.