Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Changing Uv Sets
49 views
Skip to first unread message
Gary Yuen
Jul 8, 2024, 7:45:52 PM7/8/24
to gaffer-dev
Hi Gaffer Dev,
I'm having trouble figuring out how to switch uv sets for shader assignments. I have tried entering the UV set name into the Uvset field within the aiImage node. I also tried using the uvTransform node's Uvset field as well but neither works. When using the UV inspector and entering the UV set name, I'm not able to see the uv set. I've tested the geometry's alembic file in maya and the UV set does exist. Are there special flags that need to be typed in addition to the uv set name?
Thank you
Thank you
Murray Stevenson
Jul 8, 2024, 8:24:51 PM7/8/24
to gaffe...@googlegroups.com
Hi Gary,
You shouldn't require any additional flags to specify a UV set on Arnold shaders, but if you're not seeing the UVs in the UV inspector then it's possible that the data isn't being loaded or its name isn't what you're expecting.
The first place I'd suggest you look is the object section of the Scene Inspector. If you select a location in your model and check below the "Primitive Variables" heading it should list your additional UV set, if not then the data isn't being read from the Alembic for some reason and we may need a simple example file to help figure out why (a cube with an additional UV set named and exported the same way as your model would do) - or you may have more luck exporting to USD rather than Alembic.
To demonstrate how things should be working, I've attached an example script modifying the GafferBot model with an additional "uv2" UV set created via a MapProjection node projecting UVs from a camera, and then texturing emission with those UVs by entering "uv2" into the aiImage uvset parameter.
Cheers,
Murray
You shouldn't require any additional flags to specify a UV set on Arnold shaders, but if you're not seeing the UVs in the UV inspector then it's possible that the data isn't being loaded or its name isn't what you're expecting.
The first place I'd suggest you look is the object section of the Scene Inspector. If you select a location in your model and check below the "Primitive Variables" heading it should list your additional UV set, if not then the data isn't being read from the Alembic for some reason and we may need a simple example file to help figure out why (a cube with an additional UV set named and exported the same way as your model would do) - or you may have more luck exporting to USD rather than Alembic.
To demonstrate how things should be working, I've attached an example script modifying the GafferBot model with an additional "uv2" UV set created via a MapProjection node projecting UVs from a camera, and then texturing emission with those UVs by entering "uv2" into the aiImage uvset parameter.
Cheers,
Murray
--
You received this message because you are subscribed to the Google Groups "gaffer-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gaffer-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gaffer-dev/b6de2ac9-f2f3-4022-8b00-eb373e41cca7n%40googlegroups.com.
Gary Yuen
Jul 9, 2024, 1:33:17 PM7/9/24
to gaffer-dev
Thank you, Murray!
Your information was very helpful. Under the scene inspector, I was able to locate my second UV set. It seems that the naming of the UV set did not transfer from Maya to Gaffer. It shows up as "st1" rather than it's maya name "Opacity". This is good to know moving forward. Thanks again for the information and example scene!
Your information was very helpful. Under the scene inspector, I was able to locate my second UV set. It seems that the naming of the UV set did not transfer from Maya to Gaffer. It shows up as "st1" rather than it's maya name "Opacity". This is good to know moving forward. Thanks again for the information and example scene!
Reply all
Reply to author
Forward
0 new messages