Red Nodes
I've been making a logo intro in Shake, it's probably one of the more involved scripts I've ever constructed in Shake. 200+ nodes, lots of macros, etc. Now, I've been working with it fine for a month now, and after a week or so hiatus of working with it, I open it now to run into the dreaded 'red nodes'. I've had it happen before, and this time around the symptoms are this:
1. it's got to be known that these red nodes are NOT FileIns or image generators.
2. as I start from the top of the tree and start viewing each node downstream, eventually the a node I double click on will be yellow, and some node upstream (that worked great when I viewed it previously) turns red.
3. Obviously it's not the color of the node in my tree that is concerning me, it's the fact that when they appear, Shake may often crash, or sometimes I get botched image processing (the image will appear obviously corrupted- like a bunch of scan lines)
4. Often this corrupt imagery occurs through a completely innocuous and stable math node, like IAdd, and both image processes upstream going in rendered perfectly when I viewed them before.
5. The problem occurs even when using 1 thread, not just the usual 8 I normally use in the renderControls
6. Generally I can associate the 'red node' appearing with the use of Macros, even though I thoroughly test my Macros in script form before making them final macros, and never place a macro inside a macro (using only Shake's built in processes and no extraneous coding other than linking variables)...
The only way I've ever been able to fix the problem before is either reverting to an older version, or rebuilding the script. Both obviously imply a lot of time lost. In this case, I have gone back to past versions and the red nodes are still showing up.
I don't know if things are getting screwed up in my nreal folder, if this has anything to do with corrupt caches, I really have nowhere to start. Has anyone dealt with this, have any insight, or has personally conquered the problem? Remember... I'm opening a script that was working flawlessly, seemingly the only thing that changed since last opening, is time.
1. it's got to be known that these red nodes are NOT FileIns or image generators.
2. as I start from the top of the tree and start viewing each node downstream, eventually the a node I double click on will be yellow, and some node upstream (that worked great when I viewed it previously) turns red.
3. Obviously it's not the color of the node in my tree that is concerning me, it's the fact that when they appear, Shake may often crash, or sometimes I get botched image processing (the image will appear obviously corrupted- like a bunch of scan lines)
4. Often this corrupt imagery occurs through a completely innocuous and stable math node, like IAdd, and both image processes upstream going in rendered perfectly when I viewed them before.
5. The problem occurs even when using 1 thread, not just the usual 8 I normally use in the renderControls
6. Generally I can associate the 'red node' appearing with the use of Macros, even though I thoroughly test my Macros in script form before making them final macros, and never place a macro inside a macro (using only Shake's built in processes and no extraneous coding other than linking variables)...
The only way I've ever been able to fix the problem before is either reverting to an older version, or rebuilding the script. Both obviously imply a lot of time lost. In this case, I have gone back to past versions and the red nodes are still showing up.
I don't know if things are getting screwed up in my nreal folder, if this has anything to do with corrupt caches, I really have nowhere to start. Has anyone dealt with this, have any insight, or has personally conquered the problem? Remember... I'm opening a script that was working flawlessly, seemingly the only thing that changed since last opening, is time.
Mac Pro Octo2.26GHz Nahalem, 8GB RAM, ATI Radeon HD 4870, Mac OS X (10.6.3), <3 Shake
