Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
984586
Regression
No
Significant increase in triangle and vertex count when lighting identical joined mesh models compared to separated mesh models
Steps to reproduce:
1. Open attached “LightingPerformance.zip” Unity project
2. Open “Main” scene
3. Enter Play mode
4. Enable Stats in Game view
-notice the current amount of Verts and Tris with "meshSeparated" object enabled
5. Disable “meshSeparated” and enable “meshJoined” objects in Hierarchy
-notice the current amount of Verts and Tris with "meshJoined" object enabled
Expected results:
Number of Tris and Verts stays identical or similar
Actual results:
Number of Tris and Verts increases significantly
Reproduced in: 2018.1.0b1, 2017.3.0p1, 2017.2.1p1, 2017.1.3f1, 2017.1.0a1
-------------
By design:
Unity culls per object, not per triangle. Therefore, separate objects can be culled from individual shadowmaps if they're not in the shadowmap's frustum which causes a reduced triangle count.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment