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 supportmam@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.
Yes, we are planning for the SDK v2 to support all the same documented features in SDK v1. This work will continue over the next year. If you have found something missing you can file a feature request and we will prioritise work on it.
If you run in to a problem, please file an issue following all the guidelines.
Ah, I think I missed function parameters when implementing this. I'll add that for the next beta.
We don't plan to make Construct in to a full 3D engine. We're trying to offer viable ways for addon developers to go further with 3D features without needing to wait for us to turn Construct in to a full 3D engine, which will probably never happen.
We don't intend to make Construct in to a full 3D engine. This at least gives addon developers a way to do more 3D features without having to wait for us to turn Construct in to a 3D engine. If you don't like it and want us to make a full 3D engine, well, that probably won't happen. So you'll be waiting a long time! Would you prefer it if we didn't try to provide additional ways to use 3D in Construct? If such efforts only result in negativity, maybe we shouldn't even try, and we'll just stick to 2D features from now on.
Developing enough features for a full 3D engine in Construct is likely many years worth of work. There is an endless list of complex features that true 3D engines usually support: 3D collisions, 3D physics, animated 3D models, screen-space ambient occlusion, lighting, shadows, deferred rendering, physically modelled materials, various 3D-specific optimizations, and on and on and on. So yes, adding more features for 3D is very difficult and an endless amount of complicated and time-consuming work. Construct remains primarily a 2D engine with some basic 3D features which you can often use to good creative effect (take a look at examples tagged 3D in the Example Browser). If you want more advanced 3D, and you can make things work by embedding three.js, then you get a fully-featured 3D engine with all that already available right now. Otherwise if you want more advanced 3D built-in to Construct, you may be waiting for many years to come.
It's part of the engine. It means very old and unsupported browsers show an error message instead of a blank screen.
It's a pragmatic option. If you'd rather see a 3D engine as powerful as Three.js integrated directly in Construct, you may find yourself waiting a very, very, very long time. Or you could use that option now. It allows layering other Construct content both above and below the 3D content, and it was not easily possible before the new APIs added in this release.
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.