Skip to content

1.9.2
Compare
Choose a tag to compare
@MostafaElAyoubi MostafaElAyoubi released this 03 Dec 10:33
· 1 commit to master since this release
1.9.2
8214429
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Some releases take more time than anticipated, and some others less 😊. This new version includes some major improvements for Rhino and Grasshopper Auto UI Form. It also introduces more improvements to package management performance and stability, along with some general user experience enhancements.

🦏 Awesome enhancements to AutoUIForm for Grasshopper

🍳 Update baked geometry when rerunning from AutoUIForm !

Update.Geometry.mp4

🔗 Disable Element Binding if you with to create new geometry at each run, exactly like the AutoUIForm in Dynamo

Disable.Element.Binding.mp4

ℹ️ We have enabled outputs in the AutoUIForm for Grasshopper! All you have to do is add * out * at the beginning of the name of any component and their content will be displayed in the outputs panel of the Form

Outputs.mp4

⏯️ Added support for Grasshopper Button components! Clicking the button passes the "pressed value" and runs the definition

2024-11-27_12-28-53.mp4

(Thanks to KPF Design Practice team for sharing this escalator generator tool for testing !)

📦 Better package update operations

Dynamo In Dynamo

One of the main source of issues with packages and their updates is the very long file paths that don't allow the usage of the standard System.IO methods. We got rid of many of the issues that this was causing and are adding one to the list with this release:
When trying to update packages, Orkestra makes sure they are not being currently used by Dynamo or any other process. Files with file paths > 260 characters would make this check fail. We have now implemented a way to address those and report the name of the process that is blocking the update.

Grasshopper In Grasshopper

  • We have moved our local settigns backup from Temp (which was very hard to navigate) to %programdata%\orkestra\RhinoSettings.
  • We have also implemented a backup system that keep previous settings to make sure you're able to recover all your tool in case something goes wrong.
  • We have change the timing of the reset of local settings : it used to happen when Rhino was closed, but the Rhino updater or other processes that kept Rhino from shutting down completely often caused issues. We now reinstate local settings at Rhino startup, which behaves much better.

ℹ️ Better information on save operations

One common thing we have witnessed is that sometimes it can be confusing to open a definition from Orkestra Online (in Dynamo or Grasshopper), make changes and save them using the default Dynamo or Grasshopper save, and not have those changes updated on the cloud.
The reason for this is that the default Dynamo and Grasshopper save function only saves the local version of your tool, the one that has been downloaded to your computer. If you wish to save the changes back to Orkestra Online, you'll need to use the "Cloud Save" or the "Push to Orkestra" buttons in the Orkestra Panel .

save back to orkestra online

To avoid any confusion or loss of work, we have implemented a little popup that lets you know when you're saving a definition opened from the cloud locally!

popup to let people know they are saving a cloud definition locally

💬 Commit logs can now be multi line text, with a maximum of 200 characters to make sure they're kept short! 😁

multi line commit message

🐞 Bug fixes and improvements

  • 🐛 Fixes login with SSO in civil 3D 2023 and older
  • 🚀 Improved package update logic : better handling of super large packages and python libraries with thousands of files
Assets 3
Loading