Search Issue Tracker

By Design

Votes

0

Found in

2022.3.16f1

2023.2.4f1

Issue ID

UUM-59106

Regression

No

_MAIN_LIGHT_SHADOWS_CASCADE keyword does not appear in the Frame Debugger when Shadow Cascade Count is 2 or higher and when using it as an Asset Bundle

--

-

Steps to reproduce:
1. Open the attached user project "TestShadow.zip"
2. Open the "Assets/Scenes/SampleScene.unity" scene
3. Addressables Groups Tab -> Play Mode Script -> Use Existing Build (Windows)
4. Enter Play Mode -> Open the Frame Debugger -> navigate to "DrawOpaqueObjects/RenderLoop.DrawSRPBatcher/SRP Batch"
5. Observe the Keywords

Expected results: _MAIN_LIGHT_SHADOWS_CASCADE keyword does appear in the Frame Debugger
Actual Results: _MAIN_LIGHT_SHADOWS_CASCADE keyword does not appear in the Frame Debugger 

Reproducible with: 2022.3.16f1, 2023.2.4f1
Could not test: on 2021.3.33f1 and 2023.3.0a18 due to downgrade errors relating to scripts and Frame Debugger no longer showing DrawOpqueObjects

Testing Environment: Windows 11
Not reproducible on: No other environment tested

Note:
-As per notes in the Zendesk ticket, the issue resolves if the Library Folder is cleared and the project reimported

  1. Resolution Note:

    It seems like this issue happens when global settings are updated after populating Addressables AssetBundles. When assets are put into asset bundles, their materials and shaders are included. If those shaders do not include the keyword before being packed, the change of global settings like updating the number of shadow cascades won't then update those keywords.

    The fix I found that works is:
    1. Removing the relevant assets in the Addressables Groups
    2. Reimporting them
    3. Readding them to the Groups and rebuilding.

    Please let let us know if this fix does not work for you.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.