- If you update a Variable from Python outside the Action Graph’s update context, the node network may not be notified of the change. Therefore, Print and dependent control nodes don’t react, even though the property’s output value updates in the UI.
- The Print node (with Print to Screen enabled) only reacts if the variable value change is recognized within Action Graph’s dataflow.
Typical workarounds & considerations:
- Instead of changing variables directly from Python, try triggering the change via an Action Graph node or ensure you script the value change within an evaluated node on the Action Graph (such as in response to a button or event).
- You may be able to force a refresh or trigger the network update by sending an extra signal through the graph—such as toggling another input or triggering a dummy event.
- Double-check you are not using a cached or stale value—re-query the variable’s value after the Action Graph has had a chance to process.