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.
What do you think would make us grow a lot faster?
Thanks for the heads up, I just fixed the links.
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.
We are still focusing on 2D and Construct is still primarily a 2D engine. The new sub-layers feature is a good example of a feature that is mainly useful for 2D games.
If you have any problems please file an issue following all the guidelines, as we need all that information to be able to help!
That situation should never happen in the first place. If it does, please file an issue so we can fix it.
It's still not clear to me from this why you can't just make changes in the editor. If you do that, then how it's saved on disk doesn't matter.
Please file issues on GitHub as we need all the requested information to investigate, and issues mentioned elsewhere are easily lost, forgotten or missed.
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.