Our organization recently made the transition to Civil3D 2024 and since then every so often I get the following error when running Dynamo’s in the player:
This happens with dymanos that were made in the 2022 version and the 2024 version. I don’t get these errors when running in the graph. I’ll attach the error log as well - just looking for ideas as to why this happens since I didn’t get any ideas for the error searching around or from the error message itself. Thanks in advance.
New Text Document.txt (92.6 KB)
Hi @bfrankS5TGX,
Thanks for reporting. Would you be able to share a graph that causes this? You can DM me if needed.
U6177_PESC_SURFACE_BOUNDING.dyn (276.9 KB)
Here is a copy of the graph that caused the above error.
If I run it through the graph I never have any issues but when running it through the player most of the time I get the above error
Thanks. I did some testing and was unable to reproduce. Do you have a specific DWG that can be shared as well? Again, feel free to share via DM if needed.
For other folks that may encounter this issue, here’s the explanation. The graph shared by @bfrankS5TGX includes some custom dialogs from the spring nodes package. The error occurs when Dynamo’s backup interval is set to a small enough value that it will try to save a backup file in the middle of the graph execution. Let’s say for example that you have the backup interval set to the smallest possible value, which is 1 minute. The error will occur if you kick off the execution in Player and then take more than 1 minute to get through the data entry for all the custom dialogs. That’s why it doesn’t appear to reproduce consistently, because it depends on how long it takes the user to click through everything.
The workaround is to set the backup interval to a high enough value that it won’t get triggered while you’re running the graph (perhaps 5 mins or more). We will investigate further and see if we can come up with a fix.
1 Like
