Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
4
Found in
2020.3
2021.1
2021.2
2021.2.0b3
2022.1
Issue ID
1349952
Regression
No
Instances drawn with DrawMeshInstanced flicker when the buffer changes order
How to reproduce:
1. Open the user's attached project and Scene scene
2. Enter the Play mode and observe squares
Expected result: squares do not flicker
Actual result: squares flicker
Reproducible with: 2020.3.15f1, 2021.1.16f1, 2021.2.0b4, 2022.1.0a4
Could not test with: 2019.4 (could not downgrade)
Notes:
1. With 2021.2, 2022.1 - drawn instances do not flicker if the amount of instances is less than 455 (the bigger amount of instances - the more it flickers)
2. With 2020.3, 2021.1 - drawn instances flicker with any amount of instances
Comments (2)
-
chadfranklin47
Apr 09, 2024 08:49
I'm seeing similar behavior in Unity 2022.3.23LTS with Graphics.RenderMeshIndirect()... Can we please get an update?
-
DarkSapra
Aug 07, 2023 22:16
Do we have any updates regarding this bug?
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (2022.2.X):
Fix requires a lot of work and should be tracked as a feature. Postponing until we do feature planning for the next Unity release