Although the Cloud application runs ZTV calculations and other actions on managed cloud infrastructure, the local device still requires sufficient memory, a fast SSD, and a mid-range processor for its own tasks.

System Resources

On Windows 10/11 systems, a browser with multiple tabs and background programmes typically uses 6-8 GB of RAM. Under heavier load, usage can increase to 10–14 GB. Devices with limited resources may struggle, resulting in slower performance across the system.

To support stable use of the Cloud application alongside other work software, the following specifications are recommended:

Optimal

• Windows 10/11 64-bit or macOS
• Apple Silicon (M2 or newer)*, Intel Core i5 (11th gen or newer, 4+ cores) or AMD Ryzen 5 (5000 series or newer, 6 cores)
• 16 GB or more DDR4 (dual-channel preferably)
• ≥ 256 GB NVMe SSD (PCIe 3.0 or newer)

*M1 MacBooks handle Cloud tasks reliably, though newer models deliver better performance.

Beyond hardware: understanding Cloud-based applications

Meeting local system requirements alone does not guarantee a smooth experience. Cloud streaming also depends heavily on network conditions, as the application relies on a continuous, real-time connection to remote servers.

Cloud access provides flexibility, allowing VU.CITY 3D to be used without a high-end workstation. However, connection quality has a direct impact on responsiveness and stability. A common misconception is that high download speeds alone ensure good cloud performance. In practice, consistency matters more than raw speed.

Network stability over speed

Speed tests measure how much data can be transferred per second, but they don’t indicate connection stability. Even with high speeds, cloud streaming will struggle if your connection frequently drops or fluctuates. Cloud applications require a steady, uninterrupted data flow - brief interruptions, packet loss, or high latency can cause lag or disconnections.

Multiple devices affect performance

Your internet connection is shared across all devices on your network. If multiple users are streaming or running bandwidth-heavy applications, it can impact performance, regardless of your internet speed.

Router quality and network hardware

Many users overlook the importance of their router. In office or enterprise environments, network settings, firewalls, or VPNs managed by IT can also affect performance. Older or low-end routers may struggle with cloud streaming, especially when managing multiple devices. To improve stability, use a modern router with bandwidth management and prioritisation features (Wi-Fi 6 or at least Wi-Fi 5), or switch to a wired Ethernet connection.

Latency and packet loss impact performance

Unlike locally installed applications, cloud-based apps rely on real-time communication with a remote server. If your latency (ping) is high or your connection suffers from packet loss, the app may feel unresponsive. This is why an otherwise “fast” connection can still result in poor performance.

Best practices for Cloud streaming

For the best experience with VU.CITY Cloud, follow these recommendations:

• Consult your IT department if you’re in a managed network environment, as network restrictions may affect performance.
• Use a wired Ethernet connection whenever possible to minimise instability.
• Reduce network congestion by limiting other bandwidth-heavy activities while using the app.
• Check your router’s capabilities and upgrade if necessary.
• Restart your modem and router periodically to refresh your connection.
• Monitor latency and packet loss, not just speed, using network diagnostic tools.
  
  

Alternative: running VU.CITY locally

If cloud streaming isn’t delivering a smooth experience, consider installing VU.CITY on your desktop. When running locally, the app only connects to the hub for saving and loading data, significantly reducing reliance on a stable internet connection. This is a great alternative for users experiencing network-related issues.

While cloud access offers flexibility, network conditions can impact performance. If needed, running the app locally remains a solid alternative for a seamless experience.