Closed GalaxyTimeMachine closed 1 year ago
I reset to 2ff34879665508ee5c84da8d4f4b9ad404c65732 and the error has gone...along with some of my nodes!
@GalaxyTimeMachine Sorry for the inconvenience. I have modified the node that was causing the issue. If you git pull it, hopefully that fixes the problem for you. Let me know if you have any further issues.
That works, thank you!
I update the UI and all custom nodes every morning and have just hit this error after updating 30 mins ago: