Search Issue Tracker
Fixed in 8.0.0
Fixed in 7.1.8
Votes
0
Found in [Package]
7.1.1
Issue ID
1189196
Regression
Yes
UniversalRenderPipelineAsset.scriptableRenderer throws NullReferenceException when trying to get the current ScriptableRenderer
Steps to reproduce:
1. Open the attached project "1189196.zip"
2. Open the SampleScene
3. Enter the Play mode
4. Observe the Console
Expected results: No errors or exceptions are thrown in the console
Actual results: "NullReferenceException: Object reference not set to an instance of an object" on 'm_Renderers' is thrown
Reproducible with: Universal RP 7.1.1, 7.1.2 (using 2019.3.0b4, 2019.3.0b7, 2020.1.0a8)
Not reproducible with: Universal RP 7.0.0, 7.0.1 (using 2019.3.0b3, 2019.3.0b4)
Note:
- On URP 7.1.1 Renderer List now appears under the General area of UniversalRenderPipelineAsset UI.
- In 2019.3, active render pipeline is now set via QualitySettings, or if no value is set then falls back to GraphicsSettings.
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
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
- Display issues in VideoPlayer when using Screen.SetResolution on certain Google Pixel devices
- Crash on Texture::TextureIDMapInsert when opening a specific project
- Null reference exceptions occur when ScriptableObjects saved in the same .asset file are referenced in runtime
Resolution Note (fix version 8.0.0):
Issue caused by code running before any rendering had begun in the first frame, solved by forcing creation of Pipeline earlier if required, but ideally any code dealing with rending should be done when the frame begins to render using the SRP callbacks
Verified in
Version: 2020.1.0a20.2541
Revision: trunk 019325219793
Built: Thu, 16 Jan 2020 04:57:18 GMT
with URP package 7.1.8
Resolution Note (fix version 7.1.8):
Issue caused by code running before any rendering had begun in the first frame, solved by forcing creation of Pipeline earlier if required, but ideally any code dealing with rending should be done when the frame begins to render using the SRP callbacks.
Verified in
Version 2019.3.0f6 (27ab2135bccf)
Wed, 22 Jan 2020 05:13:15 GMT
Branch: 2019.3/staging
with URP package 7.1.8