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.
The manual covers static variables: they don't reset, and act more like a global variable with a limited scope. The term "static" comes from the keyword used in C++ which does the same thing for local variables there.
There's no change to WebGL support in this release. Even old browsers support WebGL and should continue to support Construct projects just fine.
The problem is in the long run, pretty much all parts of the internal engine will be rewritten/upgraded/improved, which means all addons accessing internal details of the engine will be broken, and all projects using them will be broken. There is a real risk of a serious disaster in future with a great many projects being ruined. We have a difficult choice between taking disruptive action to guarantee that cannot happen any more, or continuing to allow increasing disruption from customer projects being ruined in future. I strongly believe that despite the disruption, taking action now is the right choice to ensure compatibility on a 5-10 year time scale.
All Construct releases for at least the next year will still support all existing addons. There are more details about the schedule in this thread.
The drag & drop behavior has not been modified in this release. If you run in to a problem please file an issue following all the guidelines.
At the moment, projects years in the making are already at risk of being permanently broken by Construct updates. This is happening and we are getting desperate customers contacting support and sadly there's little we can do to help them. This is the problem we want to solve, and this process is necessary to ensure that in the long run - years down the line - this no longer happens.
Customer projects will continue working fine if addon developers co-operate and update their addons to the SDK v2.
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.