Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.2f1
Issue ID
909909
Regression
No
Object inside Canvas gets rendered even if it is assigned to a Layer that is not rendered by the camera
To reproduce:
1. Open attached Unity project "CanvasTest2.zip"
2. Open scene "scene1"
3. Go into Play Mode
Expected result: Image should not be rendered by the camera since its Layer is not selected for rendering
Actual result: Image is rendered despite being on a custom Layer which is not selected to be rendered by the camera
Reproduced on: 5.4.5p1, 5.5.3p3, 5.6.1f1, 5.6.1p1, 2017.1.0b6
Note: added a gameObject called "SameLayerNotRendered". It has the same layer as the "Image" gameObject and it does not get rendered.
Note: Attached image "CustomLayerRendered.png" in which DoNotDisplayMe Layer is selected for rendering and renders both objects in that Layer (Image and SameLayerNotRendered) and another image "CustomLayerNotRendered.png" in which only UI Layer is selected for rendering, but Image is still rendered despite being on on a custom Layer not selected for rendering.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
Add comment