Cdfor instance. Is it by design or a bug?Full Version: Baker's UV Boundary Filling and custom attributes
I've noticed that Enable UV Boundary Filling has no effect on baked Custom Attributes, like
Hi,
This definitely sounds like a bug, though I'm struggling to recreate this case. Would you mind attaching a .hip file or providing some more information about your setup please?
Can you also please provide the version number of Houdini you're running into this problem on?
Here is my simple test case:
The only type of attribute which does not receive UV Boundary Filling is ID Layers/Int Attributes.
Many thanks!
This definitely sounds like a bug, though I'm struggling to recreate this case. Would you mind attaching a .hip file or providing some more information about your setup please?
Can you also please provide the version number of Houdini you're running into this problem on?
Here is my simple test case:
The only type of attribute which does not receive UV Boundary Filling is ID Layers/Int Attributes.
Many thanks!
Hello Alex, thanks for your reply.
I had this problem in H21.0.368 (production build), but I just checked and I don't see it anymore in 22.0.406 daily build. That is, if I drop a fresh instance of Bake Geometry Textures COP (Cop/bakegeometrytextures::2.0), because the old instance of this operator, which I have in my scene, still fails to compute UV boundary filling for custom attributes - at least for Cd. So, I believe you guys have already fixed it.
I had this problem in H21.0.368 (production build), but I just checked and I don't see it anymore in 22.0.406 daily build. That is, if I drop a fresh instance of Bake Geometry Textures COP (Cop/bakegeometrytextures::2.0), because the old instance of this operator, which I have in my scene, still fails to compute UV boundary filling for custom attributes - at least for Cd. So, I believe you guys have already fixed it.