The best idea would be to save this .CAP as something else, and then start deleting objects and/or events until the it runs again.

I voted(or whatever). Don't remember what categories, but I did.

Rich - Construct crashes. I'll go ahead and submit it as a bug as soon as I can.

Ashley - I'm pretty sure I'm using CRunObject, but I need to reinstall VC so I can check. Ultimately, I kind of stumbled around like a blind person when making the plugin.

I wish I had know about using expressions for keyboard input before. Thanks for pointing that out, lucid.

Okay, I have a question about some plugin things. I just found a crash associated with my IK plugin. If the objects the IK plugin is using aren't there(if you have them destroyed at the start, for example), Construct will crash since it can't find any objects to use. I know Construct shouldn't crash, but is there some code I need to put into my plugin to keep it from crashing?

Nifty. I didn't notice when I looked at this earlier that there's actually perspective, something that eluded me when I did this. The method I came up with didn't really support it.

nice job on this, id love to see .3ds importing like i heard linkman had done a while ago.

Mine didn't actually import .3DS files. I used Anim8or to output a vertex file(or something), then I cut all of the unnecessary crap out so I could read the files line by line unhindered.

I'm saying for the standard squished diamond isometric shape, which does require a half-height grid to snap properly. Here's a CAP showing what I'm talking about:

Diamond Isometric Grid

I don't think we need a special isometric grid. The height of the grid just needs to be half the width, and you can already change that.

If your refresh rate was something like 75, like my main computer, then there would be a difference between + 1 and 60 * TimeDelta. To achieve the equivalent of + 1, it just becomes (your refresh rate) * TimeDelta.

So basically, if you want your game to have the equivalent of what + 1 is on your computer, but still run the same on everybody's computers regardless of refresh rate, you'd just use (your refresh rate) * TimeDelta

There shouldn't be a discrepancy between + 1 and TimeDelta * 60 if your refresh rate is 60Hz. You should probably post your CAP so someone can take a look at it.

Anyways, here's a CAP I rigged up where there are two separate objects being moved using the two methods. There's only a slight discrepancy due to rounding errors.

TimeDelta example

You can also see VRAM usage while running the game with the debugger(under the project tab). The VRAM usage is near the bottom of the list in the debugger window.

This can be done using a little math. I'm not so good at explaining these things, so here's a CAP file I whipped up real quick:

RTS in Range

The goodguys have a variable called 'range'. Changing this will change the distance at which they stop.

Hope that helps.