I have a textured model in Maya 2022, and it renders the textures as expected.
I exported the scene to USD with USD Preview Surface.
This appears to import into Houdini 19 Solaris via a stage/loadlayer LOP.
The imported material appears to be some kind of generic shader.
When I try to replace the material on the screen-left tank, with a MaterialX surface, or usdpreview surface, it looks like it's applying the texture per face, instead of using the UV info.
The UV metadata is clearly there, as you can see the textures on the neighboring tanks.
What am I missing?
Thanks

The usduvtexture is missing a usdprimvarreader connected to the st input for reading the texture coordinates.

Ah, I’ll give that a try. Thanks!

jsmack
The usduvtexture is missing a usdprimvarreader connected to the st input for reading the texture coordinates.

I added a usdprimvarreader node, set the Signature to Float2, VarName to st, and connected the result to st on the usduvtexture node.
Unfortunately, the texture is still not showing up.
Is there anything I need to do at the materiallibrary LOP node level to ensure the st primvar is visible to the usdprimvarreader node?
Thanks

As a diagnostic, I switched to /obj, created a geo node, dived in, and created a usdimport LOP to load the same model from maya, appended an unpackusd node, with Output Polyons selected.
In the geometry spreadsheet, I couldn't find any st or uv parameters. However, I noticed a point attribute called map1, which was a floating-point 2-dimensional array.
So I tried changing the usdprimvarreader to map1, and it worked!
For some reason, Maya 2022 appears to export a variable called "map1" instead of st or uv, in this example, when writing to USD.

Hi. Maya's own USD plugin is a bit wonkey. To export from Maya I tend to use this with no issues: https://j-cube.jp/solutions/multiverse/ [j-cube.jp]

You could also try updating the Autodesks latest build of the USD exporter: https://github.com/Autodesk/maya-usd/releases/ [github.com]

Best

Mark Wallman
Hi. Maya's own USD plugin is a bit wonkey. To export from Maya I tend to use this with no issues: https://j-cube.jp/solutions/multiverse/ [j-cube.jp]

You could also try updating the Autodesks latest build of the USD exporter: https://github.com/Autodesk/maya-usd/releases/ [github.com]

Best

Good to know. I'll give those a try.
Thanks

Unfortunately, the multiverse plugin is failing on my MacBookPro 2014 running macOS Big Sur.
See attached error logs.

I tried installing the newest version of the Autodesk USD exporter Version 0.14.0.
When I re-export the model to USD, the texture attribute is now called "uv" instead of "map1", but the uv attribute is a 3d float array instead of a Vector2.
Since the usduvtexture node is expecting a Vector2 for st, I feed the usdprimvarreader (with a signature of Float3 for "uv", into a vectofloat (3D Vector), output values 1 and 2 are then fed into a Float to Vector2, which is then fed into the "st" input of the usduvtexture.
Unfortunately, I'm no longer seeing the texture map for the screen-left spherical tank.
What am I missing this time?
Thanks

Hi.

I did flag some of these issues over in the Maya beta forum about 6 months ago but for what ever reason the Maya Dev team are not always that responsive. I actually ended up making a tool in Houdini to convert ABC files for use in Houdini, unreal, multiverse and Blender.

The USD Multiverse guys do have a slack forum where you could ask about the issues with Mac OS.

Best

Mark

syntheticperson
Since the usduvtexture node is expecting a Vector2 for st, I feed the usdprimvarreader (with a signature of Float3 for "uv", into a vectofloat (3D Vector), output values 1 and 2 are then fed into a Float to Vector2, which is then fed into the "st" input of the usduvtexture.
Unfortunately, I'm no longer seeing the texture map for the screen-left spherical tank.
What am I missing this time?

Float to vec2 and vec3 to float aren't valid nodes for usd. These are only valid in the vex context such as for mantra shaders/attribute vops.

Just plug the primvar reader right into the texture reader. It actually doesn't matter if the geo has float2 st or float3 uv. using 'uv' with float2 or float3 on the primvar reader will work either way.

Mark Wallman
Hi.

I did flag some of these issues over in the Maya beta forum about 6 months ago but for what ever reason the Maya Dev team are not always that responsive. I actually ended up making a tool in Houdini to convert ABC files for use in Houdini, unreal, multiverse and Blender.

The USD Multiverse guys do have a slack forum where you could ask about the issues with Mac OS.

Best

Mark

Hi Mark, doesn't ABC/Alembic only support geometry and cached animation? I need the materials/textures to come across.
I joined the Multiverse slack channel.
Thanks

jsmack

syntheticperson
Since the usduvtexture node is expecting a Vector2 for st, I feed the usdprimvarreader (with a signature of Float3 for "uv", into a vectofloat (3D Vector), output values 1 and 2 are then fed into a Float to Vector2, which is then fed into the "st" input of the usduvtexture.
Unfortunately, I'm no longer seeing the texture map for the screen-left spherical tank.
What am I missing this time?

Float to vec2 and vec3 to float aren't valid nodes for usd. These are only valid in the vex context such as for mantra shaders/attribute vops.

Just plug the primvar reader right into the texture reader. It actually doesn't matter if the geo has float2 st or float3 uv. using 'uv' with float2 or float3 on the primvar reader will work either way.

Hi jsmack, that worked!
Many thanks.