Custom Node Behaviour unexpected

No, for my case I do not use dynamo sandbox. I work only in dynamo for Revit

my usual workflow is very similar to the video i sent. I work in dynamo workspace to test, then when i’m happy with the result, I copy nodes and close worksapce. Create new custom node and paste in my content. adjust inputs/outputs etc and save/close

1 Like

Hi Sol,

Here are 2 recordings with the Python node edition of Clockwork and Genius Loci packages.

Dyf name change

Dyf name change 2

1 Like

@BrookePeterson @Alban_de_Chasteigner - I see your videos, but can’t seem to reproduce on my end… so there must be something else going on here :thinking:

Builds on my machine:

  • Revit 2023.1
  • Dynamo Core 2.16.1.2727
  • Dynamo Revit 2.16.1.6510

Are you both in a similar build? Could there be an addin conflict? We’ll need to figure out how to get the same results to investigate on our end.

Thanks for your reply :

Revit 2023.1.1

Probably not related but DynamoIronPython package is not installed on your computer.

The name change happens when I click on the File tab to save the script edit.

1 Like

Ah, interesting… installing the Python Package did let me hit the bug :slight_smile: Sweet… let me loop back with the team on it!

2 Likes

Yes, also one similar build

Revit 2023.1.1
Dynamo Core 2.16.1.2727
Dynamo Revit 2.16.1.6510

And yes, i do have the DynamoIronPython package installed.

I have noticed that the name change happens by no action at all simply time.

Open new workspace, place custom node. Edit Custom node and wait. After around 30 seconds it renames

2 Likes

Hello all - We have now a reproducible way to do this internally and have filed a task to address this for the next Dynamo release (2.18). A big thanks to you all for pointing us in the right direction for this :star_struck:

5 Likes

@solamour Probably silly of me to ask at all, but is there going to be a hotfix for Revit 2023?

It seems to be a workaround to immediately do a save-as to the node after opening a custom node for editing.

Edit: NO

Even editing a DYF with nothing else open, the DYF will rename itself to backup.dyf

What is a current workaround except wait for a repaired Revit update?

Thanks Sol for your, and your team’s efforts!

I second Andreas request for a Hotfix pretty please!! :smiley:

The workaround I am using at the moment is to take a backup copy of my .dyf before opening for editing. After i edit I do a save-as to a temporary location. After saving the file I manually edit the .dyf file using text editor and replace the updated Uuid with the original Uuid from the backup i made. This allows me to copy the new node into my package location and existing .dyn files still recongnise it as the same node.

To be fair I only use this locally in our internal environment since I don’t publish my package Online to the package manager. I don’t know what affect this would have in your published packages?

2 Likes

That’s a clever hack. Doing an immediate save-as after opening the DYF seems to be needed, too.

Edit: I tried that, replacing the Uuid and changing file names but it didn’t work for me. Also, the nodes come back to be all on top of each other.

We’ll explore this, yes. It depends on whether or not Revit are going to release a hotfix, so we need to talk with the teams responsible there :slight_smile:

1 Like

So there won’t be a fix until the next Revit 2023 update? We cannot really update Dynamo for Revit separately, anymore, yes?

Is there actually a workaround until then? I am updating many graphs from 2022 to 2023 and it requires editing DYFs.

There is a way, yes, as you can see in this post: Error - specTypeId is not a measurable spec identifier? - #17 by scott.tomlinson

Technically and officially we don’t support this behavior as it’s not been tested, but theoretically it should cause no harm. It’s a use at your own risk kind of thing.

Note that the fix is not yet out, and we are targeting 2.18 for it right now if it’s not too complex :slight_smile:

1 Like

Hello everyone,

Has there been any update? Has the problem been resolved?
I’ve been experiencing the same issue recently.
I’m using Revit 2023.1.3 and Dynamo 2.17.

Thank you!
@solamour

1 Like

adding that i experience this behavior on Dynamo Core 2.17.0 / Dynamo Revit 2.17.0

We have fixed this in Dynamo 2.18, which should be in Revit 2024.1 :slight_smile:

@solamour I don’t suppose you’d have any insight into whether an updated dynamo will make it’s way into any new Revit 2023 updates? The slow moving cogs of large business have meant we won’t be able to get onto 2024 for a while yet :smiley:

There have been some amazing dynamo leaps but cant take advantage of them due to being stuck for now on Revit 2023

We’re looking into that now :slight_smile: For the Dynamo updates we rely on Revit patch cycles, so we need to piggy-back on top of that.

The tricky thing is the matrix of stuff that Dynamo touches and testing (i.e. Geometry kernel, base Revit API’s, Analytics tools, DLL’s that conflict with other addin’s etc.) meaning that we don’t release features backwards but rather only target bug fixes, stability fixes, performance fixes, memory leaks etc. in ways that are :100: verifiable and tested.

It’s a tricky balance, because we need to be confident that any fix doesn’t make things worse and the further back the Revit version, the more out of sync it becomes.

#lifeOfSoftwareDevelopment #theJuggleIsReal

2 Likes

Yeah, that’s fair enough! Definitely appreciate your work, and thanks for looking into it :slight_smile:

1 Like