ROP Composite Output TOP unexpected result in-process?

   816   0   1
User Avatar
Member
22 posts
Joined: June 2013
Offline
Hi.

I was trying to automate some texture shrinking using a TOPnet. Used a python script to find textures in a material library, a wedge to create tasks and attributes like original path, filename, etc. for each file, and then I split everything into 2 ROP Comp outs. One would handle the half res, the other would handle the quarter res. Inside, just a file node, nothing fancy.

Using Out-of-Process Cook Type does exactly what it's supposed to do, but switching to In-Process makes every file the same (looks like the pdg attribute from inside the copnet wouldn't update in-between wedges). Is it normal? Am I missing something?

Thanks.
  • Quick Links