Tweet
Hi, I would like to raise some issue regarding this. I also posted on tyflow forum, and Tyson advised me to contact chaos directly as you guys are doing the GPU implementation.
I need to do grass, so I set a standard scatter flow. When I output a flow to a tycache, I usually only output 1 frame for static objects. Then I use tycache feature to hold and clamp the frame output from 0 to 0 (or 1 to 1). I use this for grass that doesn't move.
Afterwards, I developed a hue randomization with vray multisub and random by renderID, so the grass doesn't look too uniform. I apply this to the grass mesh, and use tyFlow feature of getting the material from the mesh itself. So I did not apply this shader to tyFlow object, since it's already being referenced by the shape node.
I have made sure I am using the same tyFlow version on userPC and renderfarm. It is the slightly older version of 16127, but by reading the changelog of the version history, I don't think this issue is addressed yet.
The problems I encounter:
1. On some farm nodes, the cache is not loaded at all. This seems to be random behaviour, sometimes it's render node 9, sometimes 20. But if it wasn't loaded at the start of the job, within the duration of the job, that node becomes useless because it will always be missing the cache.
2. The shaders seems to be switching the randomness every now and then, so I can see flickering on the shader of the grass. It's caused by random by renderID. If I stick with Face Material ID and use Material ID operator set to random in tyFlow, I could work around this issue.
It's worthy of note that problem 1 doesn't exist in vray CPU, so I raised this in vray GPU section. Our IT have sneaking suspicion that it might be because the network drive is too slow and it doesn't load the cache. But it is not certain because on really light scenes with only 100-200mb 1 frame cache, this problem still exists.
I hope the problem is reproducible on your end. Let me know if you need more information.
Comment