Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.40f1
Issue ID
UUM-75380
Regression
No
Frame Debugger does not display individual Draw Calls in the Game view or the Player when using Camera Stacking
How to reproduce:
1. Open the “ReproFrameDebugger“ project
2. Open the “CameraStackingScene“
3. Open the “Window/Analysis/Frame Debugger“ window and Enable it
4. In the Frame Debugger navigate to any of the “Draw Mesh“ calls under the “RenderLoop.Draw/Canvas.RenderSubBatch“
5. Observe the Game view
Expected result: The Game view shows the materials being drawn
Actual result: The Game view is grey or black
Reproducible with: 2021.3.40f1, 2022.2.0a2
Not reproducible with: 2022.3.37f1, 6000.0.10f1
Fixed in: 2022.2.0a3
Reproducible on: macOS 14.5 (Intel), Windows 10 (User’s)
Not reproducible on: No other environments tested
Notes:
- Reproducible in the Player with attached Frame Debugger
- Reproducible both in the Play Mode and Edit Mode in the Editor
- Without the Camera Stacking (using a single camera) the Frame Debugger works as expected, it can be observed after opening the “SingleCameraScene“ and going through steps 3-6
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Resolution Note:
The issue is fixed in 2022 LTS, 2021 LTS will soon end the support.