The point of the zip format is you have normal files and don't have to base64 encode anything. I was talking about a zip of web assets - just all the normal files you'd otherwise use on a web server, but zipped. If some particular network has a format that uses a zip file but still requires base64 encoding files within that, I'd say that's a pretty weird format and I don't think we'd want to support that for the same reasons as the single-file format. Nothing should need base64 encoding at all. So please ask them as well to support normal zip files.
See this thread: construct.net/en/forum/construct-3/general-discussion-7/new-admob-sdk-20-x-deprecated-182891
As we have said we will keep supporting it so long as it is feasible to do so, but in future it may well become infeasible. If continuing to support single-file playable ads blocks us from making significant improvements to the rest of the engine, then we will probably be forced to drop support for single-file playable ads in order to be able to continue improving Construct for everyone else. This is why we have asked everyone affected to contact their ad networks and ask them to support the zip format - we can likely support that forever with minimal maintenance required. We can't allow the difficulty of supporting single-file playable ads to hold back the entire engine.
Perhaps you're using a third-party addon that also needs updating.
We routinely get far more requests than we can possibly act on - if you want to suggest a new feature you can file it here including an explanation of what you need it for. Alternatively if you need advanced typography features you can try using HTML Element and HTML layers, which lets you use CSS styles like text-align: justify for text.
If you run in to a problem please file an issue following all the guidelines.
Construct uses spritesheets instead of animated image formats. Spritesheets also allow compression between similar parts of images on the same sheet.
If you run in to any problems please file an issue following all the guidelines.
If you run in to a problem please file an issue following all the guidelines, otherwise we cannot help.
If there's a problem with this release, you can find older releases on the releases page and keep using an older version for the time being (and ideally report the problem to us by filing an issue or sending your project to support@construct.net). If the project does not open in older realeases, it's probably been somehow corrupted - you can still send your project to supporttgq@construct.net and we can try to recover it, but sometimes corrupt projects are entirely unrecoverable, so we can't guarantee anything.
This issue appears to have already been filed here, and it will be followed up there. It looks like the issue also occurred in r388.2 so it's not a regression in this release.
I tried this out in r396 with Space Blaster and it all appears to be working correctly for me. In general if you believe there is an unexpected problem with Construct, please file an issue following all the guidelines.
If your project uses loader layouts, it is possible it was changed due to a bug fix related to them - perhaps your project was previously relying on the bug to happen.
There was no intentional change to how the "Preview" button works. Any intentional change would have been covered in the changelog. Note you can change what the "Preview" button on the main toolbar does by clicking the dropdown arrow next to it and selecting a new option under the "Main button" submenu.
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.