Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1264787
Regression
No
[Profiler] Counter makes it look like profiler has "lost" data
steps to repro:
1. set the profiler capture limit in preferences to max (2000)
2. open profiler
3. profile edit mode for over 2000 frames
4. save capture
5. clear profiler
6. load from binary file (select file just saved)
7. only contains 2000 frames
Expected: all frames shown in counter are saved
Actual: only frames visible in profiler are saved
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note (2021.2.X):
As it stands, this is By Design, where the Design is admittedly Sub-optimal. However this is a conglomerat of different issues that we are looking into as part of other work, which should make both the UI and the handling of this better and clearer. This bug has been used as feedback towards that work and will be reexamined at a later point or resolved as part of that feature work.