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 supportynp@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.
The addon has been updated to use the latest version of Greenworks (v0.16.0 with NW.js v0.86.0 and Steamworks SDK v1.59).
Thanks, fixed the typo!
Follow the rest of the tutorial series and later on it covers modules, which should go over what you need.
This error is only known to occur in Electron, which is not supported. Use a supported browser like Chrome or Edge.
Some of the project's images appear to be corrupt. For example this icon file is logged in the console as an invalid image: gabriel.jemail.us/games/paperhorror2d/v1.0/icons/icon-256.png
Presumably a similar problem has happened to the project's other images. This usually indicates a problem with the uploaded files, or a server configuration issue. It is not normally a problem with Construct itself.
Browsers provide Web Bluetooth, Web USB and Web Serial APIs, providing a few options for direct communication with a device. Providing you can get a device to connect, and find documentation on the protocol (e.g. how to send and receive messages to perform various functions), then it should already be usable (possibly involving JS coding though). The new 'BBC micro:bit raw communication' example shows how this can be done - it uses the Bluetooth and Binary Data objects to communicate with a micro:bit device directly. All the BBC micro:bit plugin does is wrap that in a nicer interface.
This may be a problem with your web server. See Publishing to the web.
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.