NW.js is for all intents and purposes the same as Chrome. It is separate to the Chrome browser so there aren't other web pages that might jank the page. But there are other benefits that still apply to NW.js, such as allowing main thread work to happen in parallel.
The performance benefits of worker mode are covered in this blog post. It applies to all platforms that support worker mode.
It should be live right now!
Here it is referring to the new HTML Element plugin.
If you run in to any problems please file an issue following all the guidelines.
If you run in to any problems please file an issue following all the guidelines, as we need all that information to be able to help.
It works fine for me. If you run in to any problems please file an issue following all the guidelines, as we need all that information to be able to help.
Make sure it is correctly configured as per the manual guide.
Please do this for any issues - anything mentioned anywhere else is easily lost and forgotten, and often can't be investigated without all the details requested by the guidelines.
Isn't the limit on the Google Play Store 150mb? How would you publish such a large APK?
Besides a 600mb build would involve transferring about 1.2GB every build (if 600mb up and 600mb down). It could well be much faster to do your own local builds anyway.
Please file an issue following all the guidelines otherwise it's impossible for us to investigate.
The release notes of each update include this.
Just use Ctrl and +/- instead.
It should already be supported. Providing there are the same number of 3D shapes and sprites, each 3D shape will take the initial animation and frame from a corresponding sprite instance.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.