Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.66f2
6000.3.7f1
6000.4.0b8
6000.5.0a6
Issue ID
UUM-133778
Regression
No
Frame Count differs in the Frame Debugger after exiting Play Mode with the Frame Debugger Enabled
Steps to reproduce:
- Create a High Definition 3D Sample Template Project
- Open the Frame Debugger (Window > Analysis > Frame Debugger)
- Enter Play Mode
- Enable the Frame Debugger
- Exit Play Mode
Actual results: Frame count is different in the Frame Debugger after exiting Play Mode
Expected results: Frame count is the same as in Play Mode
Reproducible with versions: 2022.3.66f1, 6000.0.66f2, 6000.3.7f1, 6000.0.67f1, 6000.4.0b8, 6000.5.0a6
Tested on (OS): Windows 11
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 spike when loading a prefab using TextMeshPro in iOS Player
- [iOS] UI Toolkit's DropdownField fails to close on first tap when Windowed Apps is used
- VFX System Border text cursor is sometimes not visible
- Hub horizontal scroll hides all items when scrolled to the end
- GC Allocation of 384 B every frame when using CinemachineInputAxisController
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.