Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.43f1
2022.3.46f1
6000.0.19f1
Issue ID
UUM-82430
Regression
No
[Editor] Profiler (Standalone Process) "Live" button is greyed out by default
Steps to reproduce:
1. Create a new project (2D or 3D)
2. Open the Profiler (Standalone Process) window at (menu: Windows > Analysis > Profiler (Standalone Process))
3. In the "Module details panel", observe the "Live" button behaviour
\\
Actual results: The "Live" button is greyed out
Expected results: The "Live" button is enabled by default
\\
Reproducible with versions: 2021.3.43f1, 2022.3.46f1, 6000.0.19f1
\\
Tested on (OS): Windows 11
\\
Notes:
- Reproducible in either Play or Edit mode in the Editor
- Not reproducible with the regular Profiler window
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
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
Resolution Note:
Closing this as won't fix because so few users actually use the Standalone Profiler, and this is as designed. We could try to explain this better to users but it's such a select group of users we aren't planning to do this any time soon. If we hear more about this from end users we might consider it.
Resolution Note (6000.0.X):
Closing this as won't fix because so few users actually use the Standalone Profiler, and this is as designed. We could try to explain this better to users but it's such a select group of users we aren't planning to do this any time soon. If we hear more about this from end users we might consider it.