F. Sebastian (spiff) Grassia

There should be no way to misuse the composition arcs or instancing that does not produce error output (eg. introducing a reference cycle), so this surely sounds like a bug...

Hi @chongxian , yes the CMakefile needs to be configured a little differently when building against an established USD installation. I don’t have the proper changes at my fingertips (maybe...

Just wanted to provide some visibility on our internal deliberations on this one, unsatisfying though they are. We'd rather not address the "what kind of layer is it" question in...

@nvmkuruc , the biggest challenge with multiple registries aside from the extra management/API complexity is that it is easily susceptible to the "two layer problem" where we could have the...

Hi @moshev , we don't think we can accept this PR. Nothing in OpenUSD currently deletes the singleton, and it would not be safe, generally, to do so, in our...

It would definitely violate the assumptions of some of the paths through that code to allow writing to a package-layer. With this and previous Issues you've been knocking at the...

So the exception here is a `std::bad_alloc` exception that USD is just not catching, by design, right now. We have recently been reconsidering our use of and policy for exceptions,...

We've recently been thinking about this again, and while we think that there are potentially many legit files that could also throw that exception (e.g. on resource-limited platforms), we do...

``` gprim = stage.GetPrimAtPath("/world/workshop/drawer/drawer") mbAPI = UsdShade.MaterialBindingAPI(gprim) material = mbAPI.ComputeBoundMaterial()[0] if material: print(material.GetPrim().GetPath()) ``` See the referenced methods for options, please.

Hi @dgovil , we don't recall the reason for this... closest recollection is that we had some possibly confusion about the need/identity for NodeGraphs for mtlx Materials. In any case,...