Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:technology:platforms:specs_desktop [2019/03/20 12:19]
jve@orbitgt.com
+++ dev:technology:platforms:specs_desktop [2023/10/10 12:45]
jeroen
@@ Line 1: / Line 1: @@
-====== Requirements for Orbit Desktop =====
+====== Requirements for Orbit 3DM Desktop Products =====
 This page describes the hardware requirements for Orbit's desktop products.
@@ Line 5: / Line 5: @@
 The Orbit Mapping solutions do not require special hardware. \\
 However, make smart choices in relation to the volume of data to be processed and the expected performance.
+===== Screen Resolution =====
+Best layout and user experience guaranteed on screen resolution 1920 x 1080 or higher, without Display Scaling.
 ===== Operating System =====
-Windows or OSX. Technically Linux is supported as well. \\
+For more information about Windows, Linux, and Java requirements, see [[dev:technology:platforms:index|]].
-[[dev:technology:platforms:index|]].
 ===== Computing Power  =====
-Depending your expectations, type and volume of used resources (e.g. point cloud, imagery, base maps, ... ), here's a guideline :
+Minimum: 64 Bit OS, 16 GB ram, Quad-core.
-  * Minimum : 64 Bit OS, 4 GB ram, Dual core processor(s)
-  * Recommended : 64 Bit OS, 8 GB ram or more, Quad core processor
 ===== Software =====
-Next to Java, no special requirements.
+No additional software requirements. \\
+Required dependencies are packaged with the installation.
+Orbit is pure Java. The Java Runtime Engine (JRE) is included with the Orbit installation. \\
+Java doesn't need to be installed or updated. An existing Java installation won't generate conflicts with Orbit's JRE and vice versa.
 ===== Graphics Card =====
@@ Line 26: / Line 31: @@
 Orbit desktop products will use the 3D graphics card (GPU) to render complex 3D graphics, e.g. 3D tin models. \\
-If no 3D graphics card is available, complex 3D requests will be processed by the JRE using CPU.
+If no 3D graphics card is available, complex 3D requests will be processed by the Java Runtime using CPU.
-Virtual environments (like Citrix, Virtualbox, VMWare, etc.) are still struggling to incorporate movies or the use of moving high resolution images and may thus cause the Client to act slower. \\
+Virtual environments (like Citrix, Virtualbox, VMWare, etc.) are still struggling to incorporate movies, the use of moving high-resolution imagery, and complex 3D graphics. The result can be Desktop and Web clients to act slower or fail to render the 3D Scene. \\
-For example, smooth viewing and roaming through high resolution spherical images or free navigating through a 3D point cloud requires an adequate frame refresh rate. These actions can be compared with watching a HD movie. \\
+For example, smooth viewing and roaming through high-resolution spherical images or free navigating through a 3D point cloud requires an adequate frame refresh rate. These actions can be compared with watching an HD movie. \\
 When using Citrix we do advise XenApp, including video optimization and a 1GB network connection.
 ===== Internet Connectivity =====
-The Orbit desktop Standalone requires online connectivity to the Orbit License Service to operate, see [[dev:technology:core:online_license_activation|]]. \\
+Orbit desktop Standalone products require online connectivity. \\
 Orbit desktop Clients do not require online access but require connectivity with their Orbit Server, see [[dev:technology:platforms:specs_server|]].
+=== Orbit Online Acitvation ===
+[[https://activation.orbitgt.com/*]]
+The Orbit desktop Standalone products, Orbit-licensed, require online connectivity to the Orbit License Service to operate, see [[dev:technology:core:online_license_activation|]].
+=== Login and Upload to 3DM Cloud ===
+https://account.orbitgt.com/ \\
+[[https://api.3dmapping.cloud/api/*]]
+The Orbit 3DM Content Manager and Orbit 3DM Import and Upload Tool products require online connectivity to the Orbit Account Service and 3D Mapping Cloud services to login and upload data.
+=== Base Maps ===
+[[https://*.virtualearth.net/]]
+The Orbit desktop Standalone products require online connectivity to use Microsoft BING maps. \\
+BING maps are shipped by installation but are not mandatory to operate the application \\
+=== 3D Annotations ===
+[[https://3dmapping.cloud/*]]
+The Orbit desktop Standalone and Orbit desktop Client products require online connectivity to use the 3D Mapping Cloud's annotation database. \\
+D Mapping Cloud Annotations are shipped by installation but are not mandatory to operate the application.
 ===== Disk space =====
@@ Line 42: / Line 74: @@
 More attention is required to organize the huge volume of mapping resources.
-===== Data Storage and File Access =====
+===== Storage & File Access =====
 **Storage** \\
@@ Line 48: / Line 80: @@
 On importing Orbit will process all mapping data into performance-optimized resource files, which may need a bit more storage capacity. The optimized storage reduces other hardware requirements.
-**File Access and Disc** \\
+**File & Disc Access** \\
 Orbit requests result in direct file access, performance is particularly determined by the disc speed and disc access. \\
-Slow discs or slow connections will create a bottleneck.
+Slow discs or slow connections will create a bottleneck. SSD disks are nice to have.  \\
 **Big files** \\
@@ Line 68: / Line 100: @@
   * Viewing Purposes : \\ 64bit, dual core, intel i5 processor or equivalent, 4 GB memory, 2 USB3 connections. \\
   * Processing Purposes : \\ 64bit, quad core, Intel i7 or equivalent, 8GB Ram or more, 1TB hard disk, 2 or more USB 3 connections.  \\
-  * Heavy Duty Processing Purposes : \\ 64bit, quad core or more, Intel i7 or equivalent, 16 or 32GB Ram, 1TB SSD, 4 or more USB 3 connections.
+  * Minimal Heavy Duty Processing Purposes : \\ 64bit, quad core or more, Intel i9 or equivalent, 16 or 32GB Ram, 1TB SSD, 4 or more USB 3 connections.

Last modified:: 2024/03/04 15:50