This article highlights some considerations when using Vision4D from a remote machine over RDP.
This article highlights some considerations when using Vision4D from a remote machine over RDP.
Generally, it is best to use Vision4D on a system that is local to the data storage. Since data storage of very large datasets can be challenging on standard desktop or laptop systems a common workaround is to use a high-end imaging workstation with lots of storage, and to access this workstation using Remote Desktop Protocol (RDP). However, these configurations have historically been problematic with regard to GPU utilization. This article aims to clarify some of those issues and provide solutions.
The use of Vision4D over RDP is also limited by the licensing system we use.
As of 2020, soft licenses are delivered with RDP enabled by default.
Licenses purchased earlier may be upgraded to enable RDP under certain circumstances. If you have a soft license but RDP is disabled, please contact support using the link at the top of this page.
If you have a Network license, hard or soft, RDP is on by default.
If you have a hard local license, these licenses can only be configured for RDP for arivis Vision4D 3.4 or above. Older versions of Vision4D do not support RDP with a hard local key. If RDP is necessary, please contact your local sales representative to discuss replacing your hard key for a soft key or any other options that might work for you.
While the configurations tested above work, remote desktop GPU support is mostly outside of arivis' control. However, there are a few things we recommend: