Additional Nexus reference PDFs:

Nexus legacy documentation:

This information is for Vicon Nexus 2.14. For up-to-date help, see the latest Nexus documentation.

Vicon Nexus banner

Vicon Nexus 2.14 is a point release that provides features and enhancements in addition to those that were included in earlier releases of Nexus 2. For more information, see Nexus 2.14 new features and improvements.

Nexus is 64-bit only

Nexus is 64-bit only. In most cases, you should upgrade to the latest version of Nexus to benefit from the latest functionality. Before you upgrade, note the following points:

VDDs (Vicon digital device files)

  • 64-bit VDDs When you install the plug-in for your device, ensure that the 64-bit version of the VDD is correctly installed to the folder:
  • 32-bit VDDs If you use a VDD (Vicon digital device file) that does not have a 64-bit version, continue to use Nexus 2.12.# until the vendor of your VDD releases a 64-bit version of the VDD. For information about the availability of the 64-bit version of the VDD, please contact the vendor.

OpenGL solution for non-NVIDIA graphics processors

The OpenGL solution for non-NVIDIA graphics processors is supported for Nexus 2.14 (see Graphics processors for Nexus).

Note that a different version of the DLL is required for Nexus 2.13 and 2.14 than for earlier releases of Nexus.

Update to ProEclipse

Nexus 2.14 provides an updated version of ProEclipse so that the path to Vicon Polygon now uses the Program Files (x86) folder when called from a 64-bit application.

Nexus 2.14 new features and changes

Nexus 2.14 provides the following new and changed features:

Use more FLIR video cameras in a Nexus system

Nexus 2.14 offers the ability to use up to eight FLIR cameras in your Nexus system, enabling you to use post-processing with Theia.

Note that, to take advantage of this new functionality, you must use an advanced PC. For details, contact Vicon Support.

Improvements to using Python with Nexus

A new Python tab is now available in the Communications pane. Here, you can set the path to your Python installation, and can conveniently run a script without having to include it in a pipeline operation.

By default the Run Python Operation pipeline operation uses the path to the Python script from the Python tab as its default location, but you can change it on a per-operation basis if required.

For more information, see Run a Python script from within Nexus in the Vicon Nexus Reference Guide.

Using Python 2 with Nexus 2.14
The sample scripts that are installed with Nexus are compatible with Python 3. If you want to run Python 2 scripts, either the machine you are using must have Python2 in its PATH, or if you are using both Python 2 and Python 3,  create .bat files to configure the Python environment that is needed to run the required script.

Updates to CGM2

CGM2 has been updated to 4.2 and now uses Python 3 – both are installed with Nexus.

To make it easier to find the CGM2 pipeline operations, including the new operations for event detection and Kalman gap-filling, they are now displayed in their own section in the Available Operations list in the Pipeline Tools pane.

For information about using CGM2 with Nexus, see Modeling with CGM2 in the Vicon Nexus Reference Guide.

Run an executable file from within Nexus

Nexus 2.14 enables you to run an executable file (written in compiled languages such as C++ or C#) from a Nexus pipeline operation. You can use this feature to speed up or update processing and produce a more automated workflow, for example:

  • To quickly run an application you've written that takes filter-related parameters as command line options by connecting to Nexus using the offline SDK, loading the data, filtering using the provided filter parameters, and updating the model output data in Nexus.


  • For legacy VPIs that you want to continue to use in the latest 64-bit version of Nexus, you could port them to use the offline SDK rather than the VPI interface.

For information on how to run the Run External Application pipeline operation, which enables you to do this, see Run an executable from a Nexus pipeline operation in the Vicon Nexus Reference Guide.

Make pipelines read-only

You can now create a read-only folder that contains pipelines to be used within Nexus so that users of your Nexus system can use a standardized set of pipelines. This enables you to to create pipelines that all users of Nexus can access, but that are protected from editing. It is particularly useful if you need to meet MDR requirements for running standardized pipelines that must not be altered by the user.

For more information, see Make pipelines read-only in the Vicon Nexus Reference Guide.