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.
Requirements for Nexus 2.10
Note the following requirements for Nexus 2.10.
For information on graphics cards, see Graphics processors for Nexus.
Operating systems for Nexus 2.10
Nexus 2.10 is supported under the following operating system:
- Microsoft Windows 10, 64-bit (this is the Vicon-recommended OS): Compatible with and fully supported. Installation, software operation and required third-party drivers tested.
Although Nexus may install and function under other Microsoft Windows operating systems, Vicon does not support or recommend this.
Basler video cameras and Nexus 2.10
If Basler digital cameras will be connected to Nexus 2.10, 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 Basler GigE cameras under Windows 10.
MATLAB and Nexus 2.10
If you are planning to use MATLAB with Nexus 2.10, ensure that, in addition to installing MATLAB, you install the .Net Framework version 4.5 or later.
ProCalc and Nexus 2.10
To run ProCalc with Vicon Nexus 2.10, you must install ProCalc 1.2.1 or later.
Vicon IMUs and Nexus 2.10
To update IMU firmware for Nexus 2.10, use Vicon Capture.U Desktop. For information, see the Vicon Capture.U User Guide.
Systems supported for Nexus 2
Before you install Vicon Nexus 2.10, note the following limitations on supported systems:
- Nexus captures data only from Vicon systems (including Vicon Vero and Vicon Vue, Vicon Vantage, Vicon Bonita, Vicon T?Series, and MX+ and MX cameras and units).
- Nexus 2.10 does not support connection to the Reference Video System (Nexus Slave application).
This section describes functionality that is dependent upon the version of Vicon Nexus that is being upgraded:
- Upgrading from Nexus 2.7 and earlier
- Upgrading from earlier versions of Nexus 2
- Upgrading from Nexus 1.x
Although data collected in Nexus 2.10 (ie, . c3d files) can be viewed in earlier releases of Nexus, you cannot reprocess this data (ie, . x2d with . xcp files) in releases earlier than 2.7.
Upgrading from Nexus 2.7 and earlier
Improvements to camera calibration that were provided by Nexus 2.7 have the following effects on compatibility of data between releases:
- Data collected in earlier releases of Nexus can be reprocessed in Nexus 2.10 because calibration (.xcp) files that were created in earlier releases are fully compatible with Nexus 2.10. Note that if you load a calibration (.xcp) file that was created in an earlier release of Nexus into Nexus 2.10 and save it, Nexus maintains its compatibility with earlier releases.
- You can use earlier releases of Nexus to view data that was collected in Nexus 2.10 (that is, you can open Nexus 2.10 .c3d files in Nexus 2.7 and earlier).
- However, calibration (.xcp) files that are created in Nexus 2.10 are not backward-compatible, that is, they cannot be read by releases of Nexus earlier than 2.7, and loading will fail if attempted.
Upgrading from earlier versions of Nexus 2
If you are upgrading from a previous version of Nexus 2, during installation a dialog box gives you the option of adding the Auto Intelligent Gap Fill button and/or the Add to Quick Report button to your Nexus toolbar. For more information on these features, see Automatically fill gaps in trial data in the Vicon Nexus User Guide and Quick Reports in the Vicon Nexus Reference Guide . To add the additional button(s) to your toolbar, click Upgrade Files.
On first launch, Nexus 2.10 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.10 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.
Upgrading from Nexus 1.x
This section applies only to versions of Nexus that are earlier than 2.0.
Nexus 2.10 installs into its own folder, called Nexus2.10. If you already have Nexus 1.x installed, it will remain installed alongside the new Nexus installation.
On installation, Nexus 2.10 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.10.
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.10.
For more information on the installation and licensing process, see Installing and licensing Vicon Nexus .