I may be wrong but I think he means in general what is it for, not why he used it.

Not that I don't support commenting

Is your computer just not quite able to run it maybe?

If you mean it takes a long time to set up the layout, but is still running at a good framerate, then you could just make your own bar with the length tied to number of objects.

Could still do this with a poor framerate, but it will be very jumpy hehe. Perhaps a simple "Now Loading" would suffice.

ranma: No worries It's hard to tell some stuff from text, which is why people always think I'm arguing lol.

Rich: Say whaaa?

I work with mobile phones but not on games, so I won't comment on that. One thing I can think of that could use over 100 is bullets or something.

If I set it to +200 instead of +100, it misses by 4 pixels instead of 2, and then goes back to 1-2 pixels at +300.

One run of +400 missed by 7 pixels.

Uhh, I agree with you ... I said PNG is the best option because it is. That doesn't mean I don't think other options should be available, which is why I suggested zip. Also, jpeg would another option.

As for how many times you've "told me" ... well, that was the first.

And I know PNG won't compress further, that wasn't the point If you read again is said "so you don't have to use PNG." Which means, other formats beyond jpeg, etc.

lol, I just realized you guys are discussing ticks (no idea how I missed that) ... I thought there was pixel differences elsewhere.

I actually have nothing to add then lol.

We're talking a difference of maybe 10 pixels here. Do you really have areas you can't jump to if you fall 10 pixels short? Or areas you can reach if you jump another 10 pixels high? Really?

This is the only thing that caught my attention. What if someone is making a retro game, low resolution and all, I think every pixel is important.

1-3 pixels seems fine, 10 actually doesn't. I guess though if Construct isn't intended for older styles and smaller pixel art, then they can go elsewhere.

At 1080p resolution, 10 pixels is nothing ... at 320x240 or so ...

If I sound rude, I don't mean to hehe. I work with mobile phones and 10 pixels is a big deal

Pointless? The point is you wouldn't need to use PNG. Could keep your BMP or whatever and still gain the filesize. (I don't need such a feature, I'm just pointing it out).

Also, when I say zip, I mean all formats. Rar, 7z, Ace, etc.

EDIT: I should also note I think PNG is obviously the best method, I just can see why someone might want an alternative.

Maybe a better option would be to zip them and unzip at runtime. Possibly even adding something so that Construct could do this.

That way, you'd have the file size reduced for downloads, but not reduced in quality. Also, you'd be able to put a password on the zip to keep people out (until they figure out where the files are stored at runtime anyways).

I have no idea if this is possible already or whatever, just what I would do if it were up to me.

Well, that example has made me curious now if the addition is indeed needed.