Search Issue Tracker
Fixed in 5.3.6
Votes
55
Found in
5.3.4p4
Issue ID
790264
Regression
Yes
World space canvas aren't being rendered
Steps to reproduce:
1. Open project
2. Open scene "TestBUG"
3. Go to game view
-Notice that canvas disappear after few seconds. Resizing game view will make canvas re-appear for a short time
In scene view, canvas are rendered as expected
Reproduced with: 5.3.4p2, 5.3.4p4
Not reproducible with: 5.3.4p1, 5.4.0b14, 5.4.0b16
Regression introduced in: 5.3.4p2
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
rihdus
May 26, 2016 18:46
This is not fixed in 5.3.5p1. World canvas does not render to a render texture.
image28
May 23, 2016 22:56
My issue was slightly different, so filed bug report case 799554
image28
May 22, 2016 23:37
Still happening in Unity 5.3.5f1 on my system. Also think scaling of parent objects and canvas may have something to do with it.
vamky
May 22, 2016 12:52
Have been waiting for fix on this, too.
WillemKokke
May 20, 2016 17:39
To be clear, this only happens when trying to render a world space canvas to a render texture.
WillemKokke
May 20, 2016 17:36
Reproduced in 5.4.0b18 as well
WillemKokke
May 20, 2016 15:59
Still happening in 5.3.5f1 as well, it's seriously affecting my google cardboard project...
benthroop
May 10, 2016 04:46
Been waiting for this to get a fix and it's still present in 5.3.4p6
Poupi
May 09, 2016 09:19
If we should read Unity 5.3.4p6 instead of Unity 5.3.6, the bug still exists.
howardt12345
May 06, 2016 19:54
Where the hell do we get this "Unity 5.3.6"???