This doesn't affect how you make events. It's an internal feature of the engine that is applied automatically.
We're still working on it. We hope to add the option to export with the C3 runtime soon.
You must first switch your project to the new C3 runtime. See this blog: construct.net/blogs/construct-official-blog-1/c3-runtime-alpha-now-available-950
What do you mean by "operational"? Are you talking about the conditional expression? That is compiled to a JavaScript conditional expression, but the test is mainly bottlenecked on drawing and rotating instances, so it's not really a suitable test for measuring event performance.
Filed an issue for remaining C3 runtime work: github.com/Scirra/Construct-3-bugs/issues/1646
Soon I think I'll move my remaining todos to issues on github so you can see the status of it.
Both! It's always used.
That affects the runtime. Locking only makes sense for the editor, because that's where you select objects.
Are you looking for this? scirra.com/forum/construct-3-desktop-build-beta-currently-win64-only_t199344
It's already there - try locking the layer!
It's not yet supported, but we hope to add it back soon! There's more details on the current state of the C3 runtime here: construct.net/blogs/construct-official-blog-1/c3-runtime-alpha-now-available-950
Yeah, the web devs are aware, they should have a fix soon!
Just filed a Chrome bug to change this: bugs.chromium.org/p/chromium/issues/detail
We're only planning on doing videos for stable releases at the moment. The video will summarise everything in all the betas since the last stable release.
Please report any issues here following all the guidelines: github.com/Scirra/Construct-3-bugs/issues
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.