explicit initialization > relying on lifecycle

[laurentopia]

this is better because if we reuse receiver for something that bypasses lifecycle of physics trigger then this isn't initialized

[laurentopia]

it's in BakeryVolumeReceiver

[guycalledfrank]

I kept BakeryVolumeReceiver simple so it's easy to understand and modify. Not sure if I understood what problem it solves. Awake still does the same thing, but you additionally execute it in SetPropertyBlock in case it was called before Awake? In this case we can probably just check for renderers == null, e.g.:

    public void SetPropertyBlock(MaterialPropertyBlock mb)
    {
        if (renderers == null) renderers = GetComponentsInChildren<Renderer>() as Renderer[];
        for(int i=0; i<renderers.Length; i++)
        {
            renderers[i].SetPropertyBlock(mb);
        }
        current = mb;
    }

No need to apply empty property blocks before applying actual property blocks.

[laurentopia]

ok and test renderers in awake in case SetPropertyBlock was called before it // Cache renderers affected by volumes void Awake() { if (renderers==null) renderers = GetComponentsInChildren<Renderer>(); if (forceUsage) { // HDRP can sometimes (?) fail to use globally set volumes when SRP batching is enabled, so disable it for this object. SetPropertyBlock(new MaterialPropertyBlock()); } }

[guycalledfrank]

Added: https://github.com/guycalledfrank/bakery-csharp/commit/b2499932bd39d60e40112676017e459ad4029b1f