For me none of the games up there actually play - just a white box.

Tried in both Chrome and IE.

Windows 8.1 64 bit

Current "Else" condition is the best example. If you put "else" in wrong place then you can't start the preview

If you delete something important then highlight events with mistakes and don't let user do anything before fixing that broken events. If the name of that variable or something is an issue here, then why editor can't replace it with something. I'm sure C2 can handle making an internal temporary list containing names of broken variables and simply use these void names in events. And when user fix all broken events then the list could be removed.

There's a lot of possibilities to make it happen without making a mess, question is if devs want to something about it, or leave it like other unfinished "features".

This a much better way than just deleting a bunch of events.... if it can't be done with C2, at least put it in C3.

Hehe, what a cool read though - look how far C2 has come. Ashley is surely a coding guru!!

Oh you mean like this bug report that I totally didn't submit? You know this never got fixed either, at least fully.

Well let's be realistic here: if you want an audio bug investigated, you can't have any other logic for other features of the engine in play because you have an audio bug!

This implies that if there is a bug, it is likely something you did to cause it - like maybe a bullet is going the wrong way for audio to work correctly.

But what is really happening is there is a glitch behind the scenes in the engine that is conflicting between audio and bullet. So if you submit a capx with just audio events, you won't be able to reproduce it, and therefore nothing has to be done except close the bug report - yay problem fixed!

There have been numerous bugs with audio that can't be reliably reproduced with a dumbed down capx. And because of that they will not get investigated, let alone sorted out.

That however doesn't mean it isn't a C2 bug, it just means you can't reproduce it with a couple of events and no other behaviours in the project.

If we go by what the market is showing us with regards to other game-making tools, as soon as you start writing native exporters, your product is frozen. Feature development slows to a glacial pace and all efforts are shifted to attempts to bring feature parity and bug fixes.

C2 has all the features it needs now.

Don't add more: fix the export problems, then make all the current features solid, then make an new Editor, and after that start adding more features if you want.

As it stands C3 will just be C2 with a nice editor (which would be great) but still nothing more than a prototype/education tool - great if you are just a novice, but not so great if you want to let the world play your game.

You can use however many layouts/levels you want, and just attach the same event sheet for your game logic to each layout.

IE one event sheet, many layouts/levels.

I love C2, and really feel scirra have created an awesome product.

But sadly as it stands it seems that C2 is a prototype/learning tool - at this stage there are no export options that produce satisfactory results for serious game development - or at least that how many of us feel.

Chrome is now a bug - don't use it!

To address the constant barrage of performance complaints I really feel that scirra needs to build a real world game with their own product.

This will provide at leaste three benefits:

A showcase game that demononstrates the power of C2. An example/model of how to use this tool effectively/correctly. An opportunity for scirra to see what issues are faced in a project with more than one layout and a few events.

If anyone can make a game that works with satisfactory results with current exporters, scirra can!

If scirra can pull it off - then it will be proof that the product is fine, the exporters are acceptable, and all the complainers just have to buckle down and learn to use C2 properly. However I suspect that the end result would be as frustrating for scirra as they are for the developers of the shiny examples on the scirra home page.

Just commenting to keep these type post at top - they need to be known and addressed - in fact should be stickied!

— Yes noticeable jank in your video.

I think the only option at present is to learn new tools if you are serious about making games you can release. That of course is a real shame because C2 itself is an excellent tool. But you can't keep waiting and hoping things out of your control will improve.

I think we just have to accept that C2 is a prototype/education tool.

Yeah just lately I have been wondering if there is anything that can actually be done on C2 side.

My wife is fanatical with a Facebook game - Farmville 2.

She plays this game almost daily and has done for well over 12 months. It has lots of things happening on screen (1920x1080 res) all the time.

The thing that makes me wonder is that she uses Chrome to play the game and it has NEVER had any of these jank problems - period.

So is it that the people who make the game have found work-a-rounds for the jank problem, or is this more of an issue with C2 exported games conflicting with chrome in some way?

C2 is only good for simple flappy games, and prototyping.

The reliance on third party tools that don't deliver quality performance, and the constant 'wait for things to improve' is a definate no-go policy for serious game development.

All the big game devs showcased on the home page, are experiencing real issues with C2, and/or will not use C2 for large projects again.

The only way this will change (imo) is if Scirra developes a large game with their own tool, so they can experince the real issues that game devs have with this awesome - yet severely shackled - tool.