Thanks for adding the rows/columns input so quick!
However I think it should first display Columns and then Rows as dimensions are always specified in the X/Y or Width/Height or Horizontal/Vertical Order.
Columns determine the Width, it's the amount of frames horizontally, and Rows determines the Height, it's the amount of frames vertically.
The axis logic and order should be the same for both the Column/Row and Width/Height inputs. Otherwise, we must think in opposite ways for both of them which is less intuitive
Can we still import spritesheet by defining column/row count ? Can't find it.
I always loved that Construct asked to import by column/row count and hated the process in other softwares that asks to define individual frames width/height dimensions.
Column/Row is the way Construct always worked before, it's much more intuitive and it's easier to count them directly on the spritesheet preview, rather than calculating individual frame/dimension or doing the trial/error way of guessing the dimensions in many steps.
Would be great if the default would stay column/row count and to be able to switch to frame dimensions using a toolbar button
(the new importer crashes a lot so maybe i missed something)
Cool update!
I'm still getting the Steam Overlay issue:
github.com/Scirra/Construct-bugs/issues/8328
Did you report the issue you faced while developing the Steam Overlay directly to Valve with the exact feature/enhancements you would need for better Steam Overlay support ?
I think the best would be to report it yourself (as you know exactly what is lacking currently) and post it publicly somewhere so we could all +1 your post and comment your request.
Great update!
Can't wait to switch to in-house exporter and Steamworks when it works reliabily on Windows. However right now it's broken for some windows users so the workaround isn't viable yet. github.com/Scirra/Construct-bugs/issues/8328
(if anyone is also experiencing this issue with Steam Overlay using last Steamworks plugin on Windows, could you share some infos about your system to help Scirra to fix this issue?)
The bug report is related to the Windows export with the Steamworks addon (i don't use Linux)
For some windows user, the Steam Overlay workaround for Windows Webview 2 doens't seem to work. Is this bug similar to the issue you're experiencing ?
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
Member since 21 Oct, 2013