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
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Resolution Note (fix version 2021.2):
Fixed by unknown PR in 2021.2.12f1