Search Issue Tracker
Active
Under Consideration for 1.2.X, 1.3.X
Votes
1
Found in [Package]
1.2.0-pre.12 - Entities
1.3.X - Entities
Issue ID
ECSB-1019
Regression
No
“AnalyticsJobs:PhysicsBodiesAnalyticsJob” still gets called in the Editor when the Editor Analytics is disabled
Reproduction steps:
1. Open the attached “AnalyticsJobs” project
2. Open the Preferences window (Edit > Prefrences…)
3. Disable the Editor Analytics (General > Disable Editor Analytics) and restart the Editor
4. Open the “Assets/Benchmark/DynamicBenchmark/DynamicBencmarkECS” Scene
5. Open the Profiler window (Window > Analysis > Profiler)
6. Enter the Play mode
7. In the Profiler window click on any frame in the “CPU Usage” graph
8. Change the view to Hierarchy
9. In the search field type “PhysicsBodiesAnalytics”
Expected result: The search doesn’t show any results
Actual result: “AnalyticsJobs:PhysicsBodiesAnalyticsJob (Burst)” call is present in the search results
Reproducible with: 1.0.16 (2022.3.22f1), 1.1.0-pre.3 (2022.3.22f1), 1.2.0-pre.12 (2022.3.22f1, 2023.2.16f1, 6000.0.0b13)
Reproducible on: macOS 13.6.4 (Intel), Windows 11
Not reproducible on: No other environment tested
Note: If the call is not visible in the selected frame, select another frame, as in some frames the call is not being executed
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
alemnunez
Mar 26, 2024 16:02
This is a pretty large problem for games heavy on physics. In my game it's taking over 1ms on each execution of the job (freezing everything else until it's completed). And because it happens in the fixed step, sometimes it causes physics to also be executed twice in a frame, adding to almost 3ms of wasted time in the same frame.