Hmmm…I must of misread your earlier post then and assumed that you were on a Laptop. Sorry about that.

*Slaps self hard three times*

STOP IT!

Okay, yeah, that’s the last one.

You know what? I’m just gonna leave for a few days. No more.

(Watch as I come back and keep arguing. Sigh…)

Ah, so you’re using a Lappy I see. Laptops tend to use the RAM as sort of a Graphical Memory, which explains the odd value you gave. Usually the Graphical Memory is set through the BIOS on most Laptops and can be reduced.

While I’m not too sure if you’re running at the minimum already. You can always go into the BIOS and double check if the GFX memory is at the minimum setting.

The reason for this is that Construct has to load all of its textures – including some rather large images from the intro and outro – into the memory before it starts. Yes, that’s silly, and there’s an option to do it differently… but that’s not working properly and makes the game crash incessantly. So, until a newer version of Construct comes out and fixes this bug, Phenomenon 32 will have fairly high system requirements. There’s absolutely nothing I can do about this.

Also, can you give us anymore information about your rig? Graphics Card? Current RAM? If you need help locating either of these, I can provide some assistance.

@Wolfgang: I still don’t see how this makes abortion murder at the point where, original genetic code or not, the embryo has not developed into anything like a *functioning* human being. I’m not saying it’s something that should be done casually – but it’s also not the same as killing someone. Do note, also, that in many situations we have no problem removing someone from life support, and that’s not called murder. How is this any different?
But yes, we should probably get off this. Hmm… game. Ah, yes, the controls. I’m definitely going to look into making them a bit less sensitive. I got used to it after a while, and I think most people can, but it’s almost certainly better if it’s a little easier.