Milan Kolar

We use this all the time for workfiles. An artist works toward v02 of a shot, but needs to version for himself within this version so his workfiles look like...

> We have {version} now. Would the other counterpart be {minor} or {revision}? We naturally started calling them `subversion` in the studio.

It actually aligns with some feature requests we are getting outside USD. namely master versions, which is how usd is kind of designed on the base level. Clients want to...

>A user could technically deactivate the Bootstrap instances in the UI, or vice versa, deactivate the one instance they were dependent on and keep the others active. It's a bit...

I was wondering what family are you going to use for this, if any. We're kinda running into a need to create a new family that acts in a very...

> However, describing that, I must admit it's hard to find out how well this "fits" into Avalon itself since it behaves so differently from the rest precisely. I'd say...

Functionally it would all be there. But eventually artists would like to see thumbnails. Shader assignments to selected objects rather than id matching as we have it now (using colorbleed...

I'd go with option 1. no changes to loader required and very clear for user. Library silo would introduce huge amount of noise. Imagine a studio has 4-5 different asset...

@tokejepsen That's exactly what I meant in the first place and I agree with that. Functionally I thought that ideally we wouldn't copy it just yet and only add another...

Ah sorry my bad I mean Loader of course. And yes that is the key problem currently we think. If we fudge the session to make loader think it's in...