Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.3.0b7
6000.4.0a3
6000.5.0a1
Issue ID
UUM-122619
Regression
No
Changing Profiler Capture Target Frame Time has no effect in the Profiler data
Reproduction steps:
1. Create a new project
2. Open Profiler (Window > Analysis > Profiler)
3. Enter Play mode and ensure that data is being captured on the Profiler
4. Click on the Highlights CPU section and observe Selection Highlights Bottlenecks and CPU Highlights data
5. Press “Save current profiling information to a binary file” button
6. Change Target Frame Time to a lower number
7. Select the capture and observe Selection Highlights Bottlenecks and CPU Highlights data
Actual result: Selection Highlights Bottlenecks and CPU Highlights data is unchanged after changing Target Frame Time
Expected result: Selection Highlights Bottlenecks and CPU Highlights data shows different results after changing Target Frame Time
Reproducible with: 6000.3.0b7, 6000.4.0a3
Couldn’t reproduce with: 2021.3.58f1, 2022.3.68f1, 6000.0.60f1, 6000.2.8f1 (No Captures List section)
Reproduced on: Ubuntu 24.04, macOS Sequoia 15.4 (M4)
Note: Selection Highlights Bottlenecks data changes only when Target Frames Per Second (Highlights Module) setting in Preferences window is changed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
- No audio is played when Playbable Mixer is changed at runtime
- Editor hangs when painting Details containing 2D Mesh on Terrain
- No audio is played when TimelinePlayable has one output
Add comment