Baked lighting disappears with addressables 1.1.5

Unity Engine
1

When I attempt to load a scene in a standalone build or in Packed mode in editor, the baked lightmap vanishes:

4782965--456419--upload_2019-7-24_21-34-48.png
4782965--456419--upload_2019-7-24_21-34-48.png1515×534 426 KB

Loading in virtual mode seems to work fine:

4782965--456422--upload_2019-7-24_21-34-59.png
4782965--456422--upload_2019-7-24_21-34-59.png1511×513 464 KB

Unlike prior reported issues, all the maps in the baked list appear to be loaded okay according to the preview images. They just don’t show up in-game.

Two things that do change are Enlighten/Progressive setting and LightingDataAsset setting – however, I don’t think these would be needed during runtime…?

4782965--456428--upload_2019-7-24_21-35-41.jpg
4782965--456428--upload_2019-7-24_21-35-41.jpg1920×1040 396 KB

4782965--456425--upload_2019-7-24_21-35-30.jpg
4782965--456425--upload_2019-7-24_21-35-30.jpg1920×1040 413 KB

Each spot light is set to the same settings, using mixed mode in Enlighten with Baked GI in shadowmask lighting mode. Realtime GI is not enabled for this scene. Unity version is 2018.4.2f1 LTS with Addressables 1.1.5. Both the scene and its lightmaps have been enabled for the addressables system, with bundles packed separately per asset. I have tried with LightingData.asset both included and not included in addressables with no change.

4782965--456440--upload_2019-7-24_21-44-51.png
4782965--456440--upload_2019-7-24_21-44-51.png1515×515 99.3 KB

My loader code looks like as follows:

AssetReference levelToLoadReference = GetAddressableSceneReference(levelName);
        if (levelToLoadReference != null)
        {
            AsyncOperationHandle loadScene = Addressables.LoadSceneAsync(levelToLoadReference, LoadSceneMode.Additive);

            yield return new WaitUntil(() => loadScene.IsDone);
        } 
SceneManager.SetActiveScene(SceneManager.GetSceneByName(levelName));
2

So I think I managed to resolve this by switching to manual shader stripping for the lightmap under project settings > graphics > custom lightmap mode (copying from one of my game scenes).

2 Likes
3

You can submit the bug from Unity Editor. I think Addressables should work by default without a lot of tedious settings and hacks.

4

Your comment saved me from a few extra hours of pain! I had a strange issue where I loaded a scene in additive mode and then switched to it using SetActiveScene. The target scene had specific lighting settings that should be applied when I set it as active. But after I’ve moved this specific scene from “In Build” to addressable bundle - these lighting settings stopped working. I was pulling my hair out until I’ve switched shader stripping options to Custom and checked only the things that my scenes used manually.

Real shame that Addressables package doesn’t solve this issue automatically. I can see a large portion of users stumbling upon this at least once.

1 Like