newt

so why 60 fps?

even next gen consoles usually play 30 fps because 60 fps is too demanding

Why does 30 fps in any native/console game means smooth game,

and 30 fps in any Construct 2 game means slow, almost not playable game?

Maybe it's silly question, but I'm just curious

Dalal

Ashley suggests using Crosswalk because he says that it is more reliable and stable than CocoonJS Canvas+, and it has WebRTC, DOM etc.

Unfortunetly in real world, for many developers it's more important to have FAST & SMOOTH game than i.e. use WebRTC. And as far as I know (reading this forum) Crosswalk has also memory issues or 4x slower audio decoding. And Crosswalk always will be slower than CocoonJS Canvas+ just because browsers are not created for gaming, lol.

So from one hand we have Ashley who can wait years for development of browsers - because he is already earning on Construct 2, and we have dissapointed developers who can't wait months / years for some 3rd party miracles.

So it would be nice if Ashley would have more realistic approach. Especially when i.e. ludei asked him for meeting.

Ashley you said that "Reliability is essential" but then you agree that there are Chromium bugs that should be fixed at some point. So... is Chromium reliable now? In the past you were saying about 6-week period for bug fixing in Chromium. And 422000 bug was reported in October 2014.

So we have: October - November - December - January - February - March - April. 7 months?

OK - at some point this might be fixed, that's quite obvious. But now is now. And there were some benchmarks on code.google.com showing that situation is not getting better.

And if Google really takes care about HTML5 gaming then... did they assigned i.e. 10 or 20 programmers just for HTML5 gaming issues? I doubt. But they are sooo rich... They could...

mercedescolomar

black screen = your app is propably still loading,

loading bar etc. is not visible and Ashley will not fix it because CocoonJS Canvas+ was deprecated by Scirra

(however there was some post about "how to fix it")

Many complaints we see about performance are in fact bottlenecked on the GPU, so a native app would perform identically.

so why do games wrapped with CocoonJS Canvas+ are faster than games wrapped with Crosswalk? And why you can't understand that people use CocoonJS Canvas+ not because they are ludei fanboys, but it seems to work better?

and why even the simpliest projects can't work 100% smooth in Crosswalk? is bullet behavior used with "pipes" in Flappy Bird test causing CPU bottleneck?

and so on, ehh...

+1

Jayjay

Crosswalk on mobiles can't play crappybird test in 60fps, 100% smooth, without 0 jittering. And it is just 1 bird + 2 pipes with bullet behavior.

BasicTribe

unfortunetly Scirra's approach is not professional. But hey, according to Ashley Google is very rich and they have thousands of workers, so sooner or later they will come and help us. We just have to wait a few more months / years.

Ashley

[quote:12w7ntui]On page 4 of this thread, all I can do is shrug and say I don't see what you're seeing, apart from maybe acknowledging that Chrome has had a rough patch of bugs which has affected smoothness and performance (and NW.js and Crosswalk inherited that), which is Google's responsibility, and not to do with Construct 2 or its engine.

so we should contact Google and blame them that we paid for Construct 2 and we can't have smooth games on Android?

Even crappybird clones?

Jayjay

[quote:12w7ntui] I'm starting to wonder if that's because there is no platform behaviour. In our game almost all the enemies and player objects have platform behaviour, and based on discussions on the forums that is where others find slowness too. It seems like TNP is heavier on GPU usage than CPU usage as well, so that's probably another reason why it runs better than most big C2 games.

You might be right.

Unfortunately I've been hearing the same old excuses week after week... month after month, since I started using C2 some 3.5 years ago. And for a while I kept hoping the improvements we needed were just around the corner (as promised). But the same problems I experienced when I began using C2 (poor performance, lack of robust 3rd party wrappers etc.), still persist. Despite the many assurances we constantly see in the forum.

Well, recently Ashley said that in about 1 year situation should be better.

And even if there are possibilities for better performance (like Cocos2d-JS):

[quote:21sjyj2m]Cocos2d-x JSB for C/C++ is the wrapper code that sits between the native code and the JavaScript code. JSB enables calls to the native code using JavaScript and vice-versa.

http://cocos2d-x.org/wiki/Cocos2d-JS

Ashley always says that he will do nothing to improve situation on his own. Because browsers are better. And we can wait. And everyone everywhere depends on 3rd parties. And so on.

rexrainbow

Jayjay

Microsoft should come with his Spartan and conquer everything

anyway I don't understand Google in case of Android: they have AdMob, they could earn lots of money IF provide really good HTML5 support... And they have money for long term investments... yet situation on Android is bad.

Jayjay

Ashley is working hard on recipe builder for pizzas (Construct 2/3) but he does not care about ovens. So you can make great pizza, and then you have to put it in the fridge and freeze, because you can't bake it well.

anyway: Construct 3 will be shiny new editor, but after exporting our projects we will have the same old problems. So in fact nothing will really change.

Prototyping tool? Yes

Education tool? Yes

Professional game development software? No

That's sad.