Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.11f1
Issue ID
UUM-30216
Regression
No
Renderer Feature settings on the main asset aren't updated when changing Renderer Feature settings on the sub asset
How to reproduce:
1. Open the attached user project “Playground.zip“
2. Select the “GaussianBlurFeature“ asset (Assets/Settings)
3. Change the A value to any other value
4. Select the “New Universal Render Pipeline Asset_Renderer“ asset
Expected result: The A value in the Gaussian Blur Feature has changed
Actual result: The A value in the Gaussian Blur Feature didn’t change
Reproducible with: 2022.2.11f1
Can’t test with: 2020.3.46f1 (Errors in the Console), 2021.3.21f1 (Error CS1061: 'ScriptableRenderer' does not contain a definition for 'cameraColorTargetHandle'), 2023.1.0b8, 2023.2.0a (Error CS0619: 'ScriptableRenderPass.Blit(CommandBuffer, RenderTargetIdentifier, RenderTargetIdentifier, Material, int)' is obsolete: 'Use RTHandles for source and destination')
Reproduced on: macOS 13.0.1 (Intel)
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note:
The workaround will be to access the RendererFeatures through the renderer it is contained within. We have set it as won't fix since the user already can work around this bug as described above. We won't be able to fix it within a reasonable time.
Resolution Note (2022.2.X):
The workaround will be to access the RendererFeatures through the renderer it is contained within. We have set it as won't fix since the user already can work around this bug as described above. We won't be able to fix it within a reasonable time.