Search Issue Tracker
Won't Fix
Votes
2
Found in
2019.2.5f1
2019.3
2020.2
Issue ID
1223421
Regression
No
Text flickers when it's copied to a Texture2D and assigned to a Sprite Renderer in 1 frame without waiting for end of frame
How to reproduce:
1. Open the user-supplied project
2. Enter Play Mode in the "SampleScene" Scene
3. In the Hierarchy window, select the "Renderer" GameObject
4. Navigate to the GameObject's "RT Scheduler" Script Component
5. Change the Renderer Type property to "Renderer Simple" while observing the Game view
Expected result: the text values remain constant
Actual result: the text changes values every couple of frames
Reproducible with: 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Could not test with: 2017.4, 2018.4 due to console errors
Reproduces on:
VLNQA00160 iPhone 6s iOS 13.3.1
Android devices (according to the user)
MacStandalone Player
Editor Play Mode
Notes:
1. Changing the Renderer Type property to "Renderer Simple" reproduces the issue on command; the behavior can still be observed while idling in Play Mode and watching the Game view for a minute or two.
2. Can be reproduced on multiple platforms - issue is more apparent in Player than Editor, but is reproducible both ways nonetheless.
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:
Since the new TextCore is coming soon and considering the complexity of this issue, this is being closed as WontFix.