Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.2f2
Issue ID
860925
Regression
No
[Graphics] DrawMeshInstanced appears to renders empty instances in some cases
Steps to reproduce:
1. Open the attached project (CharacterInstancing (u5.6.0a2).zip)
2. Open the Assets/AnimationMatrixExtraction/AnimationMatrixAssetTestScene.unity scene
3. Run the scene (You should see 10,000 Lerpz characters rendering, arranged as a grid ( 100x100 ) on a plane. Each instance is unique, with its own color and frame animation. Due to size its hard to see any details, but switching to scene view fixes that)
4. Open the Frame Debugger
5. Start stepping through the drawMeshInstance calls
6. Upon reaching the 5th and 6th drawMeshInstance calls you should not see any change in the frame Debugger view
Expected result: DrawMeshInstanced should not render empty instances
Actual result: DrawMeshInstanced appears to renders empty instances
Note:
Bug relates to features introduced in 5.6.0
If you want to play with the number of instances rendered per DrawMeshInstance call, select the 'TestFramework Combine' gameObject and check the inspector, 'NumInstancesPerGroup' be set to 1000 (with 1000, 1020, 600, 400, 200, same behavior)
Reproduced with: 5.6.0a1, 5.6.0a6, 5.6.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment