Requirements for Orbit 3D Mapping Viewer and Plugins

This page describes the requirements of the Orbit 3D Mapping Viewer and Plugins available for Orbit 3D Mapping Cloud and on-premises Orbit 3DM Publisher.
For legacy Flash Viewer and the Flash-based Plugins for Mobile and Oblique Mapping, see Requirements for Orbit Flash Viewer and Plugins

Orbit 3D Mapping Viewer and Plugins require access to the Orbit 3D Mapping Cloud or an Orbit 3DM Publishers to load Resources or a Publication.

Orbit 3D Mapping Plugins require access to https://cdn.3dmapping.cloud.
Orbit 3D Mapping Viewer doesn't need online connectivity.

Orbit 3D Mapping Viewer and Plugins require an up-to-date version of Chrome, Firefox, Microsoft Edge (Chromium) or Safari.
Internet Explorer and Edge cannot be used because these browsers do not support the required JavaScript libraries and 3D rendering techniques.

Orbit 3DM Viewer and Plugins use GPU (if available) and requires the availability of WebGL 1 including the extension EXT_frag_depth for 3D rendering.
If there is no physical graphic card, 3D rendering will be computed in software mode, using a software emulator like “Google SwiftShader” for Google Chrome. Rendering in software mode will reduce the performance of the 3DM Viewer.
Verify if your browser's WebGL compatibility: http://webglreport.com/.

Orbit 3D Mapping Viewer and Plugins require uses WebSocket communication protocol, see https://en.wikipedia.org/wiki/WebSocket.

• AutoCad Map 3D : version 2019 and 2020. Support for earlier versions is not guaranteed.
• System Browser: The plugin requires an up to date browser, see generic browser requirements above.

• ArcGIS Desktop : version 10.6 and 10.7. Support for earlier versions is not guaranteed.
• System Browser: The plugin requires an up to date browser, see generic browser requirements above.

• QGIS Desktop : version 3.4 and more recent versions.
• System Browser: The plugin requires an up to date browser, see generic browser requirements above.