Map performance is terrible

Completed
Follow
Kenneth Argo

I'm finding that the performance of the MapWidget is indirectly proportional to the number of map markers and polylines shown on the map and it doesn't take many before the map slows so much that users are impacted.

For example, I have cases with 100 markers with flight lines between each and any operation to reposition the map by the user causes the map to temporarily freeze (in best case) and go temporarily blank (in the worse cases).

I've traced and logged and verified that none of my app's code is being accessed and see significant logging from within the UI/UX SDK.

This is on the M300 controller, using MapBox.

Any ideas for a solution before I start playing games like hiding/unhiding points dynamically?

0

Comments

10 comments

Date Votes
  • DJI Developer Support
    I think it is the Remote Controller's hardware configuration is poor. It only leave about 1.5G RAM for 3 party app. Maybe try an Android tablet and connects with M300 remote controller and see what happens.
    0
    Comment actions Permalink
  • Kenneth Argo

    It does happen a bit less on a tablet but still very bad, especially when waypoint count approaches 100 or more. A table connecting to the m300 controller isn't a practical solution for field work. Sorry.

    Is pilot app have less of an issue because it doesn't use the same sdk as mobile apps?

    0
    Comment actions Permalink
  • DJI Developer Support
    DJI Pilot will be very laggy also if you draw 100 waypoints on the map. Currently no solution for this.
    0
    Comment actions Permalink
  • Kenneth Argo

    I checked the Pilot, and it doesn't appear to have the same issue but from watching how the map reacts it appears that Pilot might be using an overlay to hold the points and not actually using point markers.

    Can you confirm?

    Unfortunately, the UX SDK doesn't expose overlays so that isn't an option at this time for apps using the UX SDK.

    0
    Comment actions Permalink
  • DJI Developer Support
    The dev team from Pilot said they are using point marker from the map api. But may be it is they way to draw the point may cause this bad performance in UXSDK. Pilot team said they only draw the additional point when they want to add. If UXSDK re-draw everything when adding a point, this bad performnce may occur, we will check.
    0
    Comment actions Permalink
  • DJI Developer Support
    Another approach would be update the mapbox api version to latest, and try a method called initMultipleSource to add multiple markers once at the time. Have a look the latest mapbox api.
    0
    Comment actions Permalink
  • Kenneth Argo

    Since the Mapbox API version is included in the UI SDK it's easily replaced.  I could inject a new version but that could lead to random issues if the newest SDK isn't fully compatible.

    I think you are correct, that the UI SDK redraws all points; I notice a flash of all points as I scroll.

    I know there is a UI SDK update due end of January 2022, any change it's coming soon?  I'm blocked from updating the SDK until the new UI SDK is released (the new SDK isn't compatible with the old UI SDK).

    0
    Comment actions Permalink
  • DJI Developer Support
    UXSDK 4.16 does some change in updating APIs and supporting M300,M2EA in some UI elements. This is most likely the last major version in 4.X. We will release 5.0 very soon.
    0
    Comment actions Permalink
  • Kenneth Argo

    Is there a release date for UI/UX SDK?  I know it was due in January, I've been waiting on the release because the 4.15 release of the UI/UX SDK crashes if I try to use the 4.16 MSDK.

    Thanks

    0
    Comment actions Permalink
  • DJI Developer Support
    UXSDK is already released, we haven't sent any official email yet. You can go to the Github and download it. Link: https://github.com/dji-sdk/Mobile-UXSDK-Android
    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post