Change the sampler setting in application settings .

> macwys.on1.biz/monkey.cap

>

> I do not want to be boring.

>

> But how to do that only a one banana disappeared?

>

you know what? when i turned on preview mode, nothing appeared, only blank screen. i turned it off and cons crashed. BUG.

Nothing should show if you check the events.

When did it crash?

1) Mute Events.

Very simple thing. What happens if this event isn't in there? Instead of deleting and undo'ing, it'd be cool if we could just 'mute' events, so they'd not be processed at runtime, but they'd still be in the event sheet.

I think you're talking about the 'toggle events' button, on the ribbon.

2) Controller Support.

This is basically the cornerstone of it all. Support for the X360 Controller and all it's functions would be great.

This could be done by any developer using our SDK. We're pretty loaded right now till after 1.0.

4) Multi-Platform support.

Construct is DirectX, yeah, but ultimately, this'd be just frigging awesome. Being able to create a 2d game that you could then compile for multiple platforms would be the best thing ever.

We have plans for this in Construct 2.0.

Yeah you could set up timelines for intricate animation/game sequences and do that, also.

Pretty much yeah .

Possibly, but it doesn't really fit with how events work. You can use the Function object to call actions after a delay.

Till the next build, when some important and silly things are fixed. Shouldn't be long.

You should be able to work out the velocity by getting the total file size and the downloaded amount, then every second working out how much was downloaded.

Welcome! I'd like to echo the sentiments stated above. We're aware our documentation isn't complete, and tutorials are certainly a very effective way to introduce people to game making, and to Construct.

From an attempted non-biased standpoint I think Construct is well suited for classroom usage, in that it is free, simple to use (no scripting, no heavy learning) and powerful. Obviously it has a learning curve the same as any other tool, but we've worked hard to keep it to a minimum (beyond learning the interface and becoming familiar with the event system).

We're definitely aiming to be at a 1.0 release sometime around this summer, and naturally the documentation should develop by then, as will example games/tutorials, I'd expect.

It's got a newish UI and shares some aesthetic similarities, but it's very different otherwise. Looks rather interesting.

That was quick! I thought it'd be fairly annoying to add, personally.

I'd definitely put money on it being our UI lib being the issue, so that's something Wine needs to work on.