paradine's Recent Forum Activity

  • Ashley

    My small test proves that native export is required even if you make a simple game with no behaviours and only one simple event.

    My test contains 5 moving 64x64 squares. The only behaviour they have is "wrap".

    APK - it runs 40-45 fps and 8-13% cpu on my mobile device (Apk is made via last version of intel XDK and crosswalk 11)

    HTML it runs 58-60 fps and 9-11% cpu on the same mobile device

    .CapX

    This test proves that Intel XDK kills about 15 fps in a very-very-very simple game.

    And now imagine what will happen with complex games.

    P.S. Later I can show you the same test built via native apk-export - you will see the difference. It is great.

  • If you're using asm.js physics, there's not much more that can be done to make it faster - it should already be about as fast as physics in a native engine.

    Ashley

    It works well in HTML5 games, but it works bad after export via IntelXDK and Crosswalk 10.

    Particles are already highly optimised and even very large effects should run well (this demo runs nicely on many of the mobile devices we have in our office, with ~800 particles).

    Ashley

    It runs 40 FPS and 60% CPU on my mobile device, but it is HTML5-demo.

    Export this demo to android via IntelXDK and Crosswalk 10 - I guess, you will get about 10 fps or even less.

  • I always ask to see CPU-bottlenecked .capx projects. Usually either nobody sends me any, they send such appallingly inefficiently designed games it is obviously just bad design, or they are actually GPU-bottlenecked. Please do send any good examples of CPU-bottlenecked games, so I can investigate if our engine needs optimising. I rarely see such examples though, which is why I have concluded most games are not CPU-bottlenecked.

    Ashley

    Well, most games that use physics, particles and pathfinding are CPU-bottlenecked.

    If it is really necessery I can send you .capx of my physics puzzle game "Tap & Clapp"

    But it's my commercial game that's why I want you not to send it to anyone else.

  • paradine - as I keep saying, many games we see are GPU bottlenecked, so would not run faster in a native engine.

    Ashley - but many are CPU bottlenecked, they would run much faster in a native engine, I guess.

  • If you could clone many Ashley for those native exporters, then it might be possible to have them.

    Very good idea, cloning Ashlay can really solve all our problems

  • Well, "native exporter" means two things, imho:

    1. It creates native app instead of creating container with portable brower and HTML5-game in it (NW.js and Intel XDK create such container, that's why apps are not as fast as they could be)

    2. It is not a third party product, because only Scirra can make it work perfect.

    I understand that it is very very hard to create native exporter - it's like creating another construct, but you can sell such exporters for extra money.

    I have C2 personal license, but I am ready to buy native exporters for extra money with pleasure. And I am not the only one, who wants native exporters and who is ready to pay for that extra money.

  • 1. Will it have native exporters to iOS/Android/Windows/Linux/OSx ?

    2. Will it have an opportunity to export game to flash format (.swf)?

    3. Will it have native physics engine?

    4. Will it have native 3D support?

    5. Will it support vector images?

    To cut a long story short:

    1-No

    2-No

    3-No

    4-No

    5 ???

    Will C3 support vector images like .svg?

  • C2 is the best tool to make HTML5 games.

    But export to other formats is not native that's why games work bad even if they are very well optimised.

    For example, I created a physics puzzle game - it shows 60 fps on Crosswalk 7 but there is an alert from Google Play about OpenSSL.

    That's why I used Crosswalk 10 - there is no alert from Google Play, but the game shows only 30-40 fps and there are freezes every 4-5 seconds.

    Other example, NodeWebkit shows very bad performance if the user does not have Microsoft Visual C++ 2008 redistributable installed on his computer.

    The game could run 60 fps on Google Chrome, but it will run 20-40 fps on Node-webkit if the user does not have Microsoft Visual C++ 2008 redistributable installed on his computer

  • I think this topic should be on top before we get official answers.

  • "Our goal is to make Construct 3 the best game making editor ever" - it's cool, but what about the best game making engine ever?

    I think, best game making editor + best game making engine = best game making kit.

    If constuct 3 has native exportes, it will become the most popular kit ever, and Scirra will become the most rich devkit making company ever.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • 1. Will it have native exporters to iOS/Android/Windows/Linux/OSx ?

    2. Will it have an opportunity to export game to flash format (.swf)?

    3. Will it have native physics engine?

    4. Will it have native 3D support?

    5. Will it support vector images?

  • scirra.com/forum/viewtopic.php

    1. That bug was closed, because Scirra did not know how to fix it. But I suggested a very easy way to do it.

    2. This bug is not only in Intel XDK. It also happens with HTML5-games in many browsers.

paradine's avatar

paradine

Member since 22 Mar, 2014

Twitter
paradine has 66 followers

Trophy Case

  • 10-Year Club
  • Entrepreneur Sold something in the asset store
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • x29
    Popular Game One of your games has over 1,000 players
  • x4
    Famous Game One of your games has over 10,000 players
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

18/44
How to earn trophies