Search Issue Tracker
By Design
Votes
0
Found in [Package]
Issue ID
1298955
Regression
No
Post Processing don't work on build and output null error in log
Creating post processing layer and camera is throwing a null ref.
Repo Steps:
1. Open the attatched project
2. Load 'TestScene'
3. Build and run
Expected results: The game runs with the bloom effect that it had in the editor
Actual results: There is a null ref and the bloom(and all ppv2 effects) fails to run
Note: This seeminly happens as they setup a new camera with post processing via API. On the camera, a script called 'CameraClose' L68 sets up a new post processing layer on teh camera and disables the existing one, if you comment out lines 68-71 the issue goes away. Interestingly this doesnt repo in the editor, so there must be some editmode resource loading that happens when adding a post process layer that doesnt execute in standalone.
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
As described in the documentation, you need to bind the resource asset to the post process layer or it won't be able to find the post process shaders. See the additional notes here: https://docs.unity3d.com/Packages/com.unity.postprocessing@3.0/manual/Manipulating-the-Stack.html#additional-notes