Vicon Nexus 2.5 is a point release that provides features and enhancements in addition to those that were included since Nexus 2.0.
For links to descriptions of the features and enhancements that are specific to Nexus 2.5, see Vicon Nexus 2.5 new features and functions.
For a description of the other features and enhancements that have been released since Nexus 2.0, see the PDF What's New in Vicon Nexus 2.4.
For a description of the other features and enhancements that have been released since Nexus 2.0, see the PDF What's New in Nexus 2.4.
For information about requirements and systems supported for this version of Nexus, see:
The Vicon motion capture system and the Nexus software, manufactured by Vicon Motion Systems Limited, have been tested prior to shipment and meet the metrological requirements as detailed in the Medical devices directive.
Nexus 2.5 is compatible with and fully supported under the Microsoft Windows 7 operating system. Installation, software operation and required third-party drivers have been tested under this operating system. Vicon recommends the Windows 7, 64-bit operating system for use with Nexus 2.5. Nexus 2.5 has also undergone limited testing under the Windows 10 operating system. Although Vicon Nexus may install and function under other Microsoft Windows operating systems, this is not officially supported or recommended by Vicon.
If Basler digital cameras will be connected to Nexus 2.5, ensure you have updated to the Basler Pylon5 SDK and drivers (v5.0.0), which are available from the Vicon website.
If you are using an Intel i340, i350 or i210 network card, when you install the drivers, select the option for Filter drivers, not Performance drivers.
The Pylon5 driver supports:
If you are planning to use MATLAB with Nexus 2.5, ensure that, in addition to installing MATLAB, you install the
.Net Framework version 4.5.
Before you install Vicon Nexus 2.5, note the following limitations on supported systems:
This section describes functionality that is dependent upon the version of Vicon Nexus that is being upgraded:
This section applies only to versions of Nexus that are earlier than 2.0.
Nexus 2.5 installs into its own folder, called Nexus2.5. If you already have Nexus 1.x installed, it will remain installed alongside the new Nexus installation.
On installation, Nexus 2.5 automatically scans for Nexus 1.x files, displays a list of any older files that it finds, and provides an automated system for importing these into Nexus 2.5.
This process copies all the old files and converts the copies, ensuring that original files are not moved, altered, or destroyed.
Custom pipelines are not copied from earlier versions of Nexus, so if you want to use your old pipelines, copy them from the following Vicon product installation folder (by default in C:\Program Files (x86)\Vicon or C:\Program Files\Vicon):
and paste them to the following location in the Vicon production installation folder (by default in C:\Program Files (x86)\Vicon or C:\Program Files\Vicon):
They will then be available in the Legacy pipeline operations in Nexus 2.5.
For more information on the installation and licensing process, see Installing and licensing Vicon Nexus.
If you are upgrading from a previous version of Nexus 2, during installation you are given the option of adding the Auto Intelligent Gap Fill button to your Nexus toolbar. For more information on this feature, see Automated gap-filling.
When you install Nexus 2.5, a dialog box similar to the following is displayed.
To add the Auto Intelligent Gap Fill button to your toolbar, click Upgrade Files.
On first launch, Nexus 2.5 scans the installation directories of earlier versions of Nexus 2 and offers to automatically transfer custom objects that it finds.
If you click Import Files, Nexus 2.5 copies custom calibration objects from earlier versions of Nexus (2.0 and later) to the Public Documents folder (eg C:\Users\Public\Documents\Vicon\Nexus2.x\CalibrationObjects).
When you create new custom calibration objects, ensure you save them into this folder (not to the Nexus installation folder), so that they are available to future versions of Nexus.