There’s an interesting bug in the cache TOP that seems to present when being fed by a render TOP - so in that case it might be a pull based bug in the render TOP?
The test conditions are as follows:
A series of base COMPs contain a render network, a script is used to load the cache top with their outputs. Currently only the output form the first in the series is cached.
Attached is a test case.
First set all base COMPs Output par to Text. Run the script in text5. The result should be:
Repeating this same process, but change the Ouptput par to Render. The result should be:
One other note here is that here’s a par execute DAT that’s also in this network. Changing top paths manually on the select TOP correctly prints the changed par - when run from the script, there’s no output - making it seem like the par hasn’t changed. That part really took me for a loop.
Here’s a tox:
base_cacheBug.tox (3.3 KB)