Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.1f1
Issue ID
1010077
Regression
No
AfterEverything Command Buffer does not receive the output from BeforeImageEffects command buffer
How to reproduce:
1. Download attached project file and open "Occlusion" Scene
2. Open and run the frame debugger
3. Notice that the occlusion effect is applied but does not appear in the next step or the final frame render
Actual result: Two command buffers that execute on BeforeImageEffectsOpaque and AfterImageEffects (or AfterEverything) are attached to the same camera. The camera targets a rendertexture. The last command buffer takes the output of that buffer and blits it to another texture. Some effects applied in the image effects pass do not show in AfterImageEffects or AfterEverything
Reproduced with: 2017.2.2f1, 2017.3.1p3, 2018.1.0b10, 2018.2.0a3
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
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
- Error “NullReferenceException: Object reference not set to an instance of an object“ is present when the UI Toolkit Debugger window is docked and inactive on Editor launch
- RenderTexture pixels are gray when created without drawing on macOS
Resolution Note:
PPv1 has been deprecated in 2018.1.