[PSA] To anyone that still has doubts about Construct 3's new runtime performance optimizations

To anyone that still has doubts about Construct 3's new runtime performance optimizations over the old runtime, try this and switch between the two runtimes

puu.sh/B6KJB/127748945e.c3p

For me the new runtime holds 60 FPS and 13% CPU usage

versus C2's old runtime with 29 FPS and 100% CPU usage

Anyone willingly sticking to construct2 at this point is a fool and you shouldn't listen to them and worry about why they are lying to you in bad faith

I don't use any plugins that need to be ported and I am still on Construct 2. Mostly because I do not see anything in version 3 that I need right now.

No problems with performance with Construct 2 ( so far )

Benchmarks ( of all kinds, not just Construct runtime ) , for the most part are bullshit, I only care about real life performance. Game either runs fine or it doesn't.

If they made sure ads worked perfectly and if I could export everything directly from Construct 3 ( working APK, iOS versions, whatever ) I'd gladly give them $500 a year, but right now, v. 3 is not quite what it's supposed to be.

Benchmarks ( of all kinds, not just Construct runtime ) , for the most part are bullshit, I only care about real life performance. Game either runs fine or it doesn't.

If they made sure ads worked perfectly and if I could export everything directly from Construct 3 ( working APK, iOS versions, whatever ) I'd gladly give them $500 a year, but right now, v. 3 is not quite what it's supposed to be.

Bullshit? Not really. Far from it.

If you have read the article. The way they approached the new runtime really makes sense that it would be faster than c2runtime. Like the use of web workers, removing backwards compatibility for canvas2d and focusing on WebGL technology, lightening and refactoring the runtime, compiling expressions to Javascript and etc...

The Construct 3 runtime is super fast and super light compared to C2runtime. You won't even need Canvas+ and Cocoon.IO anymore, which makes bloated application.

I am a subscription user of Cocoon.IO and I plan to stop soon since the Construct 3 runtime has proven to be better in terms of supporting the updated Cordova CLI version and performance, far exceeding Canvas+ and without any DOM limitations.

Not to mention, the rendering performance gain from the Sprite-sheeting feature of the Construct 3 Editor.

Construct 2 is only ever fast using Cocoon.IO with the bloated Webview plugin. But is still not that fast.

And, the Construct 3 Admob is actually in the same league as the most up-to-date Cordova Admob available on NPMJS. So, what everyone on Construct 3 is experiencing for Admob IOS GDPR, every indie developers using HTML5 are experiencing it.

I've ported a lot of plugins just to support the Construct 3 runtime, because the speed solves and will solve a lot of performance problems now and in the future.

I hope this clears things up.

For me nothing clears up until it is finally available and I can use it and test it myself.

I know I could already, but I will wait until it's done. ( We are talking about this completely new C3 runtime or just a regular C3 runtime ? )

For me nothing clears up until it is finally available and I can use it and test it myself.

I know I could already, but I will wait until it's done.

It is somewhere, 99% done. The only remaining features left to publish are the Debugger, Google Play plugin and Mobile IAP.

Reference :: github.com/Scirra/Construct-3-bugs/issues/1646

And those are just plugins, which aren't that hard to port to C3runtime. The Construct Team, could even do it in just a few hours. If you count out the Debugger.

On the Performance Side, it is, logically, finished.

I even have released a Mobile IAP plugin I made a few months ago. that I just released now.

Which is C3runtime compatible, it is called Mobile Master IAP.

It is like the Mobile IAP of Construct, only that it is full-packed with updated features from Google and Apple, like Subscriptions and Fingerprint support.

Reference :: construct.net/forum/construct-3/plugin-sdk-10/construct-3-runtime-c3-c2-mobi-136709

If you count that in. C3runtime just needs a new Debugger and a Google Play plugin for the c3runtime.

But again, the Performance side, is already long finished. But as Construct 3 progresses and as many subscriptions pass, the more performance improvement can be expected for the C3runtime.

For me nothing clears up until it is finally available and I can use it and test it myself.

I know I could already, but I will wait until it's done. ( We are talking about this completely new C3 runtime or just a regular C3 runtime ? )

You can use it and test the new runtime yourself now. It has been available for months.

And it would be really helpful to the development and community if you did.

As far as I can see there are only a handful of users actually testing and regularly posting bug reports while everyone else just waits.

And im sure there are a ton of bugs yet to be found.

Nobody is asking you to be a full time tester. Just run your most complex projects and see if everything ok. If not see if you can find the issue and post it properly to GitHub.

The more people who do this the quicker it gets out of beta.

github.com/Scirra/Construct-3-bugs/issues