Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.8f1, 2023.1.9f1, 2023.2.0b5, 2023.3.0a1
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 2023.3.0a1):
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.0b5):
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.9f1):
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.8f1):
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.30f1):
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.