Why would you have an invalid layer name in a layout file though? Is this something that comes up with merge conflicts with source control or something? It seems vanishingly unlikely that something like a hardware failure causes a few bytes in a layer name in a JSON file to be written incorrectly without affecting the rest of the project.
There are thousands of ways a project could be corrupted, and many of them probably can't show any good or actionable error message (e.g. should Construct be able to say "the second half of this JSON file is overwritten with all zeroes"? Is it even useful to you if you see that?) We occasionally make improvements only where we see it happening with real projects and there's both a good and actionable error message we can show.
Actually I don't think f16 will work for shader parameters - currently Construct always writes those as f32. However you can immediately cast the value to f16 and do any further calculations with reduced precision.
Construct defines an f16or32 type for shaders. It's documented here.
If you run in to a problem please file an issue following all the guidelines.
If you use VS Code, it actually uses the same editor as Construct does (Monaco). If you use an external editor and enable 'Auto reload on preview', you don't need to do any re-importing, so it should work similarly to before but using a different app instead of a popup window from Construct.
Yes, we'll release an LTS update with the Android update, but note it won't be for a while yet.
You can save your project to a folder and use an external editor.
'Airborne explorer' was added in r433, whereas this is a patch based on the previous release r432, so it doesn't have anything added in r433.
I don't know what exactly you are referring to, but to be clear, our policy is only to delete content that violates our Forum & Community guidelines.
There should not have been any change with legacy functions in this release. If there is, please file an issue and we'll take a look. Note however the legacy function feature was deprecated over 5 years ago and it may eventually be removed in future, so doing the necessary work to switch over to the new functions feature may ultimately be worth it if you still want to keep updating to new versions of Construct.
I just tried exporting Spell Caster with image optimization and it worked fine for me. This is very common, which is why we have our bug report guidelines - we really do need all that information to be able to help.
It's not clear what issue you're talking about. If you run in to a problem please file an issue following all the guidelines, as that makes sure you provide enough information for us to be able to help.
No, the terms and conditions remain in effect and any reverse engineering or attempts to circumvent license restrictions are still prohibited.
Please note: after first publishing this release we quickly identified a server configuration change needed for the new code editor. If it doesn't look right, try clearing your browser cache and reload Construct.
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.