Running Enscape in Virtual and Remote Environments

This page provies infromation on running Enscape in virtual and remote environments.

Overview

As the architecture, engineering, and construction (AEC) industry embraces remote and hybrid workflows, firms increasingly deploy high-performance visualization tools like Enscape in virtualized or remote-access environments.

This shift enables design professionals to access powerful rendering capabilities from anywhere, on any device – without compromising performance.

This guide provides IT professionals, BIM managers, and power users with a comprehensive framework for achieving a stable and performant Enscape experience in these advanced setups.

Understanding the Deployment Models

Choosing the right deployment model is the foundation for success. The key difference between direct remote access and full virtualization directly impacts performance, cost, and complexity.

Remote Desktop vs. Virtual Machine (VM)

Model 1: Remote Access to a Physical Workstation

• Connect remotely to a high-performance workstation (e.g., RTX 4080) located in the office or data center.
• The local device acts only as a terminal, streaming the remote desktop.
• Performance is typically more predictable, as hardware is dedicated to a single user and not shared.

Model 2: Virtual Machines (VMs)

• Operate within a self-contained VM hosted on shared or dedicated hardware.
• GPU resources are assigned either as:
  • Dedicated GPU (Passthrough) – ideal for Enscape.
  • Partitioned GPU (vGPU) – shared and less reliable for real-time rendering.
• Common platforms: Azure, AWS, VMware, or Hyper-V.

Enscape and CAD tools are accessed remotely through RDP, Parsec, or other virtual desktop clients.

Primary Use Cases and Considerations

Common AEC scenarios that benefit from these models include:

• Flexible access for designers: Run Enscape from home or on the go via lightweight devices.
• Simplified project reviews: Stakeholders can explore scenes without local installations.
• Centralized resources: Ensures consistent versions, licenses, and asset paths.

Critical Configuration Factors for Success

Performance in remote environments depends on the synergy of multiple configuration layers — not one single factor.

Remote Access Software

• Best-performing tools: Microsoft Remote Desktop (RDP) and Parsec.
• Both offer smooth camera control, stable navigation, and minimal input lag.

GPU Configuration

• Use Dedicated GPU passthrough for predictable performance.
• Avoid shared or partitioned GPUs — they often cause Enscape to fail to launch or perform poorly.

Network Performance

For stable streaming and real-time responsiveness:

• Connection: Wired Ethernet (preferred over Wi-Fi)
• Bandwidth: ≥ 50 Mbps (up/down)
• Latency: ≤ 40 ms

Security Layers and VPNs

• VPNs may throttle bandwidth or block ports.
• If permitted, test Enscape with VPN temporarily disabled to benchmark baseline performance.

Display and Software Versions

• Use a single monitor when possible for remote sessions.
• If using multiple monitors, match resolution and alignment.
• Run Enscape 4.11 or newer for the latest remote display optimizations.

Recommended Hardware Specifications

Reliable Enscape performance in remote environments requires dedicated per-user resources.

Implementation Best Practices and Strategic Considerations

Best Practices

1. Installation Target:
   Install Enscape on the host workstation or VM, not on the local client device.
2. Launch Sequence:
   Always connect remotely before launching the CAD software and Enscape.
3. Pre-Rollout Validation:
   Conduct a pilot test with trial licenses. Validate navigation, material changes, and frame rates to set internal performance benchmarks.

Strategic Consideration: Cost and Complexity

Full VM deployments are often seen as complex and cost-intensive, due to:

• High GPU instance pricing in cloud environments.
• Additional CAD and OS licensing costs.
• Increased IT management overhead.

Evaluate the total cost of ownership (TCO) carefully before adopting full virtualization at scale.

Summary of Internal Test Results

Enscape was tested across multiple virtual and remote configurations to identify viable solutions and common pitfalls.

Key Takeaways

• Best performers: Parsec and Microsoft RDP
• Ideal setup: Dedicated GPU passthrough (Hyper-V + RTX A4000)
• Use with caution: VMware Blast, ScreenConnect
• Setup failures: Typically caused by missing GPU passthrough configuration, not hardware limitations