Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0f3
Issue ID
967808
Regression
No
Camera.SetReplacementShader renders object one at a time instead of instancing them on a Standalone build
Steps to reproduce:
1. Download and open the attached project
2. Open the profiler
3. Enter Playmode
4. Observe draw calls(5)
5. Build development build for standalone
6. Run the build
7. Observe draw calls in the profiler again
Expected result: draw calls are similair when accounting for watermark
Actual result: draw calls are significantly different as the replacement shader is not properly instanced
Reproduced on 5.5.4p4 , 5.6.4p1, 2017.1.2p3, 2017.2.0p1, 2017.3.0b9, 2018.1.0a3
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
By-design. Drawing with replacement shader will not have batching / instancing.