I’d recommend searching the forum, there are a lot of discussions about this subject.
@Alien ’s suggestion is a good one, but maybe doesn’t address the core question about a “way to convert these scripts into a format that Dynamo Player can run in its default configuration”.
To me, the short answer is: Replace all Custom Nodes with Python.
I recall a long back and forth (I thought recently) about this where @jacob.small came out very against this idea, as it puts the onus on you as the developer to update whenever the Revit API or Dynamo changes, whereas if you use packages the maintainer of the package (in theory) takes some of that burden off you. I can’t seem to find that discussion, but he makes his point here:
Remember everyone: Exposed Python means you have to edit every saved version of that dyn on every system at each breaking update, maintaining a separate folder for Dynamo graphs for each year. Whereas Python nodes in a package means you can edit that package at each release, push to end users on log in, and users can use the same graphs for multiple versions.
Assuming you can track every ‘save as’ of your DYN file’s forever, the amount of work is the same while the user experience is a bit mor…
@steven.jensen has a super detailed post about his method here:
Manage scripts and package versions, Deploy to the company, Secure your dynamo graphs, while letting people experiment and learn if they are interested.
Goal of the deployment setup:
Develop the graphs out of public view and test them before deployment
Get “official” published graphs onto all the PCs, and keep them unaltered
Make the “official” published graphs easy to find
Keep all PCs up to date with changes in graphs and packages
Allow for the curious to explore, experiment and develop …
Also this:
I am a new BIM specialist at my firm. Over the course of a couple months I’ve been slowly convincing my staff on the benefits of Dynamo and automating time-consuming processes. I’ll soon want to push out graphs for my staff to use through Dynamo Player, but the question of packages has come up.
For the staff to run the Dynamo graphs properly, they need all the packages I’ve used to make the graph. Not many are adept at Dynamo enough to search and install the packages for themselves.
So in your…
and this:
Hello,
General use question for Dynamo Player here:
I’m working on a Dynamo graph that can be used in Dynamo Player by general Revit users in my firm that have no Dynamo training. The graph is just a simple tool for Revit users to easily adjust some lineweight / print settings across an entire project via Dynamo Player.
If I add a node from a custom package to the graph, does that then necessitate that anyone running the graph in Dynamo Player have the custom package installed on their own wo…
and this:
To this wonderful community,
I am attempting to enlighten the end-users with the power of Dynamo Player. I am the only dynamo-savvy-python-person in my office. The issue i’m having is that some of my graphs use custom packages (clockwork, springs, etc…), and the end-user does not have the time to learn how to install custom packages from the package manager.
How can I incorporate custom nodes into my graphs so that the end-user does not have to install each required package?
I am aware that s…
and this:
I have deployed 20+ dynamo graphs to several offices using a master repository that gets mirrored to the individual PCs. As engineers we have to use all current versions of Revit that are available to be compatible with various Architect’s files. My goal is to have people just use Player to run the graphs. If people do get interested in creating Dynamo Graphs, this is managed by providing the most used packages in the repository so they do not need to install any, and resetting the default dyna…
3 Likes