Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0b6
Issue ID
912332
Regression
No
[StaticBatching] Unneeded individual shadow batching calls are issued when certain material is selected in Project folder
Steps to repro:
1. Open attached project and 't1' scene;
2. Open Frame Debugger (Window -> Frame Debugger);
3. Open Profiler (Window -> Profiler);
4. Enter Play mode;
5. In Frame Debugger window click 'Enable' button;
6. In Project folder select 'New Material' material;
7. Observe draw calls is Profiler and Shadows.RenderJobDir calls in Profiler.
Expected result:
There are only Static batch calls fo Cube shadows (see attached expected.png screenshot).
Actual result:
Unneeded individual draw calls for Cube mesh are shown apart from Static Batch shadow calls. See attached video and actual.png screenshot.
Workaround is to select 'New Material 2' in Project folder and observe that only static batch calls are now issued.
Notes:
- Reproducible in 2017.1.0b6, 5.6.0p1, 5.5.2p1;
- Reproducible on OSX 10.12.3 and Windows 10;
- Reproducible only in Editor; not reproducible in Standalone Player.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment