Hi
I am creating a rest attribute on a usd mesh using a SOP modify to make textures stick and for rendering Pref AOV's (the bind pose/T pose of the character is at frames -10 which is why the SOP modify uses that frame). If I dive inside the SOP modify the geometry spreadsheet does not show any data but I can see the rest attribute has been created by looking at the node info within the SOP modify. So I thought the rest attribute may be visible within the Solaris scene graph details, but I cannot see it. Does anyone know where I should be looking to see rest attribute when I am back in the LOPs context?
The entire reason I want to see where the attribute geos is I want to make an HDA within Maya to export animated caches as USD with the rest attribute embedded into it. So I need to check where the rest attribute is going.
Best Mark (H 18.5.532)
link to file
https://drive.google.com/drive/folders/1LsqYGtrDrgDLqQK6zsB8IxE-jAUCLOie?usp=sharing [drive.google.com]
How to see attributes in geo in Solaris (rest)
3255 5 2- Mark Wallman
- Member
- 624 posts
- Joined: Aug. 2013
- Offline
- robp_sidefx
- Staff
- 446 posts
- Joined: June 2020
- Offline
Hi Mark,
You can see in your earlier screenshot that the cache2 node isn't specifying any output prims, so the prim pattern you're using in sopmodify_add_rest (`lopparentprims(lopinputprims('.', 0))`) isn't matching anything.
If you either explicitly specify the path(s) on the sopmodify_add_rest node or disable-and-reenable the cache2 node (which then sets output prims - as you can see in the screenshot I'm attaching), you should see the primvar.
I'm going to investigate why the Cache LOP is behaving this way. I *expect* the resolution will be that the Cache LOP will be changed to *never* set output prims.
- Rob
You can see in your earlier screenshot that the cache2 node isn't specifying any output prims, so the prim pattern you're using in sopmodify_add_rest (`lopparentprims(lopinputprims('.', 0))`) isn't matching anything.
If you either explicitly specify the path(s) on the sopmodify_add_rest node or disable-and-reenable the cache2 node (which then sets output prims - as you can see in the screenshot I'm attaching), you should see the primvar.
I'm going to investigate why the Cache LOP is behaving this way. I *expect* the resolution will be that the Cache LOP will be changed to *never* set output prims.
- Rob
Edited by robp_sidefx - May 1, 2021 13:20:51
- jsmack
- Member
- 7658 posts
- Joined: Sept. 2011
- Online
- Mark Wallman
- Member
- 624 posts
- Joined: Aug. 2013
- Offline
- Mark Wallman
- Member
- 624 posts
- Joined: Aug. 2013
- Offline
- robp_sidefx
- Staff
- 446 posts
- Joined: June 2020
- Offline
-
- Quick Links