Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.8.6
Issue ID
1153579
Regression
No
Material loaded from packed content fails to render with DrawMeshInstanced API when using "Strip All" instancing variant setting
How to reproduce:
1. Open the attached project ("case_1153579-addressables-build-issue")
2. Open the "A" scene
3. Build Player Content in the Adressables window
4. Enter the play mode
5. Notice that 4 new cubes are rendered
6. Exit play mode and open the "B" scene
7. Enter the play mode
Expected results: 4 new cubes are rendered, same as in "A" scene
Actual results: no new cubes are rendered
Reproducible with: 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Couldn't test with 2017.4, as it does not support Addressables package
Reproducible with package versions: 0.8.4, 0.8.6
Notes:
1. This issue also reproduces on builds
2. Changing the shader instancing variant stripping from "Strip All" to "Strip Unused" fixes the issue
3. Using "DrawMesh" instead of "DrawMeshInstanced" also fixes the issue.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
this is also being discussed on the forums with this user. I replied there:
https://forum.unity.com/threads/0-8-4-case-1153579-material-loaded-from-build-fails-to-render-with-drawmeshinstanced.676291/#post-4600078