Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.31f1
2021.3
2022.1
2022.2
Issue ID
1423852
Regression
No
RenderFeatures do not affect the Graphics settings when those are instantiated from AssetBundles
Reproduction steps:
1. Open the attached 'customer_project'
2. Go to the 'Window -> Asset Management -> Addressables -> Groups'
3. 'Build -> Clean Build -> All'
4. 'Build -> New Build -> Default Build Script'
5. After building Addressables go to the 'File -> Build Settings'
6. In the Scenes In Builds section make sure that only 'Scenes/LaunchScene' is included
7. Build and Run the Scene
8. Click on the 'LoadScene' button
9. Click on the 'Toggle SSAO' button
Expected result: The Screen Space Ambient Occlusion (SSAO) image effect applied to the Scene
Actual result: The effect doesn't show up
Reproducible with: 7.7.1 (2019.4.38f1), 10.9.0 (2020.3.34f1), 12.1.6 (2021.3.2f1), 13.1.7 (2022.1.0b16), 14.0.2 (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
- The Editor opens when the window is closed right after launch
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
Resolution Note:
This is closed by design but is noted as a feature request in the meantime there is a workaround for this:
var renderer = UniversalRenderPipeline.asset.scriptableRenderer;
var property = typeof(ScriptableRenderer).GetProperty("rendererFeatures", BindingFlags.NonPublic | BindingFlags.Instance);
List<ScriptableRendererFeature> features = property.GetValue(renderer) as List<ScriptableRendererFeature>;
features[0].SetActive(!features[0].isActive);