Ashley's Forum Posts

  • Closing, please test again using r181. The guidelines request that you only test with the latest version of C2. Please also specify precisely how you are exporting to each platform: only Crosswalk or Chrome support multiplayer on Android (and only the latest versions of Crosswalk), and on PC if you are using node-webkit then the older versions simply do not support WebRTC.

  • Is your graphics driver up to date?

    Sorry, not much else we can do, nobody else is reporting this so looks like a system-specific issue.

  • Sorry, nothing we can do with just an error message, especially since this can be caused by third party plugins that we can't support. You'll need to follow the guidelines to get this investigated.

  • The iOS 8.0.1 update was botched but they've retracted it now and promised an 8.0.2 update in a few days.

  • The app themes are hard-coded in to our UI library. Since writing a new theme involves getting your hands dirty with C++ code and (as far as I am aware) static linking with the Construct 2 build, we're not really prepared to support any more custom app themes.

  • I can't reproduce in Chrome 37, but it does reproduce in node-webkit. I'm not sure why it would happen since the code is short-circuited to basically do nothing if you load the same image URL as is already loaded.

    This may be a Chrome 35 bug which is fixed in Chrome 36/37, so it may be that a future node-webkit update will have it fixed. If not try reporting it again but directly to node-webkit (https://github.com/rogerwang/node-webkit/issues) since if it doesn't show up in Chrome it's likely a NW specific issue and not a C2 bug. Alternatively the workaround is simple too, just don't repeatedly load the same URL.

  • Please always make one report per bug and follow all the guidelines. We generally require that a .capx attachment include no objects or events unrelated to the problem, and having three bugs in one .capx confuses this.

    I've fixed 2 + 3 for the next build, but 1 seems to be a trickier node-webkit framing issue. I am going to close this report since 2 + 3 are fixed, please post a separate bug report if you still want to see #1 fixed. (This is another reason you should only have one bug per report: I can only close or leave open the entire report, and this is a bad fit for a report with 3 bugs with mixed status.)

  • Closing as by design. If you 'wait' in a function call, you are waiting until the function call has completed so the function parameters no longer exist. Everything is working correctly here.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Thanks, should be fixed in the next build.

    SamRock - I can't see that problem in this bug report, please file a new report following all the guidelines if you want that investigated.

  • Yes - I should have made that clearer in the blog post I guess - PhoneGap is now equal to Ejecta on all our performance benchmarks, not just that one. It makes sense because they both are currently GPU accelerated but not JIT-compiled. WKWebView adds JIT compilation so will allow PhoneGap to pull way ahead of Ejecta, instead of simply being equal.

  • Yeah, as of r181 Construct 2 will blame the correct plugin/behavior in the error message.

  • Size is still a factor for c2 games, since google play and appstore has a 30mb limit for executables.

    It's actually 50mb for Google Play, and I don't think iOS implements a limit. Intel are working on support for expansion APKs to work around the limit, too.

  • Closing, not a bug (just need to document this).

  • If there is a PhoneGap Build plugin for it, you can write a C2 plugin with the Javascript SDK to use it. I think a bunch of C2 plugins for PhoneGap already exist.

  • It means nothing, until phonegap or apple fix their damn bugs where wkwebview cannot load files using file:// URL.

    Not quite - if you read the HTML5 game performance on iOS 8 blog post, it points out that as of iOS 8 PhoneGap is equally fast to wrappers, but has a lot more features. So you can start using PhoneGap already. And when the WKWebView problem does get fixed, hopefully in a patch soon, you'll get a big performance boost - way above the wrappers - without having to do anything other than rebuild with the latest PhoneGap.