ViewFamilyTypes node issues

[J.Wehmer]

This is part of a graph that I have been using for a while now, until today it has never thrown me an error as such. Every instance of this node in my graph is behaving similar to the one in the image.

The View Type still exists in the project, but it is throwing me errors. We upgraded to Dynamo 2.0 last week, but it has not caused issues like this so far.

Is this a issue with my Dynamo, or a deeper issue with the package?

A temp fix I have done today has been to simply replace the node in the graph, but the issue comes back after I run the graph 2-3 times.

[Alban_de_Chasteigner]

Hi,

A topic with the same issue was created yesterday.

Output duplicating when opening a script

Hi @AndrewWalker, Rhythm isn’t updated for dynamo 2.0. [Rhythm] You can find the reason here : john_pierson 24d Adding to this complexity are the changes in Dynamo 2.0.x versus 1.3.x. I am trying to get ready for an upgrade but want to make sure to have backwards compatibility. Getting rid of the DYFs helps ensure this.The reason being, I really do not want to have Rhythm for Dynamo 1.3.x and Rhythm for Dynamo 2.0.x. Node model nodes must be written differently in Dynamo 2.0 and it exp…

The answer was that you can use OOTB categories instead.

[john_pierson]

@J.Wehmer

Is this a issue with my Dynamo, or a deeper issue with the package?

The link @Alban_de_Chasteigner posted summarizes it well. Essentially Dynamo 2.0 has a load of changes that are difficult for developers to implement with things like BILT right around the corner… Rhythm will not be fully compatible with Dynamo 2.0 until after BILT North America at the least.

[john_pierson]

Rhythm has been updated to add Dynamo 2.0.x support. Download version 2018.9.7.

[J.Wehmer]

Thanks @john_pierson!

Excited to download the update!