Ashley's Forum Posts

  • As part of the requirements for a project I need to provide the finished game as one html file, with all scripts, images and sounds inline.

    Why is this a requirement? I can't think of any good reason for it, and as mentioned in the suggestion, it actually makes the game considerably less efficient.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Just put the host on a fixed server.

  • The public runtime API documentation is here: https://www.construct.net/make-games/manuals/addon-sdk/runtime-reference

    It's early days though, there's still a lot to add. The runtime has a huge API surface.

  • You need to update the plugin ID in the language file, too. There's a couple of places it appears.

  • 88% of Android devices have Android 5.0+, which supports an auto-updating Android System Webview app. (Later versions of Android don't even have the app, they just use Chrome directly.) To support Android 4.x you have to use Crosswalk, which is now deprecated by its own developers. So by now I think it's reasonable to just require Android 5.0+.

  • Pretty much what I suspected - Chrome 37, from 2014 :P Closing as not a bug. Check for software updates in the Google Play store, if you can make sure the Android System Webview and Chrome are both up-to-date it should work.

  • Also not sure about this but would you mind uploading the "hacked" part of the zip library you're using to Git if possible? (If it's not too deeply coded into C3 itself.)

    Sorry, that would be a bit of a nightmare. The code is all mashed up with the NW.js exporter itself. It's a pretty ugly hack.

  • That looks like a browser. I meant checking with the Browser plugin in the APK. It's not necessarily the same. Your screenshot does indicate an old Chrome version too (65, when 67 is now out), so it does look like you are not staying up to date with software updates.

    We've seen web views as old as Chrome 30 (from 2013). It's not reasonable to support such old platforms. Generally there is a tiny number of people using them, it's incredibly difficult to test and code for, it clogs up our code with compatibility cruft, and it makes it harder to make optimisations and write new features if we hold back on using the latest web platform features. Besides, if you don't install updates, your device will gradually become more insecure as the number of known and unpatched vulnerabilities steadily increases. So you probably want to keep it up to date just for that!

  • The support check is correct for all up-to-date platforms. I verified this on my own Android device and it was correct.

    Use the Browser object and set a text object to the UserAgent expression - that should show you the Chrome version in use. It's quite a long string though so make sure the text object is big enough to contain it all.

  • You don't need to modify the official plugin anyway. The Instant Games plugin loads the Instant Games library in to the global FBInstant. So you can just create a new plugin and make your own calls on FBInstant. And that avoids the terrible compatibility nightmares of modifying the official addons.

  • That code is necessary to correctly detect support on the most recent versions of Firefox and Edge.

    Which version of Chrome or the Android System Webview do you have on your device? Is it up-to-date?

  • Can't reproduce here. The multiplayer chat example checks if multiplayer is supported, and if I build a debug APK and run it on a HTC 10 with Android 8, it works fine. Multiplayer is detected as supported and works in the chat room.

    Is the device's Chrome or webview app up-to-date? If it's old it might not fully support multiplayer.

  • I'm afraid there's very little we can do about a report like this. We require a project and steps to reproduce with bug reports because we need them to actually investigate the problem.

    Generally issues with force close suggest a crash in native code, not Construct's code, and the fact it relates to WebGL would suggest it's a GPU driver bug. There's very little we can do about that either; the GPU vendor would need to fix the driver.

  • Closing, please see the bug report requirements for posting in this forum. Please use the other forums for general questions.

  • Now I know what you're thinking but I'm not asking for a backport but rather would like to ask, how did you manage to fix/workaround this issue?

    By using a zip. It took a few days solely to reverse engineer the zip format and figure out how to hack our zip library to put the right flags in the right places.