Construct 2 vs. Unity

ggibson1

If IntelRobert can provide support on Scirra forum (and I guess that Intel is quite big company), then authors of Chromium could do that too. Scirra earns on C2 so could do something more than just saying "wait for CocoonJS", "wait for Crosswalk", "wait for Android 5.0", "wait for 2015" and so on.

newt

so jittering is user related? lol

Every case?

Probably not.

The problem is that users run into things, and can't discern between a logic issue, and a software problem.

Then to make things worse you can't just upload a capx that has private assets, and nobody wants to waste time debugging it just to find out it really was a user mistake.

newt

It's clearly an engine case, not C2 but more on Chromium & wrappers based on it, NodeWebkit & Crosswalk.

The jank, stutter or input lag is ABSENT in iOS8 WKWebView. Buttery smooth.

I wasn't talking about known issues.

I think newt was suggesting that C2 allows users to easily produce engine issues(if there are any) since C2 makes it easier to work with it. And because of this, users don't see initially the fact it is an engine issue because users interact with C2, not the engine directly. When something goes wrong, their immediate focus is on C2- with what they have their hands on.

newt

but these "known issues" affect many C2 developers

and the only answer - always and forever - is "wait"

I can only guess how "Airscape" or "The Next Penelope" devs feel - they invested lots of money, they invested lots of time, their games are visible on Construct 2 main page, but they can't play 100% smooth their games

do you think it's normal?

I think it's all conjecture until you bring real numbers of what works on each engine, on each platform, and a decent offering of the range of different machines.

But that wasn't my point.

My point is that there are a lot of baseless complaints about performance that aren't related, and are in fact user error, and that they muddy up the process of figuring out the real issues.

Sort of what Prominent said.

newt

My point is that there are a lot of baseless complaints about performance that aren't related

I see mainly posts about:

• Crosswalk (it is true because of Chromium),
• Node-Webkit (it is true because of Chromium),

and even perfectly smooth iOS has (as — mentioned) issues with webstorage

szymek

Yes someone from Intel may choose to post here and so may Google. Scirra has no say in the matter one way or the other. They are an outside observer just like the rest of us. There is no way to co-operate with any of them unless the people that make the other engines choose to engage on their own.

I concur with the frustration however. I am finishing up my game I have spent every weekend this year on... and I do not look forwards to having to deal with issues caused by the browsers / hosts... That was the risk I accepted though at the beginning because I knew then that HTML still has not caught up to capabilities of OS software even though it has advanced quite a lot. The trade off was that C2 is such a nice game engine that I could make a high quality game in just some of my spare time... Also I do not need to spend thousands of dollars to make the game that would have been required from Unity.

newt

> My point is that there are a lot of baseless complaints about performance that aren't related

I see mainly posts about:

- Crosswalk (it is true because of Chromium),

- Node-Webkit (it is true because of Chromium),

and even perfectly smooth iOS has (as — mentioned) issues with webstorage

I have been reading these forums for the past year and most people seemed to be happy with Google based hosts until just recently. And same with the web storage issue. And YES this is normal. It has always been true (for decades) that developers that use third party tools (browsers) to speed up their development must deal with the shortcomings of those tools as part of the trade off... or else just build it themselves from scratch at great expense...

So normal in fact it has a name in the software development world.... "build vs buy"

If you guys really want to migrate to other tools. Might be interested with this free n open source software.

https://github.com/4ian/GD

www.compilgames.net/index.php

compiles to native and html5. For android or ios still requires wrapper like XDK or cocoonjs.

If you guys really want to migrate to other tools. Might be interested with this free n open source software.compiles to native and html5. For android or ios still requires wrapper like XDK or cocoonjs.

biz.turbulenz(dot)com/developers

This is also available it is under the MIT license. It is a web based tool set / API for making games in the browser That said I do not think It has a level editor...

Unity is better for complex games. I use Construct 2 for simple games. The mere performance for Unity is smoother, too, and don't blame the Chromium team. HTML5 is just not ready.

HTML5 was ready awhile ago until the Chromium team broke it. :/

I'll agree with a lot of users here that HTML5 is a massive headache, the cross platform mobility is great, but we don't even really have that for anything more advanced than a simple game.

None of this bothers me yet (mobile game dev FTW) - but 2015 is when I plan to move onto a serious project that'll take about a year to finish; on the one hand, the issues we're talking about now will have gone, but on the other hand - Construct 3 will likely being coming into it's Beta phase next Christmas...

I have to wonder if there was ever a change to build an engine that exported native, and then we used "wrappers" to build our HTML5 versions, at the moment it seems we have to work backwards.