AssertionException in Post Process Stack 2.2.2

Unity Engine
1

Just updated to 2.2.2 for Post Processing and it works but I keep getting this error in the console:

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)
UnityEngine.Assertions.Assert.IsNotNull[T] (T value, System.String message) (at C:/buildslave/unity/build/Runtime/Export/Assertions/Assert/AssertNull.cs:46)
UnityEngine.Assertions.Assert.IsNotNull[T] (T value) (at C:/buildslave/unity/build/Runtime/Export/Assertions/Assert/AssertNull.cs:38)
UnityEngine.Rendering.PostProcessing.RuntimeUtilities.get_copyStdMaterial () (at Library/PackageCache/com.unity.postprocessing@2.2.2/PostProcessing/Runtime/Utils/RuntimeUtilities.cs:268)
UnityEngine.Rendering.PostProcessing.PostProcessLayer.BuildCommandBuffers () (at Library/PackageCache/com.unity.postprocessing@2.2.2/PostProcessing/Runtime/PostProcessLayer.cs:605)
UnityEngine.Rendering.PostProcessing.PostProcessLayer.OnPreCull () (at Library/PackageCache/com.unity.postprocessing@2.2.2/PostProcessing/Runtime/PostProcessLayer.cs:440

Is this known, and is there a fix?

1 Like
2

If you have Shaded Wireframe turned on in the scene view then the console is spammed with this message constantly.

3

I’ve got very similar messages too. Just upgraded to PostProcessing Stack v2.22 from v2.17 or so. Unity version 2018.3.8f1.
If I do modifications to my code and come back to the editor, I’ll get these errors again and the Post Processing is disabled on the Game tab. Either clicking play or scene tab and back kinda resolves it. Hopefully it doesn’t cause any problems further down the ine.

4

This is a bug introduced in v2.1.8 (already reported on GitHub). Downgrading to 2.1.7 will “fix” this.

2 Likes
5

Also having this issue using Post Processing v2.2.2. Unity version 2019.3.0f1.

For me the message will get spammed in any shading mode.

1 Like
6

아니 시발 하루 이틀도 아니고 버그 덕지덕지 붙은걸 2019.3 verified 라고 내놓네

7

Having the same issue: Cinemachine 2.2.9 + Unity 2018.4.5f1
NullReferenceException: Object reference not set to an instance of an object
UnityEngine.Rendering.PostProcessing.RuntimeUtilities.get_copyStdMaterial () (at Library/PackageCache/com.unity.postprocessing@2.2.1/PostProcessing/Runtime/Utils/RuntimeUtilities.cs:269)
UnityEngine.Rendering.PostProcessing.PostProcessLayer.BuildCommandBuffers () (at Library/PackageCache/com.unity.postprocessing@2.2.1/PostProcessing/Runtime/PostProcessLayer.cs:605)
UnityEngine.Rendering.PostProcessing.PostProcessLayer.OnPreCull () (at Library/PackageCache/com.unity.postprocessing@2.2.1/PostProcessing/Runtime/PostProcessLayer.cs:440)

8

Its apparently been fixed in v2.2.3, but it has yet to appear in the package manager.

3 Likes
9

Having the same issue it’s quite troublesome, I’m looking forward the 2.2.3 update

10

That’s quite a spectacular fail. Don’t they do proper QA before stuff goes live? So much for LTS being the stable one…

1 Like
11

This bug is really annoying. It is causing my editor to crash frequently. Any idea when the fix is going up?

12

Don’t know why previous versions are no more available through the package manager. Manually changed to 2.1.7 in PackageManager/Manifest.json and downgraded properly. No more annoying error stack.

13

same, lots of errors in console - waiting 2.2.3)

14

Any estimate on when 2.2.3 is out? and why cant we revert to older versions through the package manager?

1 Like
15

you can - go to package manager → select the package → select remove → re-add the version you want to use

16

No, you can only install version 2.2.2 at least on my version 2019.3.0f3. But it’s maybe possible to bypass by changing the version in the package manifest, which feels like an unnecessary hacky workaround to me. I’m just going to wait for 2.2.3

17

I’m having the same issue with 2019.0f3, when I double click on the error it brings me to my camera game object which has a post-processing stack layer on it. Hope it’s fixed in version 2.2.3, otherwise, I’ll have to test my game by exporting it each time. When I press the play button, the editor completely freezes and I have to end the process in the task manager.

18

I’ve been having the same issue, everytime i press play i get a bunch of errors that when i click them they highlight my camera, and the only fix is removing the post processing layer, but i need it for the post processing volume to work. I’ve updated the post processing stack v2 in the package manager from 2.2.2 to 2.3.0, by clicking the dropdown arrow to the left of the package, and still i get the same errors. What should i do? I don’t have any extra windows, and i’ve previously utilized HDRP, LWRP and URP, but ultimately went back to the builtin pipeline, and i’ve already unistalled those packages from my project but now i’m getting these errors i didn’t get before so maybe there’s some residue left or something.

19

same

20

It’s June 9, 2020. Still having this issue.