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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.