Snatcher:

http://en.wikipedia.org/wiki/Snatcher

I remember playing thru this whole game one rainy day, curled in bed with rain spattering and the wood stove crackling away.

It was...magical.

...which is a strange word to use to describe a violent, stylish, edge of your seat blade-runner-esque visual novel/shooting gallery. <img src="{SMILIES_PATH}/icon_rolleyes.gif" alt=":roll:" title="Rolling Eyes">

Metal gear is definitely a more original, polished, and ambitious work...but honestly, Snatcher did way more for me than gear ever did, though I'm not entirely sure why. <img src="{SMILIES_PATH}/icon_e_confused.gif" alt=":?" title="Confused">

Highly recommended, albeit hard to find... <img src="{SMILIES_PATH}/icon_cool.gif" alt="8-)" title="Cool">

Probably. Keep in mind, if you have a really old project -- say, prior to r155 with the introduction of collision cells -- you may actually get a slower result if your collision events aren't top level (ie, if you are trying to narrow down affected objects thru other means).

Your art looks great, pro but not generic. Looks like it would suit mobile perfectly.

Curious though: why brown blood?

That dragonfly-winged-hovership-thingy is brilliant!

Never played it, though I've seen it somewhere before. Looks very imaginative.

GOG is really amazing...came across this on there, been meaning to play it for ages, but haven't got around to it yet.

http://www.gog.com/game/i_have_no_mouth ... ust_scream

New order looks good, much more straightforward.

Well, if an object is invisible (not 0 opacity, has to be properly invisible) it doesn't make draw calls. Also, if you turn collisions off -- and you have to do that, they default to 'on' -- that lowers your overhead.

Even if you aren't testing for collisions with a particular object, just having collisions on can eat up a significant amount of overhead.

Arima

Thanks for the capx example. It's an approach I never thought of, and may come in handy in the future.

However, in my case collision cell opts were working fine; I was simply attempting to gain an additional advantage by only testing cols ever 3-4 ticks.

I was hoping to break the tests up by only testing 1/3 of the objects per tick, thus cutting the cpu load to third/quarter without cramming all the col testing on a single, intermittent tick (ie, every 0.1 seconds or the like).

However, it seems that, at this point in time, there's no real way to do that and retain the advantage of collision cells. Perhaps it's not even possible.

As I said before, I've moved past this for my game, but it would be nice to see this ability in the future.

DUTOIT

Thanks. Works great, and simpler to read. For anyone else reading this: if you download the capx posted above (format_number2.capx) and don't want decimals, change the first action from:

Set Text to "." & zeropad((foo*100)%100,2)[/code:2m7jhbul]

to

[code:2m7jhbul]Set Text to ""[/code:2m7jhbul]

Cheers,T

Ah, yes, that's perfect! Well, except for the decimals...but I can probably get rid of them.

Much simpler than what I was trying...plus, it works.

Thanks DUTOIT

Er, no, maybe I should have been clearer: I'm trying to insert commas dynamically. Like, if the score is 12000, I have an event which takes that, turns it into '12,000' and sets the spritefont to that (121004 becomes 121,004 etc).

Thanks anyway though.

I'm using a spritefont for a score readout. I just want to insert commas in the score, like 12,000,000, or 1,000, etc.

Anyway, I found this example (not for C2):

http://gmc.yoyogames.com/index.php?showtopic=586659

Problem is...well, all the spritefont object has is 'append text', but what I want to do is, er (googling...) prepend, because otherwise I don't know where to put the first comma.

Or...maybe I'm confused... <img src="{SMILIES_PATH}/icon_e_confused.gif" alt=":?" title="Confused">

...nah...

...any ideas? <img src="{SMILIES_PATH}/icon_mrgreen.gif" alt=":mrgreen:" title="Mr. Green">