I was just contemplating how to maybe catch this error and somehow reload the FileTexture node when it outputs NULL. I was thinking with the Try region, but when the output is NULL it didn’t actually throw an error:
(in this instance I just input an invalid path).
That proposed IsAssigned region might be nice, but it would also need some way to Reset the Region on Failure like the Try. Or maybe some combination of the 2.
I will also try with ManageProcess and see if I can reset the node (maybe with a limit so it doesn’t do it constantly) if the FileTexture outputs NULL, even though it shouldn’t.