I successfully wrote a very useful dynamo graph that will read the current dwg file, list all the layouts, and then execute a command or series of command that I tell it on each layout tab. Very useful for repeating something on a series of sheet layouts.
Advantage: took me a few hours of tinkering to get it to work well whereas if I had tried to write this in lisp, I’d still be working on it next December!
Minor disadvantage: If this were a lisp routine, it would run much faster. While I was able to get the dynamo routine associated to a command line entry that I assigned in my acad.pgp file, I noticed that it takes about 30 seconds before it actually runs the graph, presumably because it’s loading the dynamo ‘engine’ and then running the graph. Now, if I want to rerun the graph, with new commands - say I forgot to do a step or two, it’s the same thing all over again.
So, my question is this: Is there a way to pre-load the dynamo engine and leave it available to cad without having the dynamo player open? (I’m old - I like the command line.)
I’m not a C3D user so I may be missing something obvious here, but are you running in Player or opening the full add-in? Player will load everything into memory the first time in an instance but it should run faster on consecutive runs.
Gotcha. I don’t know if it’s possible, but I think you’d have a hard time having the command line leave a background instance of Dynamo open to rerun within the command line again. That’s not really the intended workflow for that case. Player seems like the better fit for running multiple graphs.
Runnjng via player will give you faster execution on the second run, and will provide more functional inputs, AND will allow you to run more than one graph without previously knowing all the dynamo file’s paths.
This seems uncharacteristically long. Would you mind sharing your graph? There might be some performance optimizations that can be made in the logic. Does it take this long to run in the main Dynamo workspace as well?
I might be wrong about this, but I believe AECRUNDYNAMO needs to not just execute the graph but also open the Dynamo CLI instance, which can take awhile (see the engine load time on the splash screen).
