It has been pointed out to me that it is far more useful to display the NodePath in the warning than the name of the node, as there may be lots of nodes sharing the same name in a project. This PR fixes this.
WARN_PRINT("Interpolated MultiMesh transform should usually be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] MultiMesh interpolation is being triggered from outside physics process, this might lead to issues (possibly benign).");
WARN_PRINT("Interpolated MultiMesh transform should usually be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] MultiMesh interpolation is being triggered from outside physics process, this might lead to issues (possibly benign).");
WARN_PRINT("Interpolated MultiMesh transform should usually be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] MultiMesh interpolation is being triggered from outside physics process, this might lead to issues (possibly benign).");
WARN_PRINT("Interpolated Camera transform should usually be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] Camera interpolation is being triggered from outside physics process, this might lead to issues (possibly benign).");
WARN_PRINT("Non-interpolated Instance "+node_name+" transform should usually not be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] Non-interpolated Instance is being triggered from physics process, this might lead to issues: "+node_name+" (possibly benign).");
WARN_PRINT("Interpolated Instance "+node_name+" transform should usually be set during physics process (possibly benign).");
WARN_PRINT("[Physics interpolation] Instance interpolation is being triggered from outside physics process, this might lead to issues: "+node_name+" (possibly benign).");