Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.3.X
Votes
0
Found in
2018.4.0f1
2019.4.10f1
2020.2.0a1
Issue ID
1278884
Regression
No
Frame Debugger doesn't work when using Camera.SetTargetBuffers
Reproduction steps:
1. Download and open the attached "FrameDebuggerSetTargetBuffers" project
2. Open the "TestCase" scene
3. Enter Play mode
4. In the Frame Debugger window, press "Enable"
Expected result: Frame debugger shows different frames/draws in the game view after selecting different items from its list
Actual result: Frame debugger shows the same frame/draw in the game view for all different items in the list
Reproduces on: 2018.4.27f1, 2019.3.16f1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.21f1