working on getting Revit 2023 up and running. Copied my 2022 project startup script to make a few adjustments for R23 and when I open it every node is stacked in one location and all the groups are missing. I starting pulling them out and trying to organize but what I have below is just fraction of the nodes. Is there a way to open this without the file being totally F’ed?
Edit: Upon further inspection it seems like the file is even more messed up. Every code block is blank and I can’t edit those nodes at all.
Mostly losing a ton of sleep, and pulling my hair out. kidding
I actually spend a lot of time in the source code poking around and that extension does a pretty outdated method of loading a file from JSON and if it hiccups a bit too much it spits out the in-progress graph which has no node locations.
One thing I find interesting is, I have been told numerous times by the DYnamo team that “the workspace references plugin can’t be the problem”. So, I am pretty pumped that you just confirmed what I have been telling folks for a little while now.
For IronPython2.7: Yes, you will need to install a package now because they swapped the engine to CPython3 on us for Revit 2023. With that change, they broke packages like Clockwork, Data-shapes, springnodes, and more. So simply install the package and you will be good to go.
Oof… sorry you’ve ran into these issues @crapai We have a task logged from a github issue that is already on our radar, but this helps provide more ammunition on it.
We will investigate both issues expressed above on our end. The Workspace References extension may be an issue @john_pierson but could also be a red herring. We’ll dive deeper!
Do these errors surface in the Dynamo log file? If so posting that (with the Revit journal) here or on the GitHub in an issue could provide the development team what’s needed to identify the source.
I doubt there is anything wrong with the particular graphs - and it’s much more likely a dynamo problem - unfortunately kind of hard to reproduce for us so far.
I doubt that too, it’s just that it is important for our project startup, so if it needs to be recreated to get around this error than I should get started. I’m going to try just copying the graph before it breaks into a blank and see if that workaround works.
I tried coping the graph nodes into a blank file, saving it, and opening and it is also producing the error.
So for now, if I need to start a project, I need to copy our 22 version, open it with “WorkspaceDependency_ViewExtensionDefinition.xml” disabled and run it.
I ran it in the player, first time using the new player btw, nice.
It completed with warning, but honestly I can’t find anything that it missed. My versions of this graph from 21 and older had additive features that required me to change file paths to get the correct Revit version of families. Since 22 I’ve changed the script to be completely subtractive so the version isn’t as important. I might have to still have a 23 version because I doubt we will be needing a demolition workset now.
EDIT:
Just ran it again and it missed some things, so I think it depends on the input I’m selecting.
Finally got a chance to look at this again and try to figure out what went wrong.
As mentioned above I was able to open the graph while “C:\Program Files\Autodesk\Revit 2023\AddIns\DynamoForRevit\viewExtensions\WorkspaceDependency_ViewExtensionDefinition.xml” is disabled. However, when I save and try to open the file I get an error “Unknown error opening file:” this causes the file to fail to open entirely.
I started open the file, deleting a part of the graph, saving as a new file and attempting to open it. I immediately saw results. I was able to narrow it down to one group, at which point I saw that one code block had an error. “invalid Associative_Factor”. The code block is simply a nested list that I was using to organize some thoughts while working on the graph. The code block is on the bottom left.
I opened the graph again, deleted that one code block, saved, and successfully opened the file. I then re-enabled the .xml file and was able to open the file without the node stacking. If I attempt to open the original un-edited file the nodes becomes stacked and I can see the error.
kidding
We have a 
