Apologies if this issue has been previously addressed, but I couldn’t find any relative posts by the search. I have a script for creating an assembly out of a selected element with options for the user to select which assembly views to create, scale, view template and titleblock for the sheet. It then places the views on the sheet and applies the selected options. I used Dyno browser to load and run the scripts from the Revit toolbar. In Revit 2024, when running the script a second time, I am getting the error shown below. The element listed is an element that is a subcomponent of the main element selected to make the assembly of. After clicking OK, the next execution of the script runs correctly. So basically every 2nd run of the script the error message shows up listing an element that was included in the previous assembly. I am getting this error in multiple projects, so I have to assume it’s a Revit issue. However, if I run the script from Player or Dynamo, I don’t get the error message. I have never had this issue with previous versions of Revit.
FYI, for those who may be using Dyno Browser to incorporate their scripts into the toolbar, you will have to find another method for Revit 2025. Or at least I haven’t been able to find a work around.
Not likely Element Binding, as each execution would perform the exact same way. You can test by trying in a brand new workshared file (the GUIDS of the new elements wouldn’t align and therefore bindings wouldn’t either) or by opening the Dynamo graph in a text editor and checking bindings.
If you do find bindings, clear them out and see if it reproduces.
If bindings are eliminated while I do wonder if some of the complex nature of assemblies is at play, we can’t know for sure without a reproducible sample. As such the next step will be to see if you can trigger the issue via other execution methods - player, Dynamo Revit, Relay or other ‘add-in-indication’ or journal playback can all work as test methods.
If it doesn’t repeat in one of those methods, Dyno becomes the likely root cause - moving to the use of Player or another tool might be advisable as you need to rethink things in 2025 anyway…
Thanks for the response @jacob.small.
I don’t have that script set up in Relay or pyRevit, but may test if/when time allows, just to let everyone here know the results.
I am currently converting all of my scripts over to C#, so getting completely away from having to utilize any third party app to get the scripts incorporated into the toolbar. Plus, the compiled code runs so much faster. I did however, test the assembly script in C# and did not get the error, so I am on board as far as blaming it on Dyno browser.
1 Like
My understanding was that dyno was as good as discontinued due to challenges prorubim faced geopolitically. Relay or another similarly maintained app is probably best in the interim.
1 Like
Yeah, it’s been discontinued or at least the company that created the app, is no longer supporting.
I knew I was pushing my luck using it, but since I already had everything setup with deployment and updates, I ran the horse for as long as I could. So far it seems to be only an issue with that script and I will be done getting everything converted to C# here soon anyway, so not going to take the time to try to move everything over to another app. Just telling my users to OK the message and re-run the script again.
2 Likes
