Release Notes for CaraVR 2.1v4

Release Date

January 2019

Qualified Operating Systems

Nuke Version	Platform
11.3v1, or above	10.12 (Sierra) 10.13 (High Sierra)	Windows 7 Windows 10	CentOS 6 CentOS 7

Nuke Version

Platform

Mac OS X/macOS

Windows (64-bit)

Linux (64-bit)

11.3v1, or above

10.12 (Sierra)

10.13 (High Sierra)

Windows 7

Windows 10

CentOS 6

CentOS 7

Other operating systems may work, but have not been fully tested. See the Nuke Online Help for more information on supported GPUs and other hardware recommendations.

New Features

This release of CaraVR is exclusively for Nuke 11.3 for all platforms. The functionality of all nodes remains the same as previous releases of CaraVR, which should still be used for older releases of Nuke.

Feature Enhancements

There are no feature enhancements in this release.

Bug Fixes

• ID 370526 - Linux only: Headsets did not work as expected when the Nuke Viewer was set to full screen.

• ID 378062 - C_Tracker: Selecting a user track and clicking the Clear All button after tracking caused Nuke to crash.

• ID 378582 - C_Tracker: Selecting a user track and clicking the Clear All button caused the track to behave unpredictably when retracking the same point.

Known Issues and Workarounds

Installation

Windows only: Delete the CaraVR version folder, if it exists, prior to installation. The folder resides here:

C:\Program Files\Common Files\Nuke\<nuke_version>\plugins\<caravr_verion>\

For example, if you're installing a new version of CaraVR 2.1, delete this folder before installation:

C:\Program Files\Common Files\Nuke\<nuke_version>\plugins\2.1\

Stitching

• Projections in Nuke's 3D system expect rectilinear footage, which is inherently limited to a 180° field of view. As a result, C_CameraSolver's manual 3D workflow, which relies on projections, only projects the central 180° from material shot on wider lenses, such as the Nokia OZO.

• ID 232523 - C_ColourMatcher: Gains control keyframes for multiple cameras in the Curve Editor are not recognized as keyframes.

Preview

• If you have a version of both CaraVR 1 and CaraVR 2 installed on the same machine, any headsets connected to the machine will not work and may cause Nuke to crash.

• Many facilities lock down USB access for security, which impacts Oculus Rift support. Some customers found that authorizing devices using a udev rule allowed them to use the DK2 on both CentOS 6 and CentOS 7, while still blocking USB storage devices. Thanks to Digital Domain for the following example:

ACTION!="add", GOTO="deauthorize_end"

SUBSYSTEM!="usb", GOTO="deauthorize_end"

TEST!="authorized", GOTO="deauthorize_end"

## make hubs deauthorize all devices by default

TEST=="authorized_default", ATTR{authorized_default}="0", GOTO="deauthorize_end"

## whitelist specific devices

ENV{ID_VENDOR_ID}=="2833", ATTR{authorized}="1", MODE="0777"

LABEL="deauthorize_end"

Windows Only

• We recommend using version 1.0.0 of the StarVR SDK for monitor output to the StarVR DK3 headset. Other versions of the SDK may work, but have not been fully tested.

• INFO and DEBUG messages are displayed incorrectly in the command prompt on some installations.

• Although CaraVR supports both SteamVR (OpenVR) and the Oculus Runtime for the Oculus Rift headset, we recommend selecting only one during a single session. Switching between the two outputs can cause the Oculus Rift to render black frames with the current version of SteamVR.

If you require both SDKs on your machine, please set the FN_CARA_VRCOMPOSITOR_QUIT environment variable to 1, which forces SteamVR to restart when you switch between outputs.

• If you're using a headset on multi-GPU machines, ensure that the device is connected to the GPU that handles the monitor output not the internal computation.

• When using the Oculus Rift CV1, we recommend using the official Oculus Rift SDK rather than SteamVR.

We recommend using the OculusVR Runtime instead of SteamVR wherever possible, as SteamVR is currently less stable for CaraVR operations.

Note: Closing SteamVR while Nuke is running with an HMD as an active Viewer causes Nuke to close. To avoid this, save and close Nuke before closing SteamVR.

• The monitor out plug-in routinely notifies about the health and safety implications of use of the Oculus headset. This is a function of the SDK and in newer versions (such as the one we employ) cannot be suppressed or shortened.

Linux Only

• HTC Vive headsets do not currently support lens distortion.

• When using the Oculus Rift CV1 on Linux, be aware that:

• Unlike the Oculus DK2, the CV1 displays black until you turn it on inside Nuke's Viewer settings.

• The CV1 does not appear in the list of available screens in Gnome/Kde, it is displayed with the supported devices in Monitor Output.

• When you initially turn on Monitor Output, all available monitors display black for a few seconds as the OS adjusts to the new configuration.

• The CV1 remains on until you close Nuke, which causes all available monitors to display black for a few seconds as the OS adjusts to the new configuration.

• When using the HTC Vive on Linux, be aware that:

• Under Centos 7, powering the headset through a USB 3 port can cause Nuke to become unresponsive.

As a workaround, power the headset through a USB 2 port instead.

• Installing a newer version of OpenHMD may clash with the one shipped with CaraVR. If you encounter problems with the HTC Vive, try uninstalling the newer version of OpenHMD.

• On some installations, the viewport on the headset doesn't cover the full screen, so you can still see the desktop background. You can work around this issue by moving the mouse pointer onto the headset screen and double clicking the Viewport.

• On some installations, you may need to open the NVIDIA Control Panel and enable the HMD as a second monitor so that Nuke can use it.

macOS/Mac OS X Only

• On Mac OS X, with the EoL official Oculus SDK installed, the monitor out plug-in cannot open the device as the SDK locks it. Possible workarounds include uninstalling the SDK, or preventing the OVRServer running at startup, using the launchctl load/unload commands (you can read about the specifics and implications of working with Mac OS X launchd here).

Miscellaneous

• Nuke Write nodes, when writing multi-view .exr files, only write out the set of channels present in the first view for all the other views. For example, if you write out the C_Stitcher’s output, because there’s only rgba in the rendered main view, the individual camera views do not output their vector channels.

To work around this, insert a vector channelset in the first view, even if it contains no data, using the AddChannels node.

• ID 309986 - Frame Server: Rendering 360 stitches through the Frame Server occasionally renders duplicate frames.