Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.4
2020.3
2020.3.18f1
2021.1
2021.2
2022.1
Issue ID
1376800
Regression
No
Worldspace canvas is not visible under occlusion culling
Reproduction steps:
1. Download and open the attached "My project.zip" project
2. In the Hierarchy window, select the "Main Camera" camera
3. In the Scene window, move the camera along the Z-axis back and forth
4. Observe the Main Camera preview window
Expected result: The red circle is always visible
Actual result: The red circle disappears when the camera approaches it
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a13
Comments (2)
-
peter226
Aug 09, 2024 14:56
This is a terrible solution, a secondary camera is expensive. We need a checkbox to disable culling and / or perhaps a custom bounding box we can set up. This is insane.
For now I'll try to move the canvas position in the player's face before rendering, and call an event in a custom pass when I'm drawing the custom pass to move it back to the original position for correct matrices.
-
ted_01
Feb 14, 2022 11:00
A solution for certain cases is to have the UIs on a different layer, only visible to a separate camera and disable occlusion on it.
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
- [macOS] Localization files are not created in the Xcode project
- Entity ID for Tile objects is serialized twice which throws an error when using Debug Inspector
- Shader Graph information icon appears below the Property Type Node
- Adding a new Multiplayer Player Tag in the Project Settings window creates a new section in the Project Settings window instead of a popup which is inconsistent with the Editor’s Tags workflow
- String.CompareOrdinal intermittently return non-zero for non-unique instances of empty strings when Mono scripting backend is used
Resolution Note:
Based on internal design of the Canvas rendering system such a option is not available. Correcting this behaviour is out of scope of the maintenance Unity UI is receiving.