Search Issue Tracker
By Design
Votes
0
Found in
2018.2.6f1
Issue ID
1084419
Regression
No
PostProcessing effect sets the Camera's DepthTextureMode when active, but doesn't clear it when inactive
To reproduce:
1. Download attached project "ProjectWithPostProcessingStack.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter Play mode
4. Observe that there is a GUILayout.Label showing the value of Camera's depthTextureMode property. It should start as None
5. Use the button in the UI to ENABLE the Depth of Field effect
6. Notice the Camera's depthTextureMode property changes to Depth
7. Use the button in the UI to DISABLE the Depth of Field effect
Expected Result: When the PostProcessing Effects are not using the Camer's Depth texture, the Camera's depthTextureMode is set to None
Actual Result: The Camera's depthTextureMode property stays as Depth, it does not change
Notes:
- This issue appears both on Windows and OSX
Reproduced on Unity 2018.1.9f2, 2018.2.10f1, 2018.3.0b3 and 2019.1.0a2
Could not check for regression on Unity 2017.* because project becomes corrupted
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This is not something we can fix without breaking other things (custom image effects that require DepthTextureMode come to mind).
For a complete description of the problem and potential solutions we tried (and side effects), please see this report on the Github repository:
https://github.com/Unity-Technologies/PostProcessing/issues/33