検索 - User list
Full Version: usd outside of lops
Root » Solaris and Karma » usd outside of lops
danwnewlands
Hey,

End goal here is to output an alembic to be used in another package but right now I'm just trying to get my geometry out of lops and into sops so I can export.

In lops everything seems fine but once the usd is exported out and either imported into sops using 'usdimport' or 'lopimport' I end up with what seems to be the correct layout but showing all geometry variations at once? If the exported usd is loaded into a sublayer then it does load correctly also?

Any idea what would cause this?

In /stage

In /obj


Cheers
mtucker
danwnewlands
showing all geometry variations at once

How are these geometry "variations" expressed in USD such that only one is visible at a time? If you're using visibility, that might be the issue, since I think by default LOP Import will import "invisible" primitives too.
danwnewlands
mtucker
danwnewlands
showing all geometry variations at once

How are these geometry "variations" expressed in USD such that only one is visible at a time? If you're using visibility, that might be the issue, since I think by default LOP Import will import "invisible" primitives too.

Yea, I'm using the addvariant node, it seems when I inspect the node it is setting visibility to "invisible"

For instance:

variantSet "model" = {
                "Street_Curbs_1" {
                    over "Asset_cement_curbs_S_sepxW_00_LOD0"
                    {
                        token visibility = "invisible"
                    }

                    over "Asset_cement_curbs_S_sepxW_00_LOD0_proxy"
                    {
                        token visibility = "invisible"
                    }

                    over "Material"
                    {
                        token visibility = "invisible"
                    }

                }
                "Street_Curbs_2" {
                    over "Asset_cement_curbs_S_sepxW_01_LOD0"
                    {
                        token visibility = "invisible"
                    }

                    over "Asset_cement_curbs_S_sepxW_01_LOD0_proxy"
                    {
                        token visibility = "invisible"
                    }

                    over "Material"
                    {
                        token visibility = "invisible"
                    }

Will have a read on the docs now so I may find the answer but what is the alternative here?
mtucker
You can have the LOP Import only import visible prims by using a VEXpression in your primitive pattern. Something like "{ usd_isvisible(0, @primpath) }".
danwnewlands
mtucker
You can have the LOP Import only import visible prims by using a VEXpression in your primitive pattern. Something like "{ usd_isvisible(0, @primpath) }".

I cant seem to get this to work, it seems to be doing the correct thing in the geometry spreadsheet but not updating the viewer?


... I have found that setting the 'Traversal' to 'Custom Traversal', in the lopimport node, opens an advanced tab, in there I can set 'Is Visible' to false and in doing that it removes the objects that I do want. I cant seem to do the inverse but I'm getting closer it seems...

Thanks for the help so far
danwnewlands
mtucker
You can have the LOP Import only import visible prims by using a VEXpression in your primitive pattern. Something like "{ usd_isvisible(0, @primpath) }".

Hey! Just coming back to this, so it was due to the prune node I was using in a addvariant loop, the prune node by default is set to hide visibility. Simply switching those prunes to deactivate instead fixed the issue!

Thanks for the help
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Powered by DjangoBB