Search Issue Tracker
Fixed in 2022.3.43f1
Fixed in 2022.3.X, 6000.0.X, future release
Votes
1
Found in
2022.3.38f1
6000.0.11f1
6000.1.0a7
Issue ID
UUM-75697
Regression
No
NullReferenceException is thrown and value does not change when changing the Shader Variant Limit value after exiting the Play mode
Reproduction steps:
1. Open the attached “ShaderVariantLimit.zip” project
2. Enter the Play mode
3. Exit the Play mode
4. Edit the value of “Shader Variant Limit” to any other value (Edit > Project Settings > ShaderGraph)
Expected result: The value changes
Actual result: “NullReferenceException: Object reference not set to an instance of an object” is thrown and the value reverts to the previous entered value
Reproducible with: 2022.3.38f1, 6000.0.11f1
Couldn’t test with: 2021.3.40f1 (Shader Variant Limit option in the Project Settings is not present)
Reproducible on: macOS 14.5 (M3 Max) (User reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- Does not seem to reproduce if the Play mode has not been entered before editing the value
- Sometimes does not reproduce after restarting the Editor and editing the value right away
- Reproducible on a new project
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Postponing; will batch forward port in the future.