Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.3.X
Votes
0
Found in
2017.4.0f1
2017.4.30f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a3
Issue ID
1181967
Regression
No
CullingGroup.QueryIndices only returns results for one camera
Steps to reproduce:
1. Download attached project
2. Open "TestCullingGroup" scene
3. Enter play mode
4. Check UI in Left corner
Results: On one camera CullingGroup.QueryIndices doesn't work. Cameras are in the same location and using two CullingGroups with the same settings.
Reproduced with: 2020.1.0a3, 2019.3.0b2, 2019.2.4f1, 2018.4.9f1, 2017.4.32f1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2018.4):
2018.4.18f1