Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
6.8, 6.7.1, 6.5.3
Issue ID
1163713
Regression
No
[HDRP] Render Pipeline reference is lost when older package scene is opened
Steps to reproduce:
1. Open attached project
2. Make sure that HDRP Render Pipeline asset is added to Project Settings->Graphics
2. Add 04_Decals scene to the project
3. Open 04_Decals scene
4. Observe that Scriptable Render Pipeline asset reference is lost and assertion errors are thrown:
AssertionException: Assertion failure. Value was Null
Expected: Value was not Null
UnityEngine.Assertions.Assert.Fail (System.String message, System.String userMessage) (at C:/buildslave/unity/build/Runtime/Export/Assertions/Assert/AssertBase.cs:29)
UnityEngine.Assertions.Assert.IsNotNull (UnityEngine.Object value, System.String message) (at C:/buildslave/unity/build/Runtime/Export/Assertions/Assert/AssertNull.cs:58)
...
Expected result: scene with decals in older HDRP package should not cause hdrp errors breaking the pipeline
Reproduced in: 2020.1.0a7, 2019.3.0a6, 2019.2.0b5
Packages reproduced in: 7.1.2, 6.8, 6.7.1, 6.5.3
Comments (1)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Fragsteel
Nov 20, 2019 20:50
I got this error from source control - I added a new HDRP Render Pipeline asset in one branch, then switched branches and all my materials turned pink. It was because I gitignore'd whatever file holds the reference to the pipeline asset.
That's my fault, not a bug, but putting that here in case others stumble here like I did.