Hi all, I have been following this thread but until now have not performed the tests - finally got around to it today, here are my results.

Before dropping below 60fps:

C2 WebGL:

about 24000 objects

C2 Canvas2D:

about 4000 objects

Pixi.js:

about 18000 objects

All tests at 1920x1080 res.

Edit: Window size seams to make no difference.

Test machine specs:

Intel i3-4160 CPU 3.20GHz

8 GB RAM

GeForce GTX 750

Win 8.1

thegrind,

"Do you think this is a browser problem or C2 problem?"

Well, yeah, but more specifically a browser developer problem. As colludium said you will get different result on different browsers. Browser developers never have and never will use/conform to standards that work towards uniformaty of the web.

The only solution unfortunately is spritefont.

Ashley, Thanks for your input:

A serious game can take years to design, develop and release, and we would basically have to put Construct development entirely on hold during that time. I don't think anybody really wants that.

Indeed and I do not want you to do that either. That is why I said for you just to oversee such a project.

Despite what you may think I am listening and do pay attention to everyone's concerns here. It's just there's not always a lot we can do.

Please be assured that I do not think you don't care or pay attention. And I appreciate that much of these issues are out of your control.

And while the fact that these things being out of your control is the reason many are calling for native export options, I appreciate that that also will not happen.

This is why I feel that a game released by Scirra themselves would just help boost confidence in this awesome engine. It doesn't have to be huge - even just Space Blaster with a few more levels and polished up with all the appropriate start screens etc, and actually published would surely go a long way to boosting confidence.

Just for the record:

I for one will keep using C2 and will support C3 despite what Scirra does in this regard. Like many others I think you have created an awesome product. I am not 100% comfortable with the likes of Google being it's biggest drawback for many users, but I will just keep targeting Windows Store as that seams to work fine, especially on Windows 10.

Anyway thanks for great product and taking the time to give feed back on this thread (and others).

Not fussed about Android - but starred and commented has been done!

This is sort of a ridiculous request. I know what you are after, but it's simply not possible. If anything Scirra would sponsor select developers to showcase their engine. That is what other industry software shops do.

Well that is basically what I suggested in the OP:

"Now I am not suggesting that Ashley stop working on C3, but that he oversees the production of this project. There are plenty of C2 gurus on this forum that may want to be enlisted, and I for one would even be willing to make a pledge to pay for it."

— I think it is being removed as an option for apps released to Google Play Store, another example of google breaking things!

Are you saying like a larger game, or a small game like what we have with the C2 example files? (Space Blaster etc.)

Not sure on how large it should be, but definitely something beyond the scope of Space Blaster.

I guess it would be something we as community could suggest and vote on. hehehe, I remember somewhere on the forums suggesting the image on the Scirra home page should be made into a game!

I know that any project of this kind would not be a small undertaking - but I really think it would be good for both Scirra and the Scirra community.

I myself am not the greatest artist, but could help make GUI elements, and would be more than happy to create them as a contribution toward the project.

This is a request for Scirra to make a game!

Now I am not suggesting that Ashley stop working on C3, but that he oversees the production of this project. There are plenty of C2 gurus on this forum that may want to be enlisted, and I for one would even be willing to make a pledge to pay for it.

Why Should Scirra Do It?

* All of us here want to see C2 and C3 not just continue, but become the best 2D game dev tool around * There is a lot of discontent with C2 at the moment, this needs to be addressed * I can't think of a better way to prove the worth of this tool * Scirra are the only ones who fully know this product and it's potential - and if they can't pull it off then heaven help the rest of us!

How would this benefit the C2 community?

* It will show Scirra has confidence in their own game development tool * It would provide a showcase example of the power of this awesome product * It will demonstrate that this tool can be used to create cool games that the world can play * It would boost morale amongst those who have backed this product - that it is a viable development tool they can rely on

How might it help the C2 community?

* It would show that performance\bugs issues can be worked around * It could show that many issues faced by devs are in fact caused by devs misunderstanding the event system * The source code could be used as a study vehicle to learn how to use this tool correctly and effectively

How might this help Scirra?

1. When developing a game for the real world, beyond a few sprites and a couple of events, running in preview
* It may help them understand better some of the issues their backers are facing with such a project * It may expose issues with the engine itself when used in this scope, which can be used to improve not just C2 but also C3
2. When exporting a project
* It could give valuable insight into the export options available to their users - i.e. make real tutorials available for great user PR * It would also expose Scirra to the issues faced with the most troublesome exporters - i.e. Chrome\NW - and give opporyunity to show Scirra community how to work around them * May also show that relying on Google is an exercise in futility
3. It will either
* Show that the issues\requests raised in so many threads about performance, native exporters, and the like, are not unfounded, and should be addressed * Or, that Scirra has been right all along, and the C2 dev community just has to get to know the product better

What Target Platform?

I would suggest two projects:

One that targets Desktop
Runtime objective; Silky smooth - fairly smooth is not OK
One that targets Mobile
Runtime objective: Smooth - at least on devices that have been out for 12 months

So what do you C2 devs out there think?

Starring - for what it's worth!!

EDIT: additional content removed in the interest of keeping this on topic after giving UberLou later comment some serious thought....

After all we all love C2 and want these third party issues sorted.....

Well, as I have said before, until a game is released that performs well on its intended target platform, C2 will not be taken seriously.

The best dev for such a game is Scirra themselves, they are the ones who know the tool and its potential better than anyone. It is in their interest to publish a cool, well performing game, that not only showcases this awesome engine, but also proves that all the issues with performance\bugs are in fact caused by those (devs) who experience them.

It may well also expose some issues with the engine, that only surface in projects with more than a few sprites and a couple events.

The challenge of course is do Scirra have enough confidence in their own engine to take on such an exercise?

Well, I don't think Scirra can do any more than they do already, at least not until they expand somewhat - but that is their call.

The sad fact is that the current export situation (chrome\NW) are woeful and will be for some time it would seam. But that is what you have to go with at present. C2 is currently for prototyping and learning tool - and extremely good one at that.