Dynamo player update loop

Dynamo Player
1

Dynamo Player — “File Content Change” Loop on Every Script (Civil 3D 2025)

Environment:

  • Civil 3D 2025 (version 25.0s LMS Tech)
  • Dynamo for Civil 3D (built-in)
  • Scripts stored on a network server (mapped Q: drive)
  • One user (me) has no issues; one coworker experiences the loop on every script

The Problem:
When my coworker opens the Dynamo Player and selects any .dyn file, the Player immediately enters a continuous loop between “Ready to Run” and “File Content Change” — resetting all input selections back to defaults with every cycle. This happens before the Run button is ever clicked, and it affects every script, not just one specific graph.

What We Have Tried:

  1. Local copy of the file — copied the .dyn to C:\Temp\ on his local machine and pointed the Player at the local copy. Loop continued.
  2. Manual run mode — confirmed all graphs are saved with Manual run mode, not Automatic. No change.
  3. Removed Watch nodes — disconnected all Watch nodes from the graph in case they were causing a feedback loop. No change.
  4. Binding Data Storage set to “No Binding Data Retained” — changed this setting on both machines via Dynamo menu → Binding Data Storage. No change on his machine.
  5. Network path vs local path — tested both. Loop occurs on both, ruling out a pure network/file-watcher issue.

What Works:

  • The same scripts run perfectly in the Player on my machine
  • The same scripts run correctly in the full Dynamo editor on his machine
  • The issue is exclusive to the Dynamo Player on his machine

What We Have Not Yet Confirmed:

  • Whether his Dynamo build version exactly matches mine
  • Whether a Civil 3D repair install would resync his Dynamo installation
  • Whether his machine’s antivirus is touching the file even when stored locally

Questions:

  • Has anyone encountered this “File Content Change” loop specific to one user/machine?
  • Is there a known Dynamo Player setting or DynamoSettings.xml entry that controls file watching behavior?
  • Could a mismatched Dynamo build version between two Civil 3D 2025 installs cause this?
  • Is there a way to disable the file watcher in the Player entirely?

Any help appreciated — this is blocking our team from using Dynamo Player for shared script deployment.

2

If the network drive has mirroring or backups of basically any kind people who aren’t the author can experience this. Player needs some degree of control in the JSON structure of the dyn, so when they set it a value and the value isn’t the same as the source the backups start to trigger which registers as a file change which causes the issue. Shared OneDrive links and antivirus tools can cause the same problem.

The easy fix is to use robocopy, group policy, or any other method (your IT team can handle this bit) to copy the files from the network to the local disc for standard graphs. Project specific can stay on the network, but coordinate how you access it and keep it to read only. Hosting on Forma can be a better solution in those cases.

3

Thank you for your help! I was very confused at first because I had made a local copy thinking this would break the link to the server updates but I guess it doesn’t (I’m still new to the cloud server concept). Apparently copying a file from the server maintains a link to the server; but if the file is downloaded from the server using a web app, the server doesn’t view it as a file needing constant updates which solved the issue.

TLDR: Cloud server bad; local copy bad; downloaded file good.

@jacob.small Thank you so much for your insight!