No nodes visible in Graph requires complete restart of Revit and Dynamo

[ThomasMahon]

Dynamo version

2.1

Operating system

Win 10

What did you do?

Opened a graph, created in v2.0 but saved in 2.1

What did you expect to see?

A working graph

What did you see instead?

Missing nodes in the graphics display (see image) which requires a complete restart of both Revit and Dynamo. Its inconsistent; it might work correctly after 1 restart or after a couple.

Opening the graph in manual execution seems to be more successful.

Nodes are combination of ZT and the OOTB TextNote. This node seems to have performance issues; its causes a noticable pause in graph execution when it first runs; any subsequent run where it has to re-execute is significantly faster. This is just a hunch, but opening in automatic mode and the graphic display issue I reckon might have something to do with memory issues caused by this node. Any ideas? I've seen other users report this issue before.

[johnpierson]

We just ran into this same thing with a graph that was used without issue in Revit 2018 + Dynamo 2.0.2 (upgraded from 1.3.4) and then opened in Revit 2019 + Dynamo 2.0.2. We do have a graph we can share with the Dynamo team too.

[QilongTang]

@johnpierson It would be great! Are you saying you can reproduce this constantly?

[johnpierson]

It was happening consistently when we were testing this week. Let me email you the graph. 👍

[johnpierson]

Well, I finally got around to testing the graph on my end (that my colleague was having the issue with) and it opened just fine on my machine. So it may not be as reproducible as I thought with this graph.

One thing we do know is he has a lot of add-ins installed on Revit and I do not.

He receives the following errors:

While loading assembly CoreNodeModelsWpf, Version=2.0.2.6826, Culture=neutral, PublicKeyToken=null, Dynamo detected that the dependency Xceed.Wpf.Toolkit, Version=3.0.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4 was already loaded with an incompatiable version. It is likely that another Revit Addin has loaded this assembly, please try uninstalling other Addins, and starting Dynamo again. Dynamo may be unstable in this state.

It is likely one of the following assemblies loaded the incompatible version:

KMCore, BIMOne.BIMTrack.Addins.Common

[QilongTang]

@johnpierson That is very likely the issue, WPF incompatibility may cause the node UI not render correctly while node model loads fine.

[mjkkirschner]

@ThomasMahon do you see similar notifications about Xceed?

[dhanjeetsah]

Hi @Amoursol, @johnpierson , I had the same issue today with Revit 2021 and Dynamo 2.6. I fixed this issue by following the steps below.

1. Close your Dynamo if it is opened. Browse C:\Users\USERNAME\AppData\Roaming\Dynamo\Dynamo Revit and locate 2.6 (the issue is with Dynamo 2.6)
2. Rename this folder as OLD or with any name.
3. Start Dynamo from Revit. This will recreate the folder as 2.6. Note: You have to add the path in “Manage Path settings” if you are using custom package path locations. Hope this helps. cheers, Dhanjeet Sah

[SpeakUp03101998]

It returned to normal when I uninstalled a newly installed add-in, I'm sure it caused some unexpected interface changes.