Search Issue Tracker
Won't Fix
Votes
1
Found in
5.2.1p1
Issue ID
743145
Regression
No
[Deferred] Artifacts in deferred (GBuffer has incorrect values?) if one camera uses the clear mode "don't clear"
Steps to reproduced:
1. Open attached project "Deferred.zip"
2. Open scene "Deferred"
3. Inspect "Main Camera (1)" and "Main Camera (2)"
4. Notice that clipping planes of these cameras are intersecting
Actual result: In the game view, notice how the part of the cube and both spheres are completely white
Expected result: Cube and both spheres would be red
Note: This only happens when camera with greater depth ("Main Camera (2)") has "Clear flag" set to "Don't clear".
Bug doesn't happen in orthographic mode or when using forward rendering path.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Fixed with new Scriptable Render Pipeline, as you could specify the exact layers and handle the comping of two cameras exactly how you intend to need them.