Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
10.2.2
Issue ID
1308454
Regression
No
ScriptableRendererFeature.Create() is being called more than once in playmode and in player
Steps:
1. Open attached project (20210115_URP_RenderCallback.zip)
2. Open RenderingCallback scene
3. Hit Play
4. Observe console
- there are 3 "ScriptableRendererFeature - Create()" log messages
5. Exit play
6. Make a standalone player
7. Run the player
8. Observer player log
- there are 2 "ScriptableRendererFeature - Create()" log messages
Reproducible in:
Unity 2021.2.0a3 + URP Graphics master 22Jan 9344cb9809816cc67c7e5f6ebbb7371f9248ed48
Unity 2020.2.2f1 + URP 10.2.2
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Re-work of the render features and their data layout will happen in 22, this will be a big change and currently without doing major data changes that could break users twice we will do it once in 2022 to lower the risk. As a work around for now, it is suggested if you need to generate and clean up a lot of resources it to either not use render features and inject the ScriptableRenderPasses manually into the cameras current renderer or to add some logic in the feature to make sure you do not re-create stuff if you do not need to.