Search Issue Tracker
Fixed in 9.0.0-preview.1
Votes
1
Found in [Package]
6.9.0
Issue ID
1205185
Regression
No
[URP] Toggling Camera Override on first Renderer Feature in the list internally toggles it for all other Renderer Features
Reproduction steps:
1. Open project in "2020.1.0a17.zip"
2. Open "SampleScene.unity"
3. Notice that there are 2 Cubes in Scene which have Different Layers L1 and L2
4. Notice that ForwardRenderer renders nothing but these two Layers L1 and L2 using Renderer Features
5. Notice that Camera is in Orthographic mode
6. Toggle Camera Override for the first Renderer Feature in list using ForwardRenderer
Expected result: Camera override applies only for the Object that is in Layer L1
Actual result: Camera override applies for both GameObjects
Reproducible with: LWRP 6.9.0 (2019.2.18f1), URP 7.1.6 (2019.3.0f4, 2020.1.0a17)
Could not test with: 2017.4, 2018.4 because these versions do not support URP 7.1.1 and above
Notes:
1. The issue reproduces only when Camera Override is toggled for the first element in Renderer Features list and works as intended when toggling it for other elements
2. First URP version to support Renderer Features is URP 7.1.1
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 9.0.0-preview.1):
Issue solved by moving away from ReorderableList and the double serialisation layer