Sorry, *Deleting all events containing [is on layer] [is overlapping] [on collision] [is visible] or some combination of them, inverted or otherwise.
I have a whole group dedicated to events with these conditions to check if certain spots on the grid are ok to draw to. From what I've gathered, said group and even single events such as:
+Tile is NOT overlapping grid
+Tile is NOT on a certain layer
are what cause the CPU to skyrocket.
I suppose there are things I can do differently now, like checking positions rather than collisions, but I'm not sure how much that will help or if I can do that for everything..
Anyway, all this to say that the new change does come with some performance issues if (I guess) used improperly, and as such, might be better if it were optional.Tokinsom2012-11-22 17:04:17