Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.4f1
2020.1
2020.2
Issue ID
1271502
Regression
No
Profiler window does not show multiple available targets for standalone builds
How to reproduce:
1. Open the attached 'project-1271502.zip' project
2. Build the 'Scenes/SampleScene' scene (make sure that 'Development Build' and 'Autoconnect Profiler' options are selected)
3. Launch two instances of the standalone build
4. Open the Profiler window
5. Observe the drop-down menu of the attaching options ('WindowsPlayer(...)')
Expected result: two standalone builds are available for profiling
Actual result: only one standalone build is available for profiling
Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.3f1, 2020.2.0a21
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in 2020.2.2f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.18f1