Does this sound tinny to you?

Testing, testing, testing.

One out of two problems seems to be OK now, though all these errors are so unpredictable that I still feel quite paranoid.

The crashing error, oddly enough, seems to occur only when I’m running the game from inside Construct. When I just run the .exe, it seems to be OK. This also makes me paranoid.

In the process of testing, I’m also attempting to optimize the game where I can so that it eats fewer resources. (Does anyone know of any good ways for figuring out hardware requirements? Other than just saying “a lot.” All my old games were so pathetically easy on system resources that you could probably run them on a 80486. Guess I’ll also ask in the Construct forums.)

Oh, and thank you all for being so kind and supportive. (Except for Evil Roda, who is evil and supportive.) It’s been very helpful.


  1. Jonas, the system requirements in this case, I think, are tied to DirectX and Construct because the latter requires the former… So whatever minimum Construct requires, that should also be the minimum req for the game. Other than that, put the game on as many PCs as possible and see how it works – the minimum config on which it runs fine should be also in the minimum req. And anyways, these are more suggestions rather than fixed needs – some people will always manage to run a piece of software on much less than the minimum req. 😉

  2. It’s actually more than Construct + DirectX, because it depends on the amount of resources the game uses. Lots of tiny levels with few graphics would run a lot easier than huge levels full of stuff. Which, despite the minimalism, is kind of the direction of this game.
    Ah, well. We’ll see.

Comments are closed.