*A C# node that outputs System.DateTime.Now.ToString()
*A Context Print that reads that data back out to Rhino
I compile this GH script into a plugin and import it into Rhino as a command.
The first time I run the script, it will return the correct timestamp. Any future time I run the command, it will return the old timestamp.
I assume that because the tool has no inputs, the configuration of the script is being cached and returned to save calculation time.
The expected behavior, which is that the current datetime is called on each execution, occurs if the script is called via the grasshopper player. So what we’re doing at the moment for our drafting team is making a dummy command in the rhp that calls the actual gh script.
@will this is related to our CI/CD conversation earlier - can you confirm if Grasshopper scripts with identical inputs from Rhino’s perspective cache old results?