Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1307699
Regression
No
Texture is drawn inconsistently when rendering Mesh to a RenderTexture and using Graphics.DrawMeshNow
Reproduction steps:
1. Open the attached "case_1307699.zip" project and Scenes/SampleScene scene
2. Enter the Play mode
3. Observe the Game view (try hovering the mouse over the GameObjects in the Hierarchy)
Expected result: Texture is always rendered
Actual result: Texture is sometimes rendered (mostly when hovering over UI elements with the mouse)
Reproducible with: 2018.4.31f1, 2019.4.19f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a3
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
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
Resolution Note (2021.2.X):
This behaviour is by design. DrawMeshNow will by default use the view matrix of the active camera when rendering (if there is an active camera). Active camera is then by itself not stable during calls to Update or coroutine execution which can make things flicker.
We have improved documentation and added a way to override the matrix if needed, although it is not the default behaviour.