Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.2f1
2020.1
2020.2
2020.2.0a8
Issue ID
1240432
Regression
No
[Profiler] Switching Profiler Target Mode from 'Editmode' to 'Playmode' under Preferences does not work
Switching the Profiler Target Mode between 'Editmode' and 'Playmode' from the Preferences window does not reflect on opening the Profiler Window.
Refer to the attached Video
Steps to Reproduce:
1. Create a New Project
2. Window > Analysis > Profiler (Observe Target i.e. Playmode/Editmode)
3. Close Profiler Window
4. Edit > Preferences > Analysis > Profiler > Default Editor Target Mode > Editmode
5. Repeat Step 2
6. Edit > Preferences > Analysis > Profiler > Default Editor Target Mode > Playmode
7. Repeat Step 2
Actual Result:
Profiler continues to Profile for Editor even though Target is set to 'Playmode' in Preferences
Expected Result:
Profiler sets Target mode based on the Setting from Preferences
Note:
Profiler "Target Mode" option in Preferences > Analysis > Profiler was introduced in 2019.3.2f1
Occurring on:
2020.2.0a8, 2020.1.0b6, 2019.3.10f1, 2019.3.2f1
Environment:
Windows 10 and macOS 10.14
License type: Pro
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2020.2):
Changed Profiler settings option name and tooltip to clarify what it does. Tried multiple alternative variants, and anything else is a UX nightmare.