Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-37945
Regression
No
Profiler fails to pull data from the Player when Building And Running a development build
Reproduction steps:
1. Create a new 3D (URP) project
2. Go to File > Build Settings and enable the “Development Build“ and “Autoconnect Profiler“ options
3. Click “Build And Run“
4. Observe the Profiler window
Expected result: The Profiler pulls data from the Player
Actual result: The Profiler connects but does not pull data from the Player
Reproducible with: 2021.3.27f1, 2022.3.1f1, 2023.1.0b20, 2023.2.0a18
Reproduced on: Windows 10 Pro
Note: Reproduction is really inconsistent. If the issue does not reproduce the first time repeat step 3 until it does
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:
This issue is not reproducible by Kernel QA. Closing for now, until we can get more information on the issue.
Resolution Note (2023.2.X):
This issue is not reproducible by Kernel QA. Closing for now, until we can get more information on the issue.