There’s a lot going on in the speckleverse, so we thought it’d be helpful to put out a changelog of what’s new on the latest versions of the connectors, web, and SDKs. Thus, welcome to the first changelog
We’ll endeavour to continue posting these as new versions are released
If you have any questions, please feel free to drop them below. Now, let’s get into it!
Invites! This can be used to create a fully private, invite-only server - or just quickly and easily invite others so you can easily share a stream with them!
Server
Fuzz testing in the CI
Security patches
Deployment guides
Published on docker hub!
Frontend
Real time notifications! You will be notified in real time in the browser of various events: stream creation, commits, etc.
SDKs
.NET
Added helper methods to send and receive in Core
Published on NuGet!
Python
Package has been renamed specklepy - please update any scripts to reflect this!
Welcome to the community @Dickels112 ! We have a few basic Civil3D conversions on the table this sprint (alignments are top priority), but most likely solids will be in the backlog for a while.
Glad to have a Civil3D user on board though, suggestions & requests are very welcome on the connector thread! On that note, feel free to introduce yourself here when you get a chance
Thanks @clrkng !
The reason I am asking this is that all coordination and integration with other software is not done on the basic Civil3D classes, but usually ends up with solid conversions. This goes from plan production, up to coordination and validation. even IFC only uses the solids (IFC 4.2 is not integrated, IFC5 is not even close to market). This, of course, is the same class as the autocad solid, with some added parameters (propertysets).
I will take it up with the connector thread!
Hey @Community, Dr. Changelove is here wishing you all a happy May the Fourth!
On this special day we are publishing our changelog from the team’s latest sprint in both the regular, and the Star Wars formats (warning: plays with sound)
See what the Speckle team has been up to in our latest sprint
Revit
Feet & Fractional Inches supported in Revit. Apologies for not supporting this earlier. We think in metric!
Fixed a bug where the default account would get unselected when creating a stream
Fixed a bug that would cause the connector styling to affect other add-ons you might have in Revit
Grasshopper
New Extend Speckle Object component. This is a cool new node that allows you to add custom properties to objects in a more natural way - similar in behaviour to how the Create Speckle Object component behaves.
Old Extend Speckle Object node is now called **Extend Speckle Object by Key/Value**
Fixed Schema Builder error when adding custom properties.
Excel
New Excel connector! Just released on the Office Store, go grab it! ♂
Server & Web
3D Viewer
Blocks support! Now you can visualise blocks (and nested blocks) exported from Rhino, Autocad and Civil3d! [Cue: I put a block in your block dawg meme.]
Server
Digital Ocean One Click image has been approved! This is really exciting as it allows you to have your own Speckle Server up and running in “one click” on Digital Ocean. **Check it out here!** (affiliate link) All you need is a domain name or subdomain to point to your IP.
We’ve also added a bunch of optimised endpoints for uploading and downloading objects.
SDKs
JS
New version of the JS ObjectLoader has been released. Alongside streaming objects one by one, it now allows you to receive an fully constructed object (e.g., the whole commit object). Makes it easier (but also less memory safe) to operate on structured Speckle data.
Server diffing support: when sending or receiving data from a Speckle Server, we’re now utilising a smart diffing algorithm to send only the data that’s needed, and receive only the data that you don’t have locally already.
This should greatly improve the time spent in uploading/downloading from Speckle, especially in the cases where the changes you’ve made are small (e.g. moved or changed just a couple of objects).
python
New in 2.2.0: Improved Server Transport
Thanks to the new Server endpoints, sending and receiving has become more efficient! The transport take advantage of this by checking the server before sending and will only send objects if they are new. On the other end, the local cache will be checked upon receive so only new objects are pulled form the server. This should speed up your sending / receiving as you update streams.
Hey @Community , you might have seen another notification from Manager today as we have released a new version of the connectos (2.1.21 to be precise).
Here’s a breakdown of all the new things and fixes we’ve worked on the last sprint. As always, any questions / feedback / concerns / wishes just say so!
Connectors
Revit
adds support for sending Recap point clouds
adds support for stacked walls
fixes block scaling issue when sending/receiving blocks from Rhino in imperial units
fixes issue when sending/receiving views from Rhino
fixes issues when receiving edge case curves and lines
fixes issues when receiving unconnected shaft openings
fixes crash when using Revit in Deutsch
Dynamo
fixes bug when receiving a specific commit
Rhino
downgrades Rhino Connector to require Rhino 6.28.20199.17141 for a broader compatibility
Autocad Civil
adds support for sending corridors (as meshes)
fixes issues with blocks
Grasshopper
adds Synchronous Sender and Receivers (thanks @Stam !)
fixes issue when sending commits with too many objects
You might have seen another red notification popping out today inside Manager ,as we’ve released v2.2.2 of our connectors and a new version of our web app. This includes many improvements and fixes, including:
massive speed improvements in all our .NET connectors (Revit, Rhino, GH, Dynamo etc…)