Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10, 7000.0.0a1
Votes
1
Found in
2021.3.33f1
2022.3.14f1
2023.2.2f1
2023.3.0a16
Issue ID
UUM-57758
Regression
No
The Physics 2D Profiler module does not display the information about processed physics in the scene when profiling the application as a Development Build
How to reproduce:
1. Open the “Repro“ project
2. Open the “Window > Analysis > Profiler“
3. Open the “Go to the "File > Build Settings..."
4. Toggle on the Development Build and press the "Build & Run" button with the “Overlap Test“ Scene selected
5. In the Profiler window select the running Player as the target to profile your application on
6. Observe the Physics 2D Profiler module
Expected result: Timings and other categories do not drop to the zero value when profiling the Development Build
Actual result: All categories except the Timings category drop to the zero value when profiling the Development Build
Reproducible with: 2021.3.33f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: Not reproducible when profiling in Play mode
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Add comment