Search Issue Tracker
Fixed
Fixed in 2021.3.22f1, 2022.2.17f1, 2023.1.0b10, 2023.2.0a6
Votes
4
Found in
2020.3.35f1
2022.2.7f1
2023.1.0a1
2023.2.0a1
Issue ID
UUM-2698
Regression
No
GameObjects from 31st layer are not rendered when Camera.cullingMask is set to 'Everything'
Reproduction steps:
1. Open the attached 'AddressablesSceneProcessingTest' project
2. Open the 'SampleScene'
3. Observe the Game view
Expected result: The circle is rendered
Actual result: Circle is not rendered
Reproducible with: 2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0b16, 2022.2.0a12
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
- Vertex data is displaced when building with Addressables with Optimize Mesh Data enabled
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
Resolution Note (fix version 2023.2.0a6):
GameObjects from 31st layers are now rendered again when users select 'Everything' for Camera.cullingMask.
For existing cases, user has to manually select 'Everything' in the dropdown list even if all layers are already selected.
Resolution Note (fix version 2023.1.0b10):
GameObjects from 31st layers are now rendered again when users select 'Everything' for Camera.cullingMask.
For existing cases, user has to manually select 'Everything' in the dropdown list even if all layers are already selected.
Resolution Note (fix version 2022.2.17f1):
GameObjects from 31st layers are now rendered again when users select 'Everything' for Camera.cullingMask.
For existing cases, user has to manually select 'Everything' in the dropdown list even if all layers are already selected.