TurboVNC 3.2

TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power. A Java-based VNC viewer is also available

Tags c vnc rdp remote-desktop 3d tightvnc cross-platform java
License Apache
State initial

Homepage Download

Recent Releases

3.205 Mar 2025 13:16 minor bugfix: ===. ### Significant changes relative to 3.2 beta1: 1. a regression introduced by 3.0.3 7 that, under rare circumstances if. Automatic desktop resizing was enabled, caused the viewer to deadlock while Resizing its window in response to a remote desktop size change. 3.2 beta1. ### Significant changes relative to 3.1.4: 1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib. Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC 3.1.x, this improves the encoding performance of the Lossless Tight + Zlib Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs. 2. Since all supported TurboVNC host platforms now contain new enough libraries. to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked Against the system-supplied versions of these libraries rather than statically Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11` CMake variables have been removed, and the build system now behaves as if those Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation And build against the system-supplied zlib implementation. 3. The TurboVNC Server now supports the DRI3 X extension when using open source. GPU drivers. This enables GPU acceleration in a TurboVNC session without VirtualGL, although the performance will be better with VirtualGL. Refer to The description of the `-drinode` option in the Xvnc man page for more details. 4. The default X startup script (`xstartup.turbovnc`) now throws an error. Rather than trying to execute xinitrc or twm, if a session desktop file for The default window manager cannot be found. 5. Configuration of the TurboVNC Viewer has been improved in the following. Ways: - Advanced param