Yes, it will be.
In addition to Tom's comment, we're not aware of such complaints from any other beta users at the moment. Mysterious problems not experienced by other users are frequently caused by browser extensions interfering with Construct, rather than being caused by Construct itself, so try disabling any browser extensions you have installed. Otherwise in order to investigate any stability issues with Construct you'd need to file an issue following all the guidelines.
I had a look and everything seems fully up-to-date to me. Note that startPathGroup is part of the IPathfindingMap interface.
I'll double-check them, but please file an issue for any incorrect or missing TypeScript definitions.
three.js currently doesn't support advanced minification. I requested support and even did some work to add support for it, but so far the maintainers don't appear to be particularly interested in supporting it.
I'm afraid I've no idea what change could have been responsible for that. Graphics driver bugs can be highly unpredictable, and if the underlying graphics driver bug is not actually fixed, it's possible it could come back in a future release. The only way to make sure such issues are reliably solved is to report it to the graphics driver vendor.
I'll try to get a setting for culling in the next beta - I meant to do that for this release but didn't get round to it.
Thanks for spotting that, it should be fixed now.
The project has a breakpoint set which causes a free edition prompt - I'll update the project for the next release so that doesn't happen.
We normally update documentation after the next stable release. If you use TypeScript you can usually experiment with new APIs fairly easily with that as it uses the type definitions to help you call the new APIs correctly.
Update: it looks like the Asset Browser isn't loading anything due to an issue caused by the release system. We're looking in to it!
This release shouldn't have broken any of the public, documented addon APIs. If it did please file an issue.
It's the industry-standard version of TypeScript, it's not "Construct's TypeScript". I think this is just how TypeScript works.
If you're doing a local build with Android Studio, you may need to upgrade your locally installed version of Gradle.
Those are TypeScript errors. You might need to do something like add '!' to assert something is not null.
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.