Nice! Congrats!

First round of animations are up, check em out! Let us know what you think.

http://googledrive.com/host/0B1Aaz61BSe ... TVhWUQxQU0

This is GEO:

[attachment=0:3pf456bb]GEO.jpg[/attachment:3pf456bb]

https://twitter.com/ProjectHexGEO

https://www.facebook.com/ProjectHexGEO

Non-triggered conditions will happen every tick as long as they are true.

Adding a "trigger once while true" condition will make it only happen once.

Well.. don't just read the manual front to back, but use it for reference (works well alongside the tutorials). When you get stuck (or if you just want to understand something a tutorial had you do a bit better), pull up the manual and search. If you can't find what you need, then use the forum search, as almost any beginner question has probably been answered dozens of times.

The window size is set just below where you set the layout size. Click "view" next to "project properties" and you'll see it.

You need to change the window size (in C2, not your browser). I would also suggest reading the manual and doing some tutorials.

Indeed, I do..

It might depend on what you're doing, though. I'll explain.. bigger window size, means your sprites will end up being bigger to match, so everything will end up using more cpu. In most cases, this is not really a problem on PC, but if there's going to be a very large amount of sprites, it can add up.

I've been working on stuff for mobile, so I'm not really an expert here, but I think I know what I'm talking about.

"I can change size" -- The size of what? window?

Have you tried the 2 things I suggested? Kinda hard to know what exactly you're trying to achieve with so little information. If you want to post a capx, I'll take a look (but I'm on stable, so I won't be able to open it if you're using a version higher than 184).

EDIT: Went ahead and got beta.. If you want to post the capx, I'll take a look!

Layout size is basically irrelevant to cpu usage and I don't really think there's a common size used.

Window size is a different story, as this decides how many pixels are being drawn on the screen.

If your game is PC only, 1080p is probably a good route to go.

I also found that using a very low number like "every 0.01, add 0.01" would not work as intended and tracks time slower than the project's own clock. I'm not sure if this is a bug, 0.02 still worked fine.

I'm not absolutely sure, but I believe this is because 0.01 seconds means it happens faster than the framerate ( more than 60 times a second (0.02 is less than 60 times a second)).

Changing the layout scale will essentially zoom in/out, if that's what you're looking for. Hard to tell from your question, but I'm guessing either that, or just change the window size to what you need.

There's a lot more details needed to make a decision like this... and honestly, if you're only at the planning phase, I wouldn't worry about it just yet..