Read through our frequently asked questions below

Build My System

Known issues questions

Issue Version Workaround Status
Plug-in Gait units for forces, moments and powers in the c3d file does not match units displayed in Nexus. Pre 2.10 Nexus displays the Plug-in Gait units as:

  • Forces – N/kg
  • Moments – N.mm/kg
  • Power – W/kg

Plug-in Gait outputs generated by Nexus are normalized to the subject’s body mass, and their values are stored in the .c3d file as such. Therefore, the units in the .c3d file metadata should be divided by kg for these outputs (i.e. N/kg, N.mm/kg, W/kg).


Plug-in in Gait Documentation updated from Nexus 2.10 (https://docs.vicon.com/display/Nexus210/Plug-in+Gait+output+specification#PluginGaitoutputspecification-Jointkinetics)

   Copy a link to this question.
Issue Version Workaround Status
After completing dynamic wand wave it is possible for the Set Origin operation to fail. This is rare, but for those who experience the problem, it will be consistent. 2.10.3 The only way to get it to work again is to close Nexus down and reopen. Solved

Resolved in Nexus 2.11.0


Nexus performance issue when there was a large number of log messages. 2.10.1 Confirmed log workaround in Nexus 2.10.1:

  1. Right-click on the Log tab, then click Show Advanced Log.
  2. Right-click in the Log window, then click Show Categories.
  3. Set Global to Off.
  4. At this point you can clear the log and hide the categories again if you wish.

Note that this will disable all log messages, both in the app and in the log file.

If you want to keep the log messages:

  • Roll back to Nexus 2.9.3. If you want to use Blue Trident sensors, you will require Nexus 2.10.x.

Resolved in Nexus 2.10.2


GetDeviceChannel returns force plate outputs as an action force in a z-down coordinate system, compared to a reaction in a z-up system as stored in the C3D file. 2.10.1 Perform the conversion after requesting the value: rotate the force and moment outputs by 180 degrees about the y-axis, and then negate all components: this is equivalent to simply negating the y-component. This applies to both force and moment outputs. Scheduled to be resolved
PC blue screen when connected digitally to Kistler force plates due to Kistler digital plug-in 2.6.1 With Nexus open:

  1. On the System tab, select Local Vicon System.
  2. In the Properties section, select Show Advance.
  3. Reduce the Buffer Reserve from 1.0 to = 0.5.

   Copy a link to this question.
Issue Version Workaround Status
The Blue Trident firmware for the Capture.U app is set so that when a trial is stopped, the sensor goes into sleep mode to save power. The sensor resets the calibration in all capture modes when you stop capture. 1.2 and 1.3 None. To ensure precise calibration, we recommend that you follow the calibration procedure at the start of every trial. Instructions on how to calibrate the IMUs can be found here: https://docs.vicon.com/display/IMU/Calibrate+IMUs Open
If you repeatedly enter and exit AR Visualization mode by tapping Home or exiting the app, the Capture.U app may stop. 1.1 None. If the app remains unresponsive on relaunch, restart the iOS device and flush the Bluetooth. Open

   Copy a link to this question.
Datastream SDK
Issue Version Workaround Status
Native MATLAB integration no longer supported 1.10 Native MATLAB integration has been replaced by .NET as Mathsworks support the use of .NET directly in MATLAB (https://uk.mathworks.com/help/matlab/using-net-libraries-in-matlab.html). To make use of Datastream SDK 1.10, update legacy MATLAB scripts to .NET. To continue using native MATLAB integration, refer to support in Datastream SDK 1.9. Solved

   Copy a link to this question.