Hello @Pit - The post above by @Michael_Kirschner2 has found the issue, and provides a workaround in the short-term as we look to make a more comprehensive and cohesive fix. Please use that to unblock right now!
After some struggling, I found that only nodes for ‘selection’ cause the error.
My workaround is as follow.
- Save as a temporary file after replace all nodes for selection with custom node temporarily on Revit 2022.
- Open above file on older version of Revit, then correct the replaced nodes.
Thanks for your suggestions. As you can imagine, besides testing if dynamo works as it is supossed to work, I have as well my day to day work related with what dynamo is suposed to properly do. All this kind of issues are making me think if I am In the correct platform to produce. If I were a Dynamo tester i would have tested and accepted the solution before.
I understood Hyunu_Kim solution not the pasted lines of code suggested some days before. After proceeding how Hyunu_Kim suggested the node can be opened but it has to be rebuild again.
As a partial solution It works.
Have a nice day.
We are actively working on a fix for this right now @Hyunu_Kim - so it should only be temporary. We sincerely apologize that this happened and are improving processes to ensure it doesn’t happen again
Hello @Pit - Totally understand, and we deeply apologize that this bug made it out into the wild
We do spend a large amount of time manually testing, and the vast majority of Dynamo nodes/features have tests written for them that will tell us when things go wrong. Beyond this, we are now improving our processes to ensure this particular flavour of problem doesn’t occur again
As for the solution, I’m glad that the one from @Hyunu_Kim worked for you! In case you were curious, the solution that @Michael_Kirschner2 proposed is as follows (For education and/or fun if nought else):
- Dynamo files (file.dyn) can be opened using Notepad.
- When you open these up, they use the JSON file format which uses a series of curley braces to demarcate things. If you want to view how this is organized, you can paste your .dyn file into an online JSON viewer.
- Inside of the .dyn file, there is a lot of information about things like; what nodes you have, their location, what wires connect to what, if you have groups etc.
- @Michael_Kirschner2’s suggestion was to directly edit this file to revert the change that we made that caused the bug.
- To do this, you can do a find operation on the text for
hostSelectionand replace them with
Selectionfor any node that was marked as IsInput.
- Ensure you do this outside of it being opened, and save it. That means, when Dynamo opens up the file, it will correctly deserialize (i.e. read the data needed to open up your graph in the correct way).
@solamour I wish I could set two solusions. haha.
Using notepad seems pretty easy, but some would prefer my workaround who doesn’t like to deal with strings like me .
I believe Dynamo was invented for them at the first place.
Thanks for your detailed explanation.
@Hyunu_Kim - Definitely! One is a bit more technical, the other is easier to understand Just wanted to showcase how you could do it with manual editing!
DynamoRevit2022_BugFix.dyn (15.7 KB)
This is somewhat similar to the approach we are looking at, but would be an extension that automatically does it in the background! I too get my kicks out of using Dynamo to interrogate Dynamo stuff.
I will hopefully be creating this extension repo today - will update this reply with a link.
@Michael_Kirschner2 has written a post on this issue, here: [faq] My .dyn/.dyf file from 2.12/2.13 won't open in older versions of Dynamo
Please have a read if you come to this thread!