Tracker legacy documentation:

Vicon Tracker banner

For information on known issues in each point release of Vicon Tracker 3, see:

Known issues in Vicon Tracker 3.9

  • Setting the camera calibration parameter Calibration Type to Calibration Refinement has the same effect as selecting Full Calibration.

Known issues in Vicon Tracker 3.8

  • Setting the camera calibration parameter Calibration Type to Calibration Refinement has the same effect as selecting Full Calibration.

Known issues in Vicon Tracker 3.7

None.

Known issues in Vicon Tracker 3.6

  • If you use variations on upper/lower case, you can create multiple object presets with the same name (eg, Test and test).
  • When using only one camera with an Apex device, the Apex is displayed intermittently.

Known issues in Vicon Tracker 3.5

  • Recalibrating with multiple cameras selected re-calibrates only one camera.
  • Hang on startup with Vue/Bonita video connected.
  • Crash on exit if Tracker is opened on a machine already running Nexus.
  • Tracker hangs if started without a previously used dongle attached.
  • Capture/Calibration is stopped if camera errors occur.
  • Creation of objects cannot be undone.

Known issues in Vicon Tracker 3.4

  • CSV export doesn’t export unlabeled reconstructions.
  • Tracker hangs if started without a previously used dongle attached.
  • Capture/Calibration is stopped if camera errors occur.
  • Creation of objects cannot be undone.

Known issues in Vicon Tracker 3.3

 None.

  • Need to click Yes to use license for each feature when use trial license dialog is displayed.
  • Subject list drop down does not automatically resize.
  • Cannot add Apex if Apex has been added in a second system file.
  • Calibration fails if one or more cameras are blank.

Known issues in Vicon Tracker 3.1

IssueExplanation/Workaround
When the system frame rate is set above 80Hz, if you enable Preview mode, no preview is displayed for Vantage cameras (the Camera view is blank).To use Preview mode for Vantage cameras, select a system frame rate below 80Hz. To be addressed in a future release. T-Series Preview mode continues to work as expected.
Object creation cannot be undone.

You cannot use Undo (CTRL+Z) after creating an object.
To remove the object, delete it instead of using Undo.

Rotation causes translation for an object aligned to global axes.In some circumstances (e.g, when a small object is very distant from the origin) rotation along a particular axis, e.g, the X axis, for an object that is aligned to the global axes, causes a significant translation along the Y axis.
Tracker fits absent Apex to objects in the capture volumeIf an Apex is present in a capture volume containing an object such as an Active Wand or a rigid body plate, and you add the Apex to the System tree and then remove the Apex from the capture volume, Tracker may fit the absent Apex to an object in the capture volume.
To avoid this issue, whenever you are not using the Apex in the capture volume, turn it off.
Cameras set to different strobe intensities cause Apex or Active wand to sync incorrectly with the camera system

When using either an Apex or an Active Wand, unwanted effects (for example, jitter in tracking) are caused by using cameras at different strobe intensities or if one or more disabled cameras is present in the capture volume.
To avoid this issue, ensure all cameras are set to the same strobe intensity and that there are no disabled cameras in the volume.

Known issues in Vicon Tracker 3.0

IssueExplanation/Workaround
Object creation cannot be undone.

You cannot use Undo (CTRL+Z) after creating an object.
To remove the object, delete it instead of using Undo.

Auto masking cannot be limited to a subset of all cameras.If you select a subset of all the available cameras and click Start in the Create Camera Masks section of the Calibrate tab, all camera views are displayed and all are masked.
Rotation causes translation for an object aligned to global axes.In some circumstances (e.g, when a small object is very distant from the origin) rotation along a particular axis, e.g, the X axis, for an object that is aligned to the global axes, causes a significant translation along the Y axis.
Apex jitter caused by switching between Continuous and Strobe mode.

With an Apex set to its default LED Intensity of 2 in Tracker, or if it is set to 3, in situations where the Apex switches between being synchronized with the cameras and not being synchronized, it alternates between Strobe mode (synchronized) and Continuous mode (not synchronized). This causes tracking to jitter.
To avoid this effect, in the General section of the Properties pane, either change the LED Intensity setting to 1 or select Continuous Mode. Note that if you select Continuous Mode, power consumption increases, causing the battery to be depleted more quickly.

Tracker fits absent Apex to objects in the capture volume

If an Apex is present in a capture volume containing an object such as an Active Wand or a rigid body plate, and you add the Apex to the System tree and then remove the Apex from the capture volume, Tracker may fit the absent Apex to an object in the capture volume.
To avoid this issue, whenever you are not using the Apex in the capture volume, turn it off.

Cameras set to different strobe intensities cause Apex or Active wand to sync incorrectly with the camera system.

When using either an Apex or an Active Wand, unwanted effects (for example, jitter in tracking) are caused by using cameras at different strobe intensities or if one or more disabled cameras is present in the capture volume.
To avoid this issue, ensure all cameras are set to the same strobe intensity and that there are no disabled cameras in the volume.

Apex is not compatible with VR cameras.To maximize battery life, the Apex does not emit both frequencies of light that are required to support Visible Red (VR) cameras, so the Apex cannot be used in systems with VR strobes.
Analog data from Apex cuts out

If an Apex is left running with Graph view displayed in Tracker, after a minimum period of about 10 minutes, the analog data may cut out and the graph view shows no Apex data.
If this issue occurs, perform a manual resync.