Search Issue Tracker
Fixed in 2017.2.X
Votes
2
Found in
5.6.1p1
Issue ID
917188
Regression
Yes
Assertion failed: RendererUpdateManager when calling CommandBuffer.DrawRenderer on disabled mesh renderer
Steps to reproduce:
1. Open user attached project
2. Open scene 'asdf'
3. Enter playmode
- Console spammed with two assert messages:
RendererUpdateManager only synchronizes renderers that are added to the scene, so AssertIsTransformInfoUpToDate can only be called on renderers that are added to the scene
In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first
4. Enable mesh renderer for the Sphere GO
- Assertions stop, sphere is renderer with red material
5. Disable mesh renderer
- Assertions spam again, the sphere is black
Regression introduced in: 5.6.0b8
Reproduced on: 5.6.0b8, 5.6.0f3, 5.6.1p2, 2017.1.0b8, 2017.2.0a2
Not reproduced on: 5.5.4f1, 5.6.0a1, 5.6.0b1, 5.6.0b7
Fixed in: 2017.2.0a4
Backported to: 5.6.2p1, 2017.1.0f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Add comment