Speckle 2.15 Released!

Hello @Community👋,

Speckle 2.15 is finally here and we thank you for your feedback, feature requests, and community testing. Feel free to update Connectors from the Speckle Manager. Also, make sure to update all Connectors at the same time.

Here is what’s new:



  • :new: Added support for Revit 2024
  • :new: Loading of missing families on receive from a local drive


  • Support for design options


  • :bulb: Light cones are now excluded when sending to Speckle

  • Send cropped meshes from the view filter

  • Levels and types enabled for Mapper.
  • Correct display meshes for instances with modified geometry
  • Refactored categories logic into a shared project
  • Fix for areas mesh and profile
  • Lots of instancing and other bug fixes


  • Receive objects from layers with invalid chars on the correct layers

Mapper for Rhino

  • Improved wall logic for extrusions


Rhino <> SketchUp

We have made some improvements on Rhino <> SketchUp Workflow. Here is what we improved:

  • Rhino layers → SU Tags
  • Rhino materials → SU materials
  • Rhino views → SU scenes
  • Rhino blocks → SU components
  • Rhino curves → SU lines
  • Receiving individual elements as components
  • Receiving Surface Edges from Rhino as hard edges in SU
  • Receiving Rhino breps as extrudable geometry

Mapper for SketchUp

  • :new: Added support for “Floor Mappings”

ezgif.com-optimize (2)

  • :new: “Mapping Source” added


  • :new: Create “Levels and Types” from Mapping Source

  • Default values for dropdowns
  • UI bindings
  • Adding Level relations to objects
  • UI improvements (Notifications)


  • Added support for sending/receiving views as Blender cameras.


  • Added support for sending Collection Instances with nested child objects.
  • Fixed issues with receiving nested Revit instances that contained hosted elements.

Structural Connectors

  • Tekla installer fix
  • Polygon mesher for CSi

AutoCAD & Civil3D

  • Support for AutoCAD 2024 and Civil3D 2024
  • CivilProfile:Profile class and updates ProfileToSpeckle conversion


  • :new: Support for classifications

  • Receive block instances
  • Mesh conversion improvements


  • New options for Versions sent from Navisworks which enable easier data analysis workflows with PowerBI and SDKs and a better Web Viewer experience (all opt-in for now):


  • First-Object data can now, optionally, coalesce to the Geometry nodes,

Before: with only Geometry data

After: with full First Object data

  • Full-hierarchy versions are now, optionally, possible. Select one node but send the full data tree from root to selection
    • Include internal properties. Normally hidden in advanced settings for power users, now enabled by the Connector, and…
    • Properties sent with internal names. They aren’t pretty prop names but will be consistent across different languages.
  • Improved User Experience
    • Granular progress reporting for those BIIIIIG sends we’ve been seeing.


  • Of course, bug fixes from Community Reports
  • Developer Mode


  • Where a long conversion fails to send, Retry Send won’t repeat the conversion - temporarily available as we scale the server to handle those BIIIIIG sends. This is step toward Offline-Mode.
    • Redirect Sends cached conversions to a new destination.

Power BI

  • Improved coloring logic with Color By input
  • Improved settings panel with viewer settings
  • New “conditional formatting” based on rules (applies only if no Color By input is set)
  • New viewer toolbar (with support for views, section box, zoom extents and color reset, the last one is experimental and will be removed in the future once coloring can be done in the standard Power BI way)

ezgif.com-optimize (1)

  • Support for custom views coming from the model
  • New setting to hide or ghost the context objects in the visual (any object that is not on the input data is considered a context object)


  • Speckle.Revit.Parameters.ToNameValueRecord → Gets a parameter object and returns a record with the parameter name as key and its assigned value. Simplifies working with Revit parameters in PowerBI.
  • Speckle.Utils.DynamicColumnExpand expands a specific table column, adding all its fields as new columns in the table.
  • New landing page with helpful links to speckle resources


  • Supporting custom CRS offsets and rotation


  • Mac manager installer
  • Cleaner UI
  • Stability improvements
  • Added GIS classes to specklepy


  • Expanded TraversalContext to allow inheritance. This allows more options for extending traversal to keep track of additional context.
  • Fixes for requests for invalid auth tokens failing.

Server & Web

3D Viewer

  • Text rendering support for text speckle objects.

Server & Frontend

  • Early Alpha Release for FE2!
  • Resolved a potential security issue where the x-frame-options header was not being correctly set for authentication routes. This header mitigates potential clickjacking attacks. This was identified via separate reports from security researchers Ahmed Chauhan and Kunal Mhaske, and we wish to thank them for their contributions.
  • Improved error handling and logging during object upload. This should enable better understanding of failed Sends, helping with the ongoing improvement of Speckle.
  • Improved logging and error reporting for the file import service, this should enable a slightly better understanding of failed file imports, helping with the ongoing improvement of Speckle.
  • Numerous version upgrades to dependencies; these upgrades address reported CVEs in these upstream dependencies.
  • Speckle server now requires Node version 18.16.1.


  • Prometheus metrics now report the status code of the HTTP response. This allows us to understand when failure error codes are being generated, helping with incident identification and ongoing improvement of Speckle.
  • Helm Chart allows the notifications email ‘from’ address to be customised.
  • Helm Chart enables the maximum file upload size supported by the ingress to be customised.
  • Docker Compose undertakes a HealthCheck of the running Speckle containers; this requires Docker Compose version 2.3 or greater.
  • HealthChecks for both Docker Compose and Helm Chart now include a timeout period, enabling slow responding services to be reported as unhealthy.

Tired of reading? Watch the reel :popcorn::