How to run Enscape in virtual and remote environments

Summary:

• Chaos Product Manager Mehmet Gündüz explains how to access Enscape from anywhere using virtual machines (VMs) and remote workstations, even though official support is limited to local machines.
• Workflows include remote desktop applications, VMs with dedicated or shared GPUs, and high-performance office workstations accessed remotely.
• A smooth experience depends on using reliable remote software, stable network connections, dedicated GPU passthrough, and consistent display setups.
• Recommendations include: testing setups with trial licenses, using updated versions (4.11+), and validating performance with medium-sized projects before team rollout.

As remote and hybrid workflows become more common in the AEC industry, many users are exploring how to access Enscape running on virtual machines (VMs) or powerful office hardware through remote access regardless of physical location.

This document outlines what these technologies are, what setups we have tested internally, and our general guidance for achieving a usable, stable, and efficient Enscape experience, despite not officially supporting these environments.

Important disclaimer:
Enscape is officially supported only when installed and run on local machines that meet our system requirements. This guide reflects the results of internal testing and industry feedback as of August 2025. Hardware configurations, virtualization technologies, and Enscape behavior may evolve. Please treat this document as a snapshot in time, not a future-proof reference.

Table of contents

1. What is a remote desktop application?
2. What is a virtual machine?
3. What is a workstation with remote access?
4. Key considerations for a reliable experience
5. Hardware recommendations
6. Tested Enscape setups in virtual and remote environments

Understanding the environments

1. What is a remote desktop application?

A remote desktop app allows you to control a computer (usually located elsewhere) from your own device. The remote computer streams its screen to your device and receives input from your mouse and keyboard. This approach is often used to access office PCs from home or while traveling.

2. What is a virtual machine (VM)?

A virtual machine is a computing environment that runs on shared or dedicated hardware using a hypervisor. VMs can be hosted in cloud platforms like Azure, AWS, or Google Cloud, or on-premises, such as in the server rooms of architecture firms using platforms like Hyper-V or VMware.

These virtual systems can be configured with either:

• Dedicated GPUs (entire GPU assigned), or
• Partitioned GPUs (a slice of GPU power allocated to each VM session)

Regardless of location, remote desktop software is required to access and interact with the VM. Once connected, users can run Enscape and CAD applications inside the VM as if it were a physical workstation.

3. What is a workstation with remote access?

A workstation with remote access refers to a high-performance desktop computer; usually located in an office, studio, or data room, that is accessed remotely using applications like Microsoft Remote Desktop (RDP), Parsec, or Citrix Workspace.

These workstations are typically equipped with powerful CPUs and GPUs (e.g., NVIDIA RTX 4080 or higher), fast storage, and direct access to local files and project networks. Instead of physically sitting in front of this machine, users can operate it from another location such as their home, a client site, or a field office by streaming its desktop to their own device.

It can deliver near-local performance if paired with the right software and a stable network. It is often more predictable than VM setups because there is no virtualization overhead or resource sharing.

Typical use cases in AEC:

• Architects connecting to their office machine from a MacBook or lower-spec laptop while traveling.
• Project managers reviewing walkthroughs or scenes without needing a full local installation of Enscape.
• Hybrid teams accessing centralized hardware to ensure consistent software licensing and asset storage.

Key considerations:

• Unlike VMs, remote access to a workstation does not require virtualization or hypervisors.
• Because the machine is dedicated to a single user session, hardware resources are not shared, reducing contention and improving predictability.

Key considerations for a reliable experience

Achieving a smooth experience with Enscape in remote or virtual setups depends on several interdependent factors.

1. Remote software

Different applications produce vastly different results. According to our internal tests, Microsoft Remote Desktop (RDP) and Parsec have both delivered good results under the right conditions. They provide stable navigation, effective control of the Enscape camera, and reliable display streaming when used with capable hardware and a strong network connection.

2. Display setup

Use a single monitor whenever possible. If multi-monitor use is required, keep resolution and alignment consistent across all screens.

3. Hardware configuration (GPU access)

Dedicated GPU (passthrough) is ideal. Shared GPUs often fail to launch Enscape or degrade performance.

4. Network speed and stability

• Performance depends not just on speed, but latency, packet loss etc.
• Use wired Ethernet where possible.
• Recommended: 50+ Mbps down/up and latency < 40 ms.

5. VPN and security layers

• VPNs can introduce throttling or block required ports.
• If allowed by policy, test with VPN disabled for benchmarking.
• Use Parsec or similar tools that prioritize low-latency streaming and are known to perform reliably even under secured network conditions.

6. Software version

Enscape 4.11 and newer includes fixes and optimizations for remote access and display handling. We strongly recommend updating to at least version 4.11 for all remote use.

Hardware recommendations

These are baseline and recommended specifications (2025):

Notes:

• In shared or virtual environments, these specs must be guaranteed per user session, not shared across multiple VMs or sessions.
• Lower-tier configurations (e.g., 16 GB RAM, 8 vCPUs, older GPUs) may technically run Enscape, but performance will vary and is not recommended for production workflows.

Final notes

• In feedback rounds conducted with IT administrators from architecture and design firms, a common concern was raised: Running CAD and visualization software in virtual machines is often seen as overly complex and cost-prohibitive, primarily due to the challenges of configuration and the additional licensing costs associated with virtualized environments.
• This is a critical factor for firms considering VMs as part of their long-term infrastructure.
• Install Enscape directly on the host machine (whether workstation or VM).
• Start Enscape after establishing your remote session. Launching it beforehand can result in camera and display bugs.
• Test before rollout: We recommend using trial licenses to validate behavior in your setup before expanding it to teams.
• Validate performance with medium-size projects. During our tests, we performed the following tasks:
  1. Starting Enscape from the CAD environment
  2. Navigating scenes and walkthroughs
  3. Adding and editing assets
  4. Changing materials
  5. Switching views and projections
  6. Measuring frame rates and checking responsiveness

We do not officially support virtual environments

Enscape is officially supported only on physical local machines that meet our system requirements. Our Support Team cannot assist with the following in remote/virtual environments:

• GPU passthrough or partitioning issues
• Remote display alignment problems
• VPN-related restrictions
• Streaming or encoding lag
• Performance issues due to internet or cloud host limitations

This guide is provided for information purposes only and does not represent a formal support commitment.

Appendix: Tested Enscape setups in virtual and remote environments

Below is a detailed summary of environments we tested internally. The results reflect real-world performance using Enscape 4.2 to Enscape 4.7 versions.

Note: Tests included launching Enscape, navigating through medium-sized projects, placing assets, switching views, adjusting materials, and observing responsiveness under multi-display setups.

Explore the latest version of Enscape, or if you haven't already experienced the ease and speed of real-time visualization, try it today for free.