Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2021.2.8f1
Issue ID
1396220
Regression
Yes
Shader keyword PROCEDURAL_INSTANCING_ON does not work in builds
Reproduction steps:
1. Open the attached project
2. Open and Play the scene 'SampleScene'
3. Notice that the shader works and there are multiple cubes in the scene
4. Exit Play mode
5. Build the project
Expected result: The build has the same result as Play mode in the Editor
Actual result: In the build there is only one cube, indicating that the shader is not working
Reproducible with: 2021.2.8f1, 2021.2.11f1
Not reproducible with: 2020.3.33f1, 2021.2.7f1, 2021.2.12f1, 2021.3.0f1, 2022.2.0a10
Couldn't test with: 2019.4.37f1 (Building issues)
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
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
Resolution Note (fix version 2021.2):
Fixed by unknown PR in 2021.2.12f1