Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.11
Issue ID
1058770
Regression
No
[LWRP] Post Processing V2 effects appears inconsistently when changing the depth value on a different Camera
Steps to reproduce:
1. Open QA-supplied project
2. Open Scene "scene_main"
3. Change the depth value on the camera without the Post Processing attached ("__camera_secocond_ui")
4. Observe the Game view
Expected: The Post Processing either disappears or appears when the depth value is set to <=0 or >=0
Actual: the Post Processing appears on the following depth values: (<-1 and >=0 && <1)
Reproduced in: 2018.1.8f1, 2018.2.0f2, 2018.3.0a5
Notes: Only happens with LWRP
Earlier versions were not tested due to LWRP not being introduced yet
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
- Summary tab is selected but its content is not displayed when pressing Ctrl/Cmd+A in the Project Auditor window
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
Resolution Note:
LWRP does not support Screen Space - Camera mode. We will remove this option from UI when LWRP is enabled. The alternative is to use Screen Space - Overlay or World Space camera.
By using a second camera to render your UI you have extra culling cost, camera state setup and bandwidth cost by writing and reading more memory. If a second camera depends on the result of a previous one, the camera render target has to be initialized by reading external memory to GPU, this is especially troublesome in mobile as external reads from GPU memory consume power and therefore can cause device to overheat.