Are you using WebGL effects?
If the devices you are testing (and aiming) don't have that much of computing power, and you don't want your game on tablets, then you can decrease the resolution of the images. Still, I'm interested in what devices did you use for testing?
Construct 3 will be using the same HTML5 runtime, so it will stay a HTML5 engine. That means, you'll have to use wrappers. Note however that they are improving, so as the ability of the smart devices to support webview applications.
Welcome to the Scirra Community Feel free to ask your questions and have a good time with Construct 2.
If you optimize your code and avoid using too much effects then you should be fine with the 1280x720 resolution. However do test your game on different devices from the beginning. Then you'll see if a newly added feature/object/effect slowes the game down.
If there would be a 4th option, I'd say cloud storage Are you designing this API especially for Construct 2?
It should work, that's how I did my game too. Plus, mine was an old XDK project so I had to remove and re-add all the plugins in XDK. But don't worry, if it builds for you then you're done.
It looks good. Thank you for this effect.
You just have to change the CLI version in XDK and rebuild it. If you didn't make any changes in your project, you wouldn't even have to re-export it. It should work easily, only if you use some 3rd party plugins (or your previous XDK project was really old) then you can have some issues.
Here's a picture of what you have to change:
https://dl.dropboxusercontent.com/u/166 ... ersion.png
Thanks for the heads up, now I know it's possible. Hopefully someone will clear it up why it's not included.
Develop games in your browser. Powerful, performant & highly capable.
Anything that'll allow me too use multiple light sources and many shadows without WebGL is all I need.
I don't think that you'll get that without WebGL. Ashley said that in the future, when 98% of devices will run WebGL they plan to drop the Canvas2D renderer because it's holding them back from implementing more advanced rendering features.
There was a discussion about this before and (if I remember correctly) there's a browser limitation that prevents the HTML5 apps from doing that kind of stuff. Someone correct me if I'm wrong.
Member since 8 Sep, 2011