F. Sebastian (spiff) Grassia

There is "internal pixar" precedent in the Presto scenegraph that "config attributes" imply structural changes to a prim's definition; while we are continuing discussions on whether that mechanism will need...

That's correct, @nvmkuruc . In fact, we've stopped authoring it in Presto/menva, but don't disallow it, for old assets. And yes, it doesn't restrict uses in property names or namespaces.

We think that's quite reasonable, even given that not all platforms support env var's equally well. We'd consider a PR if you'd like to send one in with a CLA?...

Even more curiously, and contra-indicatory (is that a word?), is [this code for handling zero](https://github.com/PixarAnimationStudios/OpenUSD/blob/53d7d647d293fe1aaeb03d2186e8cdeefe09a6fd/pxr/usd/sdf/layerOffset.cpp#L55-L68) in SdfLayerOffset...

So... given that we also do not prevent zero-scales in layer offsets, what do folks think about defining the behavior like this: If the time-mapping from a layer to the...

When a zero **scale** appears in a sublayer’s layerOffset, we don’t have the flexibility to interpret as “time does not advance”, because the composed layer time-mapping will already have collapsed...

Hey @dgovil , @meshula 's suggestion would allow for more access to the existing data than what you and I were thinking (everything collapses to a single sample), but I...

Hey @dgovil - we were unable to think of a useful, meaningful need for either a layerOffset-scale of zero **or** a `timeCodesPerSecond` of zero, so we propose simplifying the whole...

Just in case it might trigger something over here, could you attach/provide the crashing callstack? --spiff On Thu, Oct 9, 2025 at 12:14 PM Dhruv Govil ***@***.***> wrote: > *dgovil*...

Just confirming that the Hydra side of ColorSpaceAPI is planned but not yet available.