Search Issue Tracker
By Design
Votes
8
Found in
2020.3
2021.2
2022.1
2022.1.0b8
2022.2
Issue ID
1403774
Regression
No
[HDRP] 120KB of GC and slow performance when calling Camera.Render()
Reproduction steps:
1. Open the user's attached project
2. Select File > Build and Run
3. Open Window > Analysis > Profiler
4. Observe ScriptRunBehaviourUpdate
Expected result: ScriptRunBehaviourUpdate doesn't take up a lot of CPU
Actual result: ScriptRunBehaviourUpdate takes up around 30-60% of the total CPU
Reproduced with: 2020.3.31f1, 2021.2.15f1, 2022.1.0a11, 2022.2.0a8
Could not test with: 2019.4.36f1 (errors in the build)
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Camera.Render() isn't supported by HDRP
AOV documentation for HDRP:
https://docs.unity3d.com/Packages/com.unity.render-pipelines.high-definition@14.0/manual/AOVs.html