Started seeing this in my scene files after upgrading to 19.5:
"The layer imported from SOPs has no save path set. The SOP node's layer will be output to a file path generated from its Houdini path."
ELI5; for someone with infantile USD fluency trying desperately to understand Solaris, what does this mean and how is it properly solved?
SopImport Save Path warning
10917 8 2-
- dhemberg
- Member
- 207 posts
- Joined: Nov. 2015
- Offline
-
- mestela
- Member
- 1853 posts
- Joined: May 2006
- Online
I have some sketchy notes here that try and stay jargon free (well, jargon free-ish):
https://www.tokeru.com/cgwiki/index.php?title=UsdGuide11 [www.tokeru.com]
https://www.tokeru.com/cgwiki/index.php?title=UsdGuide11 [www.tokeru.com]
-
- dhemberg
- Member
- 207 posts
- Joined: Nov. 2015
- Offline
You are excellent sir.
Followup question: my Solaris setup begins with a SopImport node: I have several SopNets in Solaris, each of which make some geo. Then, I use SopImports to assemble them all.
When I leave the "Layer Save Path" param empty on the sop imports, I see warnings mentioned above. My understanding of your docs is that I can fix this warning just by providing something useful in that parameter, so I turn it on and do something like
But now I get a new, even less helpful warning:
What's THIS one mean?
Interestingly, if I just use $HIP/thing.usd, I get no complaints. But that doesn't help me understand what's going on...
Followup question: my Solaris setup begins with a SopImport node: I have several SopNets in Solaris, each of which make some geo. Then, I use SopImports to assemble them all.
When I leave the "Layer Save Path" param empty on the sop imports, I see warnings mentioned above. My understanding of your docs is that I can fix this warning just by providing something useful in that parameter, so I turn it on and do something like
"$HIP/../tmp/thing.usd"
But now I get a new, even less helpful warning:
Could not load sublayer @op:/stage/sopnet/OUT.sop:SDF_FORMAT_ARGS:authormaterialpath=0&globalauthortimesamples=0&kindschema=nestedgroup&pathprefix=/world/geo/gallery/interior&savepath=H:/houdini/tmp/thing.usd&savepathtimedep=0&scalarconstantattribs=albedo_texture roughness_texture bump_texture displacement_texture&seed=588.616&t=0@ of layer @anon:00000011792D0200:LOP:rootlayer@; skipping. (Recomposing stage on stage @anon:00000011792D0200:LOP:rootlayer@ <00000011EE707C80>)
What's THIS one mean?
Interestingly, if I just use $HIP/thing.usd, I get no complaints. But that doesn't help me understand what's going on...
Edited by dhemberg - Aug. 8, 2022 09:40:46
-
- jsmack
- Member
- 8177 posts
- Joined: Sept. 2011
- Offline
dhemberg
You are excellent sir.
Followup question: my Solaris setup begins with a SopImport node: I have several SopNets in Solaris, each of which make some geo. Then, I use SopImports to assemble them all.
When I leave the "Layer Save Path" param empty on the sop imports, I see warnings mentioned above. My understanding of your docs is that I can fix this warning just by providing something useful in that parameter, so I turn it on and do something like"$HIP/../tmp/thing.usd"
But now I get a new, even less helpful warning:Could not load sublayer @op:/stage/sopnet/OUT.sop:SDF_FORMAT_ARGS:authormaterialpath=0&globalauthortimesamples=0&kindschema=nestedgroup&pathprefix=/world/geo/gallery/interior&savepath=H:/houdini/tmp/thing.usd&savepathtimedep=0&scalarconstantattribs=albedo_texture roughness_texture bump_texture displacement_texture&seed=588.616&t=0@ of layer @anon:00000011792D0200:LOP:rootlayer@; skipping. (Recomposing stage on stage @anon:00000011792D0200:LOP:rootlayer@ <00000011EE707C80>)
What's THIS one mean?
Interestingly, if I just use $HIP/thing.usd, I get no complaints. But that doesn't help me understand what's going on...
Do you want the sop layers to actually be saved to different files, or just used to build a larger single file? If you don't want individual files, then just check the box to copy onto the stage.
-
- dhemberg
- Member
- 207 posts
- Joined: Nov. 2015
- Offline
It's not my goal to save anything; just trying to muddle my way through building a renderable scene in Solaris. As I mentioned above, this file offered no warnings or errors in H19, but suddenly lots of errors in 19.5, and it wasn't clear to me why.
Ticking on "copy contents into editable layer" seems to remove the warnings.
Ticking on "copy contents into editable layer" seems to remove the warnings.
-
- jsmack
- Member
- 8177 posts
- Joined: Sept. 2011
- Offline
dhemberg
Ticking on "copy contents into editable layer" seems to remove the warnings.
The no save path set warning you can ignore if you don't plan on saving out a usd scene for consumption by others. I'm not sure why you are getting layer not found error when using a relative path for a save path. Try using an absolute path instead.
-
- vopaholic
- Member
- 11 posts
- Joined: March 2018
- Offline
Yeah I get this message too when using SOP create in reference mode. Seems the problem is with using a relative path that points above hip location, like $HIP/../usd/pig.usda. If I use $HIP/usd/pig.usda it's fine.
A relative path above hip works everywhere else like in Config layer and usd rop so it would be nice to have it behave similar in sop create/import.
A relative path above hip works everywhere else like in Config layer and usd rop so it would be nice to have it behave similar in sop create/import.
-
- jsmack
- Member
- 8177 posts
- Joined: Sept. 2011
- Offline
ChristianP
Yeah I get this message too when using SOP create in reference mode. Seems the problem is with using a relative path that points above hip location, like $HIP/../usd/pig.usda. If I use $HIP/usd/pig.usda it's fine.
A relative path above hip works everywhere else like in Config layer and usd rop so it would be nice to have it behave similar in sop create/import.
Use an absolute path. Try pre-expanding a relative path to an absolute path by passing a 'unix style' relative path to the abspath() expression function.
-
- mtucker
- Staff
- 4565 posts
- Joined: July 2005
- Offline
-
- Quick Links