Dynamo 2.19 Release

Hello, everyone!

We’re excited to announce our latest release, Dynamo Core 2.19! Check out a quick blurb below:

Dynamo 2.19 comes with a much-improved search feature that provides more relevant search results. It adds a zoom state, unique shape, and tooltip information for package nodes, improves the Python editor experience, and provides better documentation for chart nodes. This release introduces a variety of quality-of-life updates, including the ability to drag and drop notes to pin them, a new setting to control whether exported image file names include a time stamp, and more.

For full details on this release, check out the release notes !

Learn more about the release in our blog: Dynamo Core 2.19 Release - Dynamo BIM :page_facing_up:

When you’re ready to dive in, you can download the release here . Be sure to let us know your feedback under this post! :writing_hand:

Previous few release blog posts:


As part of this release, we have revamped Search using Lucene! This means that Search has changed a bit, and we want to articulate some of the differences here.

Buckle up, enjoy the ride and please do give us feedback in this thread as we seek to tweak it to be even better :pray:

Lucene Search is a high-performance, full-featured text search engine that allows us to move on from the original, bespoke implementation and leverage the full knowledge of developers whose speciality is Search - big win! :mag_right:

When searching for Nodes in Dynamo, we currently use the following fields:

  • Name
  • Category*
  • Search Keywords
  • Description

*Please note that the shelves in the Library are not the Categories in this context. These Shelves are somewhat artificial, designed to make finding nodes easier without forcing the development of them down a certain pathway.

The Categories referenced here are things like Core.Input (Node namespaces) utilized by the Dynamo in Nodal development.

For example:
Search terms; "list join"

  • here we utilize the empty space " " for separating words.
  • We will find nodes with:
    • list in the Name
    • join in the Name
    • Contains list in the Category like all the nodes in “Core.List”.
    • Nodes that contain list or join in the Description (If it is repeated several times, it will gain more weight).
    • Nodes that contain list or join in the SearchTags (More repetition here gives more weight)

Currently the period . operator behaves the same way as the space " " above, but we’re investigating if this is better suited to be a specifier - i.e. instead of a separator it becomes part of the full node-name as depicted in Dynamo’s UI that allows you to type.

Each search field has Weights associated with it, covering:

  • Fuzzy
  • Normal
  • Wildcards

Each of these weights gets calculated on the above Search hierarchy and re-calculated for successive terms / keystrokes with a slight usability delay.

Problem areas:
We’re still not done yet, as explained above we don’t yet pair the full node name as depicted in Dynamo. This means you may be searching for a Sphere.ByCenterPointRadius and not quite get the answer you expect:

For example:
Search terms: "Sphere by center"
Result: You may notice that this doesn’t return the Sphere.ByCenterPointRadius node in the first few results. This is due to:

  • The node Name is ByCenterPointRadius and the Category is Geometry.Sphere.
  • When using spaces in this Search term, Lucene will try to get:
    • Nodes with Sphere, By or Center in the Name
    • Nodes in which the Category is Sphere, By, or Center
    • Nodes with Sphere, By or Center in the Description
    • Nodes with Sphere, By, or Center in the SearchTags

In the short-term, and generally, you may have better search results by using the latter part of a node name, but suffice it to say that we’re looking at tweaking this even further so that results are as predictable as possible! :pray:


Hi @solamour, I’m using version 2.19.3

and I’ve encountered a strange repetition of nodes in the left-side library.
For example:

So, Is this a bug or a feature?:slight_smile:

Can you post your dynamo log file for review?

Hi @jacob.small

this one?
dynamoLog_4c260ed8-b0ef-41a7-861c-c0e73d12a85c.txt (3.8 KB)

Hi @solamour

With the newest updates of Dynamo strange results appear. The point is that as soon as a string corresponds to Double, additional decimal zeros appear in it (by default). Below is an image of a simple example, but I noticed this in C3D when I started getting attributes of blockRef value.000 format (these were element numbers).

Do you see the same result on your PC?

Hello @ana.ortizMPU5K - This is a known issue that has been resolved in the next release. Unfortunately it slipped in our release builds :frowning: So our sincerest apologies for that.

It is only a visual bug and all numbers are still the same under the hood (You can test by exporting to CSV).

1 Like

I did some tests and indeed the visualization part is different from the actual. thanks for the reply. hope for an update from you soon.

1 Like

Hello @ana.ortizMPU5K - this is now updated in Dynamo 3.0 and beyond to correctly show on Integers. We’re still working on making floating points better for doubles for a future release.


hi, super cool thanks for the tip