[Bf-committers] Proxy Removal for Blender 3.0

Hadrien Brissaud hadriscus at gmail.com
Wed Sep 22 19:20:32 CEST 2021


Alright, good to see this is known already. For clarity's sake, by
"overriding material" I didn't mean changing individual node properties and
connections and such, but linking a completely different material on the
object (usually a copy of the linked one). I didn't actually expect
overrides to the node tree topology/properties to be supported, that sounds
awfully complex. It is probably simpler to approach "material variations on
linked assets" through drivers between the object's custom properties and
its material, which so far doesn't work either -this is something that I
tried during production and eventually resorted to local materials because
those drivers would fail upon linking the character.

Thanks for your reply, have a good evening

Hadrien


On Wed, 22 Sept 2021 at 10:43, Bastien Montagne via Bf-committers <
bf-committers at blender.org> wrote:

> Hi Hadrien,
>
> Thanks for the feedback. Yes overrides of materials are still very
> unreliable, this is due to how materials are weirdly related to both
> Object and ObData IDs... not to mention that there is currently almost
> nothing overridable in materials anyway, so you would need to rely on
> tricks (drivers and custom properties) to get some properties editable etc.
>
> Time was lacking to address this issue for 3.0, it is a known TODO for
> the near future, together with some other annoying limitations.
>
> All development on liboverrides happens in master currently, no branch
> to try out.
>
> Cheers,
> Bastien
>
> On 9/21/21 7:15 PM, Hadrien Brissaud wrote:
> > Hi Bastien,
> >
> > as a user I am generally happy with overrides (thanks!!), except when
> > I need to override a material. Last I tested the behaviour was rather
> > unpredictable : an override was -seemingly- created, but on file
> > reload it would revert to the linked material instead, and the
> > override button was inoperative (greyed out). I will give this a round
> > of testing with latest master tonight, unless there is a specific
> > branch I should check out ? I'm a bit out of the loop.
> >
> > Cheers,
> >
> > Hadrien
> >
> > On Tue, 21 Sept 2021 at 16:32, Bastien Montagne via Bf-committers
> > <bf-committers at blender.org <mailto:bf-committers at blender.org>> wrote:
> >
> >     Hi fellow users & developers
> >
> >     Now that library overrides gained maturity and are production
> >     ready in
> >     the 'character animation' case (where they replace the old 'proxy'
> >     system), it is time to think about removing those proxies.
> >
> >     Plan is to commit in the coming days the following changes:
> >       - Add auto-conversion of proxies into library overrides on file
> >     load;
> >       - Remove the 'make proxy' operator.
> >
> >     For the time being, an option (OFF by default) will be added to the
> >     'Experimental' part of the User Preferences to skip converting
> >     existing
> >     proxies on file load. That way it is still possible to force keeping
> >     proxies if absolutely necessary, and/or for test purposes.
> >
> >     If everything goes well this option will be removed towards the
> >     end of
> >     BCon2 (end of October 2021). Full cleanup of internal proxy
> >     evaluation
> >     and management code can then happen during BCon1 of Blender 3.1.
> >
> >     Cheers,
> >     Bastien
> >
> >     _______________________________________________
> >     Bf-committers mailing list
> >     Bf-committers at blender.org <mailto:Bf-committers at blender.org>
> >     List details, subscription details or unsubscribe:
> >     https://lists.blender.org/mailman/listinfo/bf-committers
> >     <https://lists.blender.org/mailman/listinfo/bf-committers>
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> List details, subscription details or unsubscribe:
> https://lists.blender.org/mailman/listinfo/bf-committers
>


More information about the Bf-committers mailing list