> In fact, C2 is capable of making something way more complex than CC can even begin to hope to handle.Fact? I'm disappointed to read such a wrong sentence from you. There is not one app that proves you right. Contrary, there are lots of complex applications made with CC that simply can't be realized with C2. Maybe I have to add the word "yet".
You can't judge a tool's capabilities by the content created with that tool. Games take a long time to make, and C2 hasn't been out that long.
True, there is functionality missing from C2 that CC has, but it's being added regularly.
Regardless, even in its current state, I don't recall many games that were made with CC that couldn't be made with C2 (thumb war being the most notable example, but even then if C2 had sprite distortion it might be capable, though it might require a fast machine).
There are also plenty of examples of stuff C2 can do that CC can't - probably more examples at this point, and those examples are probably more relevant to the majority of users (exporting to mobile, mac and linux, for example).
Or you don't mean complex but quantity and not runtime but edittime?
I'm not sure what you mean by that, but having made a complex game in CC with over 10,000 events, 500 objects and thousands of animation frames, I can state with some authority that my attempt to make something complex with CC didn't work well at all and CC is not reliably up to the challenge of making a large complex game. CC is barely, barely able to manage loot pursuit which is actually a medium to small game, and yet it takes 10 minutes to load the battle event sheet, 7 seconds of waiting for every single edit made to that event sheet, 30 minutes to undo or delete an object, 5 minutes to preview, there are events I can't move or edit without crashing the editor and I have to repeatedly close and restart the program when using the animation editor to keep memory leaks from crashing the program, not to mention all the instability caused by trying to do things like delete family variables or such keeping me from reworking the code.
Conversely, my attempts to make things in C2 have worked much, MUCH smoother. Aside from the features it lacks (sprite distortion, etc) and event execution speed (which is plenty fast for almost everything most people will want to do), C2 can make the vast majority of what CC can, and a lot of what CC can't. It's better in almost every way.
Even if CC didn't have its instability I would still like C2 more. More platforms, better editor, faster preview, actively developed - honestly, I don't understand why people talk like CC is the actual great version of construct when C2 is so much better. Perhaps it's because other people haven't tried making something complex with it yet to realize how frustrating CC can be. Or perhaps it's concerns about html5. I was concerned at first as well about html5, but it's turning out to be far, far more capable than I thought - capable of even outrunning CC's rendering speed by a good margin with a recent graphics card.