Use the left controller to move the scene. When the left trigger is pulled, the scene will be 'stuck' to the controller and move with it until the trigger is released.

The right controller is used to move the cursor, line, or plane tools (which can move parts created by these tools as well).

Activate this by opening the VR and User defined input preferences, and check the User defined input box (see VR and user defined input Preferences ). A line used for picking will extend from the controller.

In order to move parts created by the cursor, line, or plane tool, the user needs to ensure that Interactive Toggle is active for the created part in question (see the Interactive session in How to Create Clip Planes for an example of interactively manipulating an EnSight part created using a tool).

When the cursor, line, or plane tools are visible, the user can point the controller at one of the tool control points (see Use the Cursor (Point) Tool, Use the Line Tool, or Use the Plane Tool ). When the picking line gets close to a tool control point, it will be drawn green. When the trigger is pulled, that control point is grabbed and the tool moves with the controller.

The main EnSight window will remain on the desktop. What appears on the head mounted display (HMD) is a duplicate of what is in the viewport, with the above setup. Sort of equivalent to going "full screen" in normal EnSight (in the HMD there is no graphical user interface, but just the viewport being drawn).

To select parts, create items, you will need to raise the goggles up, and perform that operation normally on your desktop. Again, the display in the HMD is just a duplicate rendering of the viewport.

No Right-click operations are available within the VR display.

Movements of the scene with the Mouse/Gamepad/Spacemouse (see SpaceNavigator and Gamepad) are reflected in both the HMD and the main desktop view within EnSight. However, movements of the HMD (look up/down, left/right, and left controller scene grab) are not replicated in main desktop view of EnSight.

The graphics card will need to render the image twice: on the HMD, and on the main EnSight window. For large models, this can lead to a slow performance. You can improve the performance by opening EnSight with the -bbox flag. This flag will make the main EnSight window visualize only the bounding boxes of the parts, instead of the parts, leading to a better performance. Note that the flag will not affect what the user sees with the VR Device itself.

Transparent surfaces do impart performance losses. Typically, this means that the draw in the HMD does not track as smoothly, and will sometimes drop the user back into the grey room. You can improve performance with transparency by reducing the amount of depth peels (Edit → Preferences → Performance).

Interactive streamlines and clip planes can be manipulated within the HMD. In larger models, the user may experience dropping back to the grey room when attempting to move the interactive tool, as EnSight can become overwhelmed with the streamline or clip calculation/update, and the VR device will loose signal, and place the user back in the grey room momentarily until the part is updated.

Playing through time is not recommended, as this continual disk i/o diversion will cause the HMD to drop back to the grey room. In this situation, we would suggest using Transient Flipbooks instead (where the transient domain is cached to memory), which allows the playback from memory (much quicker) than disk i/o.