Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4
2018.4
2019.3
2019.3.5f1
2020.1
2020.2
Issue ID
1227959
Regression
No
Camera's depth is ignored when calling Camera.Render() for Render Texture with "Skybox" and "Dont Clear" cameras
How to reproduce:
1. Open attached project "Depth Clear Test.zip" and scene "SampleScene"
2. Enter play mode
3. Observe the Game view
Expected result: the blue square is visible and behind the green square
Actual result: blue square is visible and in front of the green square
Reproducible with: 2017.4.38f1, 2018.4.20f1, 2019.3.6f1, 2020.1.0b2, 2002.2.0a3
-
zemayk
Mar 24, 2020 13:07
Rdxhd mоvіе 2020 is rеallу a gооd рlаtfоrm wherе customers cаn dоwnloаd thеіr favorіte latеst Hindi moviеs online аt frее оf are priced.
-
Clonkex
Mar 18, 2020 22:58
Well that's BS. Not only is it extremely unlikely that "many users" are using Camera.Render() into the same render texture as another camera with the clear flags mistakenly set to "Don't Clear" when they actually want "Depth Only", the built-in renderer's camera stacking cannot possibly rely on the hack of ignoring the "Don't Clear" flags for manual rendering only but not for automatic rendering! That's nonsense! Please review and make sure you've fully understood the problem!
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
- [iOS]"The destination host has an erroneous SSL certificate" error is thrown when using UnityWebRequest to connect to the server with a self-signed certificate
- Freeze/crash on DynamicHeapAllocator::Allocate when opening a specific project
- Text Settings Inspector sections names have no padding
- UI elements shrinking, misaligned buttons, swapped icons, or incorrect styles when rapidly cycling through Scenes in the Player
- Text field does not disappear if Ctrl+Z is pressed while editing in Viewport
Resolution Note:
This is part of the built in renderer camera stacking. We can not change this behaviour now at risk of regressing many users projects.
Workaround: have the 'render texture' settings match the current quality settings (msaa and color format)