Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.1.1f1
Issue ID
954138
Regression
No
Instantiated sub-canvas gets invisible when another sub-canvas moves out of the screen if root canvas contains only sub-canvases
Reproduction steps (GIF attached):
1. Open the attached project.
2. Build it as standalone.
3. Click 'Instantiate Canvas 2'.
4. Click '<' near 'sub canvas1' text until 'SubCanvas 1' leaves the screen.
- 'SubCanvas 2' may become invisible now.
5. Move 'SubCanvas 2' around clicking '<' and '>' buttons near 'sub canvas2'
- 'SubCanvas 2' becomes invisible on some spots.
Expected behavior:
'SubCanvas 2' is visible all the time when it is on the screen.
Note:
Higher reproduction rate using full screen.
Sometimes 'SubCanvas 2' gets visible again when moved around.
Reproduced with:
5.5.5f1, 2017.3.0b2
iOS (easiest to reproduce) - 'SubCanvas 2' becomes invisible when 'SubCanvas 1' leaves the screen.
macOS Standalone, Windows Standalone - may require 'SubCanvas 2' movement.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment