F. Sebastian (spiff) Grassia
F. Sebastian (spiff) Grassia
I agree that's a concern, @nvmkuruc , and the only way in USD-of-today to make the limited scope obvious in the data itself instead of documentation would be to require...
Hi @dgovil , `Can*()` and `Validate`methods sound great. But also, upon another read, I did not think it was possible, but in any case not desirable, to have a multiple-apply...
> One downside is that the UsdGenSchema overwrites that default when run. I wonder if maybe having it understand a default instance name would be a good addition to the...
See [Customizing Per-Class Properties](https://openusd.org/dev/api/_usd__page__generating_schemas.html#Usd_PerClassProperties) for exactly that use-case (which appears in UsdGeom schema.usda) - spolier, it's `customData[extraIncludes]`
Are there cases where it's insufficient to just put includes in **custom** section of the cpp - that's what we generally do. Unless the header actually needed types defined in...
Huh, so this is actually an "easier" problem to address than what I thought you were having. I'm kind of surprised that applying/removing a clipSet does not trigger stage-level invalidation...
Thank you, @kikaxa . So for several reasons, it's not practical for UsdStage itself to propagate invalidation through relationships and connections - even in the "forwards" direction, and here we're...
Hi @chadrik - sorry for the delay; we finally had a chance to talk this over, and we like the idea of at least your step #1 at this point....
Nothing new to add, @chadrik , `pxr_boost` is there for you to experiment with. Full disclosure we won't have time to help or get you feedback till after siggraph!
Hello! Please do not modify any generatedSchema.usda files, as it will cause some of our internal test automation to fail. I think reviewers will know to skip them. Thank you!...