Search Issue Tracker
Fixed in 2018.3
Votes
11
Found in
5.6.0b1
Issue ID
864476
Regression
No
[DrawMeshInstanceIndirect] Wrong computeBuffer being passsed to consecutive DrawMesh calls
Steps to reproduce:
1. Open the attached project (CharacterInstancing (u5.6.0b1).zip)
2. Open the Assets/AnimationMatrixGpu/AniMatrix_InstanceIndirectAppend.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)
4. Use mouse to move a camera in the Scene view, so you can look around and try to match the position/rotation as shown in the screenshot
5. Observe, the shadows appear in the wrong position
Expected result: The shadows should appear in the right position
Actual result: The shadows appear in the wrong position
Note:
Bug relates to features introduced in 5.6.0
Computations are made in the custom shader (AniMatrixM44Culling)
Reproduced with: 5.6.0a1, 5.6.0a6, 5.6.0b1, 5.6.0b3
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
- Japanese diacritic symbols are missing from the build executable file when building the project
- [Hub] Tutorial Project summaries advise to set preferred Editor to 2019.1 when Hub 2.x does not have preferred Editor anymore
- Tilemap Collider 2D exists when tiles are being deleted
- Using Assert.Inconclusive in editmode stops the running test
- Overriding OnInspectorGUI without EditorGUILayout GetControlRect results in EditorGUI PropertyField invisible/clipped/collapsed
akkip6526
Jun 01, 2019 04:59
There are more user are connect the more time and you will connect the right option views are there you will enjoy the more time and you are connect the some time ago.http://fileexplorerwindows.com such great option and you will enjoy the more user are apply the same time.
kaffiene
Aug 06, 2018 01:15
When is this getting patched? I still have this in 5.6.3
Bamfax
Jun 11, 2018 15:39
Also seeing this in 2018.2.0b6 using a surface shader. Opened another Bug Report on it, having forgotten that it was already documented on the DMII thread. Thanks a lot Tengel!!
Xira
Dec 02, 2017 11:36
still seeing this even in 2017.3.0b6
tengel
Mar 16, 2017 17:08
Found a temporary workaround. Described here https://forum.unity3d.com/threads/drawmeshinstancedindirect-example-comments-and-questions.446080/
tengel
Mar 16, 2017 15:25
Same here on b11.
When having more than one DrawMeshInstanceIndirect call, only one of them renders shadows.
afrasson
Mar 16, 2017 14:38
Still present on 5.6.0b11.