Players unable to render maps

Mappedin JS
1

Hello,

We noticed that some our players(touch/non-touch) are unable to render the mappedIn maps. When attempting to load the page that displays the map, the players go out of memory and restarts.

Is it possible to improve performance somehow? Is there a configuration or setting that can be tweaked to make it lightweight ?

Following are the bunch of players that are unable to render the map

  • Philips BDL4151T (touch)
  • Philips BDL4550D
  • Philips BDL3550Q
  • LG UH5C (WebOS 3.0)
  • LG SM3G (WebOS 4.0)
  • LG UH5E-BJ
  • Samsung QMR
  • Bluefin Linux RC3399 touch
  • LG UL3J (WebOS6)
2

Hey ParSR,

Are you setting the viewport within the page’s heading?

<meta name="viewport" content="width=device-width, initial-scale=1.0" charset="UTF-8" />

If not, try adding that. If these are mobile style devices it will ensure the map is rendered for mobile instead of a larger desktop screen, which will help to reduce memory usage.

3

Thank you. I did add these however the players are still not rendering the maps. Is there any other configuration that I can tweak perhaps?

4

Are you rendering the Map with the Mappedin SDK, using Mappedin Web or the Mappedin Viewer?

What version of Mappedin SDK are you using? We have reduced memory usage in version 6 compared to version 5.

5

We are using mappedIn Wed SDK. The current version being used is 6.0.1-alpha.25

6

Any takers for suggesting improvements ? This is a blocker for us !!!

7

I’ve been discussing this with the SDK development team. Right now, there isn’t a way for you to do reduce the overhead to render the map but it is something they’re going to look into.

Check back in with us in a few weeks.

8

Sure. Is it possible to get a list of dependent libraries being used ?
Some of the players may not be suitable for advanced JS libraries and we feel this might be a reason as well for players failing to render the maps.
For eg: On inspecting the layout, three.js usage is seen.

9

Sure thing. Here are the requirements and libraries used by the Mappedin SDK that could have an impact on hardware compatibility.

Libraries

  • Three.js
  • MapLibre

Graphics Hardware Requirements

  • WebGL 2.0 support is required

The following browser are currently officially supported

  • Chrome 51+
  • Safari 10+