but adding some depth to 2D couldn't be that difficult, right?
Ha, ha, ha, ha hahahaha XD
Sorry, no, this radically changes everything. People who say "it's just an extra dimension right?!" have no idea what kind of tech goes in to this!
You should probably post to Intel's forums, where Intel staff can help you.
We don't officially support the CLI, you are generally on your own if you build it that way. Have you tried PhoneGap Build or the Intel XDK? If those work, I assume you misconfigured the CLI somehow.
Are you using the latest version of the Steamworks SDK as well? There's quite a few things to keep up to date here.
How are you building it? Are you using the Intel XDK, PhoneGap Build, Cordova CLI...? If you're building it yourself with the CLI have you checked for any errors returned by the web view?
Develop games in your browser. Powerful, performant & highly capable.
We're working hard on it. I'm afraid we don't want to release any information until we're closer to release!
Use 'point' sampling in project properties.
Closing, please follow the bug report guidelines.
NW.js is based on the same browser engine as Chrome, so I find it difficult to explain why there would ever be a performance difference between the two.
If you're talking about Canvas+, that has been officially unsupported for some time now, because it's incompatible with so many features it basically never works. So if you try to use it you are on your own and should not have any expectation of it working correctly. The Cordova exports which are based on real browser engines are the officially supported export options for mobile, and as far as I am aware, they are working fine for the vast majority of users.
It worked fine for me with NW.js 0.13.0-beta5, that's what the plugin was built for. Trying it with an earlier version might have corrupted the app data folder - try renaming the project and starting fresh with the right setup.
Apple want to prevent webpages from forcing themselves to go fullscreen. There have been various hacks to fake fullscreen in Safari over the past few years, and they usually break or get changed in the next iOS release. So anything you come up with will likely be brittle and break quickly. The best solution is to encourage use of add-to-homescreen, publish a Cordova app, or hope Apple implement the fullscreen API in the next version.
Member since 21 May, 2007 Last online 27 Oct, 2026
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.