disable opengl windows 10 remote desktop problem

The reason that GNOME 3.8+ does not work with OpenText Exceed onDemand (EoD) is unrelated to performance. In addition to compressing the display, the ETX proxy can also skip frames to reduce the bandwidth required for the remote display. The proxy can be installed on the same server as the 3D desktop to avoid flooding the network connection between the proxy and desktop host. Graphical issues, such as black icons and windows, can be caused by unsupported (non-Mesa) graphics drivers.Įxceed TurboX (ETX) includes a server-side proxy that compresses the X11 traffic before sending it across the network. Slow performance and high network usage are a result of rendering methods that are not designed for remote connections (sending uncompressed X11 bitmaps over the network every frame). Failure may occur due to the desktop using OpenGL capabilities that are not available remotely. GNOME 3 was designed to work with direct OpenGL rendering, and may either fail or perform poorly over a remote connection. Network traffic between the X server and X client (GNOME 3 host) will be very high.The user may see black icons and windows (or other graphical issues).Connecting to GNOME 3 desktop with OpenText Exceed™ or OpenText Exceed TurboX may result in the following behaviors: OpenText Exceed onDemand™ cannot launch GNOME 3 desktop.Ģ.

GNOME 3.8+ is an OpenGL-based 3D window manager that comes as the default window manager in RHEL7 and CentOS7. Current selection is theGlobal website.ģD Desktop Support This article discusses the current status of GNOME 3 support for the Exceed product line.

Disable opengl windows 10 remote desktop problem