Halfgeek's Recent Forum Activity

  • Currently Crosswalk due to Chromium, but in Android 5+ (when it becomes more widely used.. which could take a LONG time), both should be just fine, with an edge for PhoneGap due to smaller filesize.

  • CJS canvas+ is generally better for smaller games due to small file size, faster loading etc.

    I still prefer Crosswalk/XDK for Android, its got really good plugin options, proper full-screen immersive mode for 4.4+, positional audio (works really well with headphones) and multiplayer if your game needs it.

    For my games, the smoothness advantage of CJS canvas+ is gone, I notice periodic stutters even worse than Crosswalk. I find my larger fleet battles remain smooth on Crosswalk and I have not had any complaints regarding stutters (which I notice myself, but it goes away after ~30s in-game, strange).

    When I did use AdMob directly with Crosswalk, I found the fillrate was >90%, most of the time 99%. With MoPub, the banner fillrate was ~80%. I did not use fullscreen Ads so I can't comment.

  • When I started, I made a big RPG, lots of stages & boss battles, full talent system, shops... it was around 3K events & ~15% CPU use, I thought at the time it was optimized. Then later on I rebuilt it from scratch, it was ~700 events with ~5-10% CPU utilization on an i5 3770K.

    You always learn new ways to implement features with C2's flexibility.

  • Seconds.

    You didn't test it to see?

  • A few days only.

    Apple locks out their dev console for a week, so you can't even see any details.

  • You can track the WebStorage issue here: https://crosswalk-project.org/jira/browse/XWALK-3252

    Thanks.

    It looks like they have a similar bug to CJS's WebView+ on the newest version, related to user profiles for storing data.

  • > I've definitely been experiencing these stutters and latency since well before Chrome 38. Aurel Aphrodite can you confirm?

    >

    I had things stuttering like year and two years ago already.

    Possibly due to nVidia disabling some of their GPU when detecting browsers, defaulting to the Intel HD graphics? I saw it was a known glitch. I didn't have such issues because I've been using AMD graphics for the past few years.

  • michael

    Chrome is the dominant browsers, for Win 7/8, so its the goto browser for testing for most of us. This isn't a C2 problem but... it is a C2 problem in the end, because we rely on these end tools to export.

    HTML5 is designed for the web, fine, we get that, but this situation is critical because the web (Chrome & Firefox being the bulk) currently is broken for HTML5 games.

    So atm, here's the export options:

    Chrome Store = can't use WebStorage, no functional IAP system. /seppuku

    Firefox Market = forget about it, performance is horrendous and stutters like mad.

    Direct HTML5 for browsers = If they are on recent Chrome or Firefox, its unplayable due to stutters.

    Android = wrappers rely on Chromium, its also affected by the stutter bug. Crosswalk is also plagued with security flaws that flag your app to be removed by Google. You just hope players don't mind the stutters. Maybe its on mobiles so they aren't as ******** as PC gamers are about such things... :/

    iOS = CJS WebView+ which uses WKWebView, great when it works, but its got a major flaw of losing save data to iOS8's auto-clean process when devices run low on storage. O_o

    Finally, direct PC/MAC/Linux export: Use an older NW else risk the stutters. Sadly Linux is still broken due to NW not updating library dependency. Looks like PC/MAC with NW 10.5 is the only viable option, even-though its not optimal (Steam Overlay, Cloud Save?)..

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
    • Post link icon

    Got the overlay to work in Greenworks v3 with NW 10.5 by using the --in-process-GPU flag, adding it to the "package-win.json" as well as "package.json".

    Working smoothly.

  • Thanks for the write-up.

    Looks like we're stuck with NW 10.5 for a long time.

  • It exports directly ready to play Mac Apps, without further need to "compile" in XCode.

    iOS is another matter.

  • 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.

Halfgeek's avatar

Halfgeek

Member since 24 May, 2013

Twitter
Halfgeek has 4 followers

Connect with Halfgeek

Trophy Case

  • 11-Year Club
  • Coach One of your tutorials has over 1,000 readers
  • Email Verified

Progress

13/44
How to earn trophies