Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.23f1, 2023.2.18f1, 6000.0.0b12
Votes
0
Found in
2021.3.34f1
2022.3.19f1
2023.1.20f1
2023.2.8f1
2023.3.0b4
6000.0.37f1
Issue ID
UUM-61605
Regression
No
Deep Profiling Support is labeled differently depending on if Development Build is enabled or disabled in Build Settings
How to reproduce:
1. Create a new project
2. Go to "File" ->"Build Profiles"
3. Click "Asset Import Overrides" and observe it
Actual result: When the "Development Build" option is disabled, the "Deep Profiling" greyed-out option is labeled without "Support", when it is enabled it is labeled as "Deep Profiling Support"
Expected result: The "Deep Profiling" option is always labeled the same
Reproducible with: 2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.1.20f1, 2023.3.0b4
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
Add comment