Solaris - SopModify geo disappearing after polyreducing
1645 3 2-
- mmmark
- Member
- 11 posts
- Joined: June 2017
- Offline
Hello SideFX forum folks,
Looking for some workflow help in regards to Solaris + SopModify. After heavily polyreducing some geo in the SopModify context, the edited geo doesn't show up back in the Solaris main view. I figured this might be a prim "path" and/or "usdpath" attribute issue, but either old or no geo (see screenshots) shows up when I try to manually add the same "path" attrib.
Any ideas on the "right" workflow for this? I'm trying to use Solaris, not OBJ, as the primary context for Layout for this project, so any help on this type of workflow would be greatly appreciated.
Thanks,
Mark
Looking for some workflow help in regards to Solaris + SopModify. After heavily polyreducing some geo in the SopModify context, the edited geo doesn't show up back in the Solaris main view. I figured this might be a prim "path" and/or "usdpath" attribute issue, but either old or no geo (see screenshots) shows up when I try to manually add the same "path" attrib.
Any ideas on the "right" workflow for this? I'm trying to use Solaris, not OBJ, as the primary context for Layout for this project, so any help on this type of workflow would be greatly appreciated.
Thanks,
Mark
Lead Unreal Technical Artist @ Silver Spoon Animation (part of AE.Live) // portfolio: realtimemark.fun // artstation: @mmmark
-
- mmmark
- Member
- 11 posts
- Joined: June 2017
- Offline
Attached is a trimmed example file of the issue im having. Toggle the Switch to see both "either old or no geo shows up when I try to manually add the same "path" attrib" issues.
Lead Unreal Technical Artist @ Silver Spoon Animation (part of AE.Live) // portfolio: realtimemark.fun // artstation: @mmmark
-
- cwhite
- Staff
- 745 posts
- Joined: Oct. 2012
- Offline
In the scene graph tree there is a /sopmodify3/Mesh0 prim overlaid, which means that you're not overlaying the modifications over the original prims and the name / path attribute is being lost
I'm guessing that's happening from the remesh, since the input geometry has a path attribute that disappears after the file cache?
In the sopmodify that is updating the path attribute, there are still some prims that have an empty path if you look in the geometry spreadsheet
I'm guessing that's happening from the remesh, since the input geometry has a path attribute that disappears after the file cache?
In the sopmodify that is updating the path attribute, there are still some prims that have an empty path if you look in the geometry spreadsheet
-
- mmmark
- Member
- 11 posts
- Joined: June 2017
- Offline
Thanks for the reply cwhite. I took another look at the Geometry Spreadsheet and manually copy+pasted both the name + path attributes (not just "path") from the geometry before the polyreduce. The "geo disappearing outside of SopModify context" issue still persists though...
A very helpful person on the ThinkProcedural Discord server (solaris_stage_lops) ended up solving this. Turns out you can simply CopyAttribute path + usdxform, with the latter attribute fixing the "geo disappearing" issue.![](/static/djangobb_forum/img/smilies/smile.png)
See the attached updated zip for a working sample file.
A very helpful person on the ThinkProcedural Discord server (solaris_stage_lops) ended up solving this. Turns out you can simply CopyAttribute path + usdxform, with the latter attribute fixing the "geo disappearing" issue.
![](/static/djangobb_forum/img/smilies/smile.png)
See the attached updated zip for a working sample file.
Edited by mmmark - Feb. 8, 2023 21:44:57
Lead Unreal Technical Artist @ Silver Spoon Animation (part of AE.Live) // portfolio: realtimemark.fun // artstation: @mmmark
-
- Quick Links