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
2019.4
2020.3
2021.2
2021.2.10f1
2022.1
2022.2
Issue ID
1403469
Regression
No
Sequential shader compilation significantly slows down AOV capture when using the Recorder package
How to reproduce:
1. Open users attached project
2. Open Assets > Scenes > SampleScene.unity
3. Open Window > General > Recorder > Recorder Window
4. In the Recorder window click the "START RECORDING" button
5. Open the Task Manager
6. In the Task Manager locate and expand "Unity Editor"
7. Observe the Task Manager
Expected result: Multiple "Unity Shader Compiler" processes are used
Actual result: Single "Unity Shader Compiler" process is used
Reproducible with: 2019.4.35f1, 2020.3.29f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a6
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (2022.2.X):
Fixing this requires non-trivial changes to the render loop code.
We will schedule this as feature work and prioritise with other features.