Creating objects larger than 96x96 w/o drastic inc. in CPU in Design Philosophy

ID:151290
 
Sep 28 2011, 7:16 am (Edited on Sep 28 2011, 7:23 am)
So I was play testing my project and noticed when creating a large object, the CPU usually jumps up by like 20 for an object that is 128x128 and the game freezes for a second or two.

The thing is, I've seen other projects creating even larger objects and showing no signs of a slowdown of the game. An example being here. If you'd like you can skip to 00:50(blast around 256x256) or 2:38(aura around 128x500?) for a good examples.

After I saw the video, I started to get slightly confused. How are such large objects being created yet no lag and no momentary slowdown? Along with that, there are pretty great particle and flaring fire effects which also look pretty CPU consuming?

Any ideas on how all this is being done without any drawbacks?
#1 Sep 28 2011, 9:50 am
They are probably split into many smaller objects.

It lags because Dream Seeker doesn't use hardware.
#2 Sep 28 2011, 9:57 am
In response to Zaoshi (#1)
Zaoshi wrote:
They are probably split into many smaller objects.

It lags because Dream Seeker doesn't use hardware.

I was told that it isn't much of a difference between using split up pieces and a whole big icon though.

LordAndrew wrote:
Creating an icon that is multiple states that you must build together via a proc is sorta more complicated, if only because you have to build the entire thing from the pieces.

Looking at a whole icon and then a version that's split into several 32x32 tiles, the latter takes up more space (but it's a very, very small amount [1.24 KB compared to 1.27 KB]).
#3 Sep 28 2011, 10:12 am
In response to AbdelJN (#2)
Maybe allocating memory for icon takes less time, I'm not fully sure. But you don't see normal map lagging even if move fast.
#4 Sep 28 2011, 4:09 pm
In response to Zaoshi (#3)
Zaoshi wrote:
Maybe allocating memory for icon takes less time, I'm not fully sure. But you don't see normal map lagging even if move fast.

What do you mean? Can you rephrase the second part?
#5 Sep 29 2011, 5:41 am
In response to AbdelJN (#4)
If you have big map with a lot icons it doesn't lag when you walk around.

Just try to split icon in several parts.
#6 Sep 29 2011, 6:07 am
In response to Zaoshi (#5)
Zaoshi wrote:
If you have big map with a lot icons it doesn't lag when you walk around.

Just try to split icon in several parts.

Oh I know that. That's not really the problem. It's creating objects during runtime with New() for things like projectiles. For some odd reason it boosts the cpu up by like 20 yet I can create like 30 individual objects that are 32x32 without any/much change to cpu at all.
#7 Sep 29 2011, 6:57 am
In response to AbdelJN (#6)
Well most likely it has trouble loading big file.
Maybe it need to copy icon somewhere else, I'm not sure how it works internally.