Since 2022.1 you can refer in a Code Block to āDocument.ModelSpaceā, āDocument.PaperSpaceā and āDocument.AcDocumentā but all these returns null. I think someone accidentally made these visible or forgot to put functionality in it. It is only possible to point to āDocument.Current.ModelSpaceā and so on, even while these are not auto-completed.
For Binding Data Storage settings, all the Dynamo and Dynamo Player behaviors are save with previous version if no setting is changed.
For Store in Drawing for Dynamo setting, this is the scenario:
Binding data is saved to .dyn by default.
When we run a script on drawing1, the binding data saved to .dyn is the relationship between node and object on the drawing1.
When we run the same script on drawing2, the binding data in .dyn is reset to the relationship between node and object on the drawing2.
It means when we run the same script on drawing1 back again, the relationship between node and object on the drawing1 is gone. New objects will be created, not update the original objects. It might be an issue.
If Store in Drawing for Dynamo setting is on, we will use the binding data saved in drawing when run script in Dynamo. For the above user case, the issue is solved.
I have this same issue. I did a fresh install of Civil 3D with 2022.1 and dynamo is not appearing on the manage tab despite having the proper license permissions. Is anyone else having this issue.
I had the same issue, but with the 2022 install (not 2022.1). Installing 2022.1 actually fixed it! Anyway, you can get around it by doing NETLOAD for the AeccDynamo.dll file in C:\Program Files\Autodesk\AutoCAD 2022\C3D.
Unless it is disappeared. After 2021.1 installation I didnāt have Dynamo available anymore in Civil 3D 2021. If I search the Program Files folders I can only find this dll in 2020 and 2022 locations.
Wow bindings are bizarre. Utterly useless. Itās as if they havenāt anticipated at all that people make scripts for their teams to use, and that every time you tell your team āhey change this setting so that my script will workā, or āhey you have to remember to run as adminā, or āhey IT let the team run this one software as adminā, many wonāt, efficiencies are lost, and your efforts are wasted - the exact opposite of what Dynamo should be.
I just want a node that will let me āturn offā object binding, so that in relevant scripts a user who knows nothing about Dynamo except how to use Dynamo Player can run a script, and then run it again selecting a different target object, without undo-ing what the first run did.
If you arenāt aware yet, the binding settings can be changed in 2023 without admin rights. This isnāt a solution if your team is on 2022 for awhile, but good to know I guess. More here:
Thanks, thatās good to know, I do expect weāll be going to 2023 at some point. When my team isnāt too busy I get to focus on Dynamo, so whenever I get back to it I get to learn about all the advances to Dynamo while I was busy on other things
And hey, I discovered your Camber package this week, after struggling and failing to get some python code to work for setting ACI colours on layers. Your work is making mine a lot easier.