Eilef Sandnæs

If you don't have a renderfarm and special need for effects in your sequences, Redshift should make your life easier.

Found a solution.

I had to write the filepath into a text field that's connected to the texture node inside the Houdini engine, and not a “File - image” that Maya didn't like. Maya went mad when there is a “%” inside a image link.

dlee
Texture VOP is using UV coordinate as face S/T when UV attribute exists, even for PTex. You can delete the UV attribute to get around the issue, or (if you need to keep the UV attribute for other uses), you can wire shading global's S/T into Texture VOP's UV input (using Float to Vector VOP, set S as first component and set T as second component).

Thank you for the help again!

Your fix to rename the uv attribute worked like a charm in Houdini, but when i use the same Digital Asset in Maya with Houdini Engine the artifact appear again

It happens in Maya when importing geo straight with a objectMerge node.

I also tried to build a rop_alembic inside the tool that export out an Alembic file. Then the file is imported again, with a wrangle step that renames uv attribute, last step is a baketexture that will make the PTEX.

The PTEX bake only works if i do the alembic export step in Houdini, and import it inside Maya and press bake texture.

But if i do all the steps inside Maya with the Digital Asset the PTEX file wont work, just get a constant color on each face like earlier.

so now i'm stuck again


Do you have some wisdom to share again? or is it some kind of limitation with how Maya sends geo to Houdini that makes this hard to do?