Setting up EnSight on a zSpace virtual reality display


Update 04-Nov-2016:

The current zSpace "300" machines no longer use VRPN for tracker operation, and a new SDK implementation is required. Currently, EnSight does not support the new SDK for the zSpace 300 device. Should this be of interest, please contact your local EnSight representative to discuss.


- Use EnSight 10.0.2h or later.

- There are two .bat files and two .dconfig files in the .zip file. The .bat files set two environment variables that tell EnSight to look for VRPN input, and then launch Ensight using one of the two  .dconfig files. dconfig is short for display config. There are hard-coded paths in the .bat files that will have to be changed using a text editor.

- zspace_detached.dconfig is for a system that has both a regular monitor and a zSpace display. It would be used if you want the whole  EnSight GUI on the regular display, and also show the 3D scene on the  zSpace device. This config is for a system with a 1280x1024 display on the left and the zSpace device on the right. The "displayorigin" line in the dconfig file can be edited to change the position. If the zSpace device is on the left of the monitor, use "displayorigin 0 0".

- zspace_gui.dconfig is for a system that only has the zSpace display. The head tracking and wand tracking would happen against the display in the main GUI.

- The zspace_detached configuration has more accurate tracking.

- InfiniteZ has a VRPN server available, but they do not install it or start it by default. Search for the current VRPN version. Currently:
Download the VRPN server, install it, and start it.

- After EnSight starts, it initially will not process stylus input from VRPN. It starts processing the input when you go to Edit -> Preferences -> User defined input, and check the "User defined input device" box. In the same box you can check "Macro panel interface" and "Part panel interface", to show the VR GUI.

- To make the Macro panel work, after you install EnSight and launch EnSight once, it will make a directory called $HOME/.ensight100. After you launch once, copy the macros directory in the attached .zip file to $HOME/.ensight100. So after the copy you should have
$HOME/.ensight100/macros/[a bunch of .macro, .play, and .define files]

The files in the macros directory control the position and layout of the VR GUI. If you want to tweak anything, the root file is a text file called hum.define. hum is short for "head's up macro".

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request