You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our map usage is fairly straightforward, but we've noticed that the puck2D is causing CPU usage in XCode debugger to hover at 30-60% even while idling on the map. If we remove the puck, we sit at 0-5%, as we'd want. I tried disabling the animation via the following code and it had no effect, but maybe I'm not successfully disabling it?
Thanks for the report, @samskinner32. I'm closing this ticket in favor of #1939.
Please, take a look at the provided workaround options: #1939 (comment)
* Make padding optional in `cameraForCoordinateBounds` (#1978)
* Make padding optional in `cameraForCoordinateBounds` and `cameraForCoordinates`
* Add changelog entry
* Update API breakage allowlist
* Add missing dependencies to DebugApp (#1983)
* Add missing dependencies to DebugApp
* Make MAPBOXMAPS_PATH project-specific, not target-specific as it's redundant
* Remove redundant artifacts (#1969)
* Update release readme maps version
* Remove xcodebuild log generated by a wrapper
* Update SDK version to 11.1.0
* Update CoreMaps/Common
* Changelog
* Update license
---------
Co-authored-by: Roman Laitarenko <[email protected]>
Co-authored-by: Aleksei Sapitskii <[email protected]>
Environment
Observed behavior and steps to reproduce
Our map usage is fairly straightforward, but we've noticed that the
puck2D
is causing CPU usage in XCode debugger to hover at 30-60% even while idling on the map. If we remove the puck, we sit at 0-5%, as we'd want. I tried disabling the animation via the following code and it had no effect, but maybe I'm not successfully disabling it?Expected behavior
I would expect the puck to not increase CPU usage so drastically.
The text was updated successfully, but these errors were encountered: