Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
3
Found in
2019.3
2019.3.7f1
2020.1
2020.2
Issue ID
1241218
Regression
Yes
[URP] Stencil settings of Render Object does not get applied when changing them in the ForwardRenderer asset
Reproduction steps:
1. Open the project from the attached file "1241218.zip"(link in edit)
2. From Assets open the CustomForwardRendererData asset
3. In the Inspector settings in New Render Objects section check the Stencil checkbox
4. De-select CustomForwardRendererData
5. Select it again and Inspect the Stencil property
Expected result: Stencil checkbox is checked
Actual result: Stencil checkbox is not checked
Reproducible with: 7.3.1(2019.3.12f1), 8.0.1(2020.1.0b8, 2020.2.0a9), 8.1.0(2020.1.0b8, 2020.2.0a9), 9.0.0-preview.14(2020.1.0b8, 2020.2.0a9)
Not reproducible with: 7.1.8(2020.2.0a9), 7.2.1(2020.2.0a9)
Could not test with: 4.10.0-preview(2018.4.22f1)(feature not introduced)
Notes:
- Reproducible with properties of Stencil
- Not reproducible with other properties of the Render Object
- Changing Stencil properties directly in the NewRenderObjects asset saves the changes correctly
Comments (3)
-
as87dgs6asg0a
Dec 24, 2020 20:10
I'm seeing this in the LTS version: 2019.4.14f1
-
Tim_unity2020
Nov 02, 2020 12:41
Same question as @THEONLYRUDEY. Please answer :D
-
TheOnlyRudey
Sep 04, 2020 07:59
Is there any possibility, that it'll be fixed in 2020.1 as for now it's still in review?
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note (fix version 2020.2):
Fixed in URP 10.0.0-preview.1