Great update, thanks for all the ongoing work on better export and Steam support.
There is an issue with the Steam Overlay of the Steamworks addon. On some systems : it doesn't work and completely freeze the app window making it impossible to resize/close and without showing any error in the console. It happens to other C3 devs from the Discord too.
Reported the issue here: github.com/Scirra/Construct-bugs/issues/8328
Thank you for all the amazing Instance Bar improvements, also cool to see Steamdeck support is actively worked on!
Many thanks for the Tree control search improvement and for working on a cool Steamdeck export solution!
Will LTS support all export-related and service-related updates ?
Any chance to add support for auto-reloading "Files" folder on Preview please ?
github.com/Scirra/Construct-feature-requests/issues/330
No the APIS won't be the same and all add-ons ever created will need to be rewritten from scratch (+ many of them will be impossible to port), which is MUCH more tedious than fixing 1 line of code every 5 years if something broke by accident
By creating a compatibility disaster ruining EVERY customer's project ?
I'm using 4 years old add-ons and it's fine. If one break by accident, it's likely it would be fixable in some way by renaming a function or rewriting a little chunk of the code.
But soon, EVERY addon will break, EVERY addon will need to be rewritten from scratch and some of them (all the best ones) won't be possible to port.
2 months ago you promised you will support Addon SDK V1 documented features indefinitely in this thread. So it looks like the plan is to break this promise.
construct.net/en/forum/construct-3/scripting-51/method-access-engine-181244
The exception to all this is the documented, supported APIs. If you use those, we promise to support them indefinitely
You can of course stick to the documented APIs and do anything you like, and we promise to support that indefinitely
Sooo... according to the forum thread about addon SDK 2.0, you plan to break every single addon ever made for Construct 3 and every single project ever made with C3 using at least 1 addon on purpose in approx 1 year ?
What are you doing Scirra ?
Ashley answers on this issue is "There was indeed a small memory leak creating and destroying some kinds of objects which could accumulate over time."
As an addondev, I would like to know what "some kinds of objects" meant. Also it could provide better understanding on how to optimize our game performance.
Thanks for the fixes, Preview Button enhancement and 3DCam LookVector
"Possible long-term memory leak creating and destroying thousands of objects"
Could you provide more infos on when the memory leak happened when creating/destroying a lot of objects please ? (was that happening anytime an object instance was destroyed/a behavior instance was destroyed/in more precise scenarios ?)
Thanks for the great year !
Happy Christmas thanks for all the amazing updates this year !
Wow an other big update ! thank you for this, Xbox UWP export is huge.
Great to see you made backward-incompatible changes for Flowchart feature, this is indeed better this way !
However I still hope the full potential of Flowchart will be exploited by letting us Create Logic per Nodes (Node Conditions, Custom Node Types with "instances variables" and that kind of stuff). Right now it doesn't help us a lot VS the old way to achieve that kind of systems using JSON/Array or even just Game Objects connected with parent/child hierarchy relationships which is a shame.
Mockup, current issues details and their solution in this thread construct.net/en/forum/construct-3/general-discussion-7/new-flowcharts-feature-r370-179833/page-2
What a great surprise ! Very hyped about the potential of Flowcharts.
However I think it would be a shame to miss the opportunity to include logic within Flowchart Nodes with ease, as it's probably 70% of what would be amazing with such a feature. To create Behavior Trees, State Machines and Dialogues and enhancing the "instant" visual scripting capabilities of C3.
I detailed this suggestion and made a mockup here: construct.net/en/forum/construct-3/general-discussion-7/new-flowcharts-feature-r370-179833/page-2
We should be able to associate ACEs On Enter Node / On Exit Node / On Tick Node for each node. So for example we can play a sound, change a global variable, move the camera or do whatever we want for each nodes without creating huge error-proned string/token based else if statement. Also adding Conditions to Node directly would be amazing.
Member since 21 Oct, 2013