IFC exporter and all of those totally show up as Addins in this manager, if they are installed.
Okay, more testing:
- Removing all of the Packages from Dynamo also didnt quell the issue.
- Removing all the Dynamo VIEW EXTENSIONS, DID make the problem go away.
Now to see which extension or combination of extensions, seems to be causing this issue.
I may have spoke too soon. Now that i removed all the packages, AND all the extensions, and put them all back one at a time, it seems to not want to crash anymore (which (i guess) is a good thing?).
Going back in the active project to see if it behaves now.
Crashed right away when i tried it in a real project. What the actual hell! LOL
Yeah - something (In Dynamo or Revit) is causing things to happen out of sync.
Might require a procmon dump at this point. 
One other thought now that we have ruled out add-ins and network access: is desktop connector doing anything with any of the things?
Interesting Point!
Sooooo, nothing out of the ordinary. But Desktop Connector does something whenever its a project on ACC now, right? Like, it used to be that you didnt actually need DC running, but (i think) now you do?
But thats interesting. I might have crossed wires because for packages and extensions i tested in a blank unsaved file. Hmmmmmm.
1 Like
Okay. So, you nailed it that it seems to be ACC related. It crashes if im in an ACC model. If im in a regular unsaved file, it does not.
I killed DC so its not running at all, still crashes.
Current status: No Revit addins running, No Dynamo Packages, no Dynamo View Extensions, DC is disabled. If i open an ACC model, and tell Dynamo to go âOpenâ using the Open Icon while a graph (local) is opened⌠ded.
1 Like
Yeah - going to need tech support on this one so we can loop in the Dev team.
Either (a) something is off about one of the various parts of your Revit install, (b) youâve stumbled into an ACC/Revit/Dynamo bug that no one else has found as they arenât using all 3 tools at once, (c) there is an add-in while disabled is still partially loading somehow, (d) there is a Dynamo customization which is in conflict with the rest of the stuff on the system, or (e) there is an infosec policy preventing access to some part of the system after another part of the system is called which is causing the crash.
And it could be any combination of the 5, in whole or in part.
Can you submit an issue via the github? If not I can tomorrow; note that many of my colleagues on the Dynamo for Revit team are tied up with AU stuff so it may take a bit longer than usual to get it picked up.
I submitted an Autodesk SR about it. 23148366.
I dont know how to file/make issues on github. :-/
1 Like
Ok - I can give you a how to someday if youâd like (always like to turn a
into a
). The SR should work fine - just a more difficult platform for many to access.
1 Like
this is a long thread so I may have missed it - but can you please disable all dynamo packages you do not need, especially the dynamo migration graph assistant one.
Hey there-
Already tried it. We have:
-Disabled all packages (except the ones in use in the graph)
-Disabled all extensions
-Disabled all Revit addins (except Dynamo)
It DOES now seem that it is graph specific, but its affecting all of the graphs i was testing at the time. So its a combination of:
- The graphs in question
- Revit 2023
- The project/model being on ACC
- The packages the graphs use
If i take any of those 4 out of the equation, the problem goes away. But i can reproduce it on the regular, on any of our machines.
2 Likes