Ashley's Forum Posts

  • We support Ludei's Webview-based platforms via the Cordova exporter (they are cordova-compatible). Canvas+ will remain deprecated: it had far more problems than Crosswalk.

  • I replied to the bug report. If it works in Chrome but not in NW.js it's clearly an issue with NW.js.

  • Ashley: I know you're probably sick of me pointing to this, but I would really love for you to read these two articles and then tell me if this is not a technology worth considering

    Given the number of people here criticising us for "depending on third parties too much", I am extremely wary of adding any additional technology dependencies in to the C2 workflow. Even if Haxe works pretty well, we could still get shafted by compiler bugs, missing features and unoptimised parts that kill the performance. In particular I think Stencyl got burned by some of these types of issues. I'd rather stick with HTML5 - it may not be perfect, but it's improving fast and has some huge players backing it, such as Microsoft and Google.

    slowly replacing parts of the engine with asm.js code?

    IMO this is a much better idea than writing native exporters. I do want to do this eventually, but it still means rewriting a big part of the runtime, and probably breaking compatibility with all existing plugins. So I want to do this eventually, but it would probably come post-C3 release.

    Also regarding native exporters - one of the reasons C2 is $129 for all exporters and not $999 is that we only have one codebase we need to maintain. All that extra engineering work would probably push the price up to another level. And "all exporters for one price" is a really nice thing about our licensing IMO.

  • If the game has loaded, then 'On start of layout' will trigger in events (even in a loader layout). Before that, what are you hoping to do? There's only a loading bar showing.

  • I really can't do anything with my users, can't change webview's core in their apps...

    This is why we recommend using Crosswalk - you get the latest Chromium engine with Android 4.0+. Also from Android 4.4+ the web view is based on Chromium, and from Android 5.0+ it auto-updates the web view as well. So this will be fully resolved once Android 5.0+ reaches majority market share.

  • I can see a different object lighting up, but is there any way you could simplify the .capx at all? If it's just 2-3 objects and it reproduces right away without having to interact, it would be a lot easier to investigate.

  • Closing, please follow the bug report guidelines (attach a .capx etc)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing as won't fix, we can't support the Android browser as it is old, buggy, lacks many features and is no longer maintained. Recommend to your users to use Chrome for Android instead, which is available on Android 4.0+ (the vast majority of devices).

    We won't integrate your code as it seems to rely on heavily modifying the document through several jQuery calls. We would definitely need to test that very carefully over a range of devices before releasing, but instead we would prefer to advise to use Chrome.

  • Closing as not a C2 bug, sounds like a local network config problem.

  • Are your graphics drivers up to date? Other than that, there's nothing much we can do unless you follow the bug report guidelines, which includes attaching a .capx demonstrating the problem.

  • Should be fixed in the next build, thanks.

  • Closing, please follow the bug report guidelines - there is nothing we can do without the steps to reproduce and all the other information asked for.

  • Closing as not a bug. Seams may appear between exactly adjacent objects when you use floating point positioning or scaling. Since you use "letterbox scale" here you will very likely get floating point scaling. To guarantee seamless rendering you need to use letterbox integer scale, point sampling and pixel rounding. Or just use the Tilemap object and enable seamless mode.

  • Closing as not a bug, you've just discovered the double floating point precision limit.

  • Closing, please follow the bug report guidelines (attach a .capx, and also note what aquinn said).