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.
The SDK version 2 supports all documented APIs that were in the v1 SDK. It will only break addons if they ignored a warning in our SDK documentation saying not to use undocumented features. The SDK version 2 also uses an industry-standard design also used by all other software and tools in the industry.
The aim is to stop compatibility disasters that repeatedly end up ruining customer's projects.
What makes the Addon SDK v2 so important that it's worth breaking all 3rd party plugins?
Ending compatibility disasters that ruin customer's projects.
All the documented APIs in the v1 SDK are still supported in the v2 SDK.
Addon developers need to update their addons to SDK v2 and they will continue working.
That explains it - the experimental features setting allows opting-in to the same defaults as beta releases use, so it will default to WebGPU enabled with that.
Please contact supportqaw@construct.net for any queries about payments.
WebGPU 'Auto' mode is giving me the WebGL renderer in r388, so it looks like it's working as intended.
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.