EnSight does not support the running of the client on one machine and setting the system display environment back to a different machine. Not all of the features of OpenGL are supported on all platforms in this mode which can conflict with EnSight's graphics. It is intended that you actually run the client from the console of the client machine.

If you run the client on a remote machine and display back, you will see the following warning displayed on the console machine:

------------------------------------------------------------------------

Warning: EnSight has detected indirect OpenGL rendering. This could be caused by remote display using X11, by an incorrect setting of the DISPLAY environment variable, or by a bad driver installation.

When running using indirect OpenGL, you will notice a performance degradation and loss of some rendering features. If you are running over a network we strongly recommend that you install EnSight directly on the client machine. EnSight is a client/server application, and you can run the EnSight server on your remote machine.

------------------------------------------------------------------------

One way is to run the client on your local machine with a manual connection:

ensight_client -cm (Linux)

ensight_client -cm (Windows)

and on the remote machine:

ensight_server -c clienthostname (Linux)

ensight_server -c clienthostname (Windows)

Another way is to run your client and to tell it to open a connection on a remote machine (default is ssh) as follows

ensight_client -c remotehostname (Linux)

ensight_client -c remotehostname (Windows)

Running one or multiple servers remotely incurs no cost as only the EnSight client requires a license key.

And, of course the various VR combinations of display are valid.