Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0b5, 2023.3.X
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a20
2023.2.0a1
Issue ID
UUM-20646
Regression
No
SRP constructor is called when the scene has not been loaded
How to reproduce:
1. Open the attached user project "SRPConstructor.zip"
2. Observe the Console
Expected result: "OnEnable" is logged after "RenderPipeline Constructor"
Actual result: "RenderPipeline Constructor" is logged after "OnEnable"
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Reproducible on: macOS 12.5 (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
- WebGPU errors when CoreCopy shader is used to copy an MSAA texture
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
Resolution Note (fix version 2023.3):
Unity does not switch the render pipeline immediately when you set GraphicsSettings.currentRenderPipeline or QualitySettings.renderPipeline. Unity only instantiate a new RenderPipeline instance the first time any Camera renders after you set a new RenderPipelineAsset. To make it more clear we introduced two new callbacks in RenderPipelineManager.
Subscribe to activeRenderPipelineCreated to know that RenderPipeline is created.
Subscribe to activeRenderPipelineDisposed to know that RenderPipeline is disposed.
Resolution Note (fix version 2023.2):
Unity does not switch the render pipeline immediately when you set GraphicsSettings.currentRenderPipeline or QualitySettings.renderPipeline. Unity only instantiate a new RenderPipeline instance the first time any Camera renders after you set a new RenderPipelineAsset. To make it more clear we introduced two new callbacks in RenderPipelineManager.
Subscribe to activeRenderPipelineCreated to know that RenderPipeline is created.
Subscribe to activeRenderPipelineDisposed to know that RenderPipeline is disposed.
Resolution Note (fix version 2023.1):
Unity does not switch the render pipeline immediately when you set GraphicsSettings.currentRenderPipeline or QualitySettings.renderPipeline. Unity only instantiate a new RenderPipeline instance the first time any Camera renders after you set a new RenderPipelineAsset. To make it more clear we introduced two new callbacks in RenderPipelineManager.
Subscribe to activeRenderPipelineCreated to know that RenderPipeline is created.
Subscribe to activeRenderPipelineDisposed to know that RenderPipeline is disposed.
Resolution Note (fix version 2022.3):
Unity does not switch the render pipeline immediately when you set GraphicsSettings.currentRenderPipeline or QualitySettings.renderPipeline. Unity only instantiate a new RenderPipeline instance the first time any Camera renders after you set a new RenderPipelineAsset. To make it more clear we introduced two new callbacks in RenderPipelineManager.
Subscribe to activeRenderPipelineCreated to know that RenderPipeline is created.
Subscribe to activeRenderPipelineDisposed to know that RenderPipeline is disposed.
Resolution Note (fix version 2021.3):
Unity does not switch the render pipeline immediately when you set GraphicsSettings.currentRenderPipeline or QualitySettings.renderPipeline. Unity only instantiate a new RenderPipeline instance the first time any Camera renders after you set a new RenderPipelineAsset. To make it more clear we introduced two new callbacks in RenderPipelineManager.
Subscribe to activeRenderPipelineCreated to know that RenderPipeline is created.
Subscribe to activeRenderPipelineDisposed to know that RenderPipeline is disposed.