When the system frame rate is set above 80Hz, if you enable Preview mode, no preview is displayed for Vicon Vantage cameras (the Camera view is blank).

To use Preview mode with Vantage cameras, select a system frame rate below 80Hz.

When you right-click the Devices node on the System Resources pane, Noraxon is not available in the Add Digital Device menu.

When you install the Noraxon plug-in (ViconInterfaceForNoraxon - v1.0.2.1.msi), change the installation path to C:\Users\Public\Documents\Vicon\Nexus2.x\DigitalDevices\

Analog output component names saved into a C3D file are truncated if <OuputName>.<ComponentName> is longer that 16 characters.

Ensure that the compound name is 16 characters or fewer.

.NET is turned off by default on Microsoft Windows 8, which stops ProEclipse running.

Enable .NET framework 3.5 on Windows 8 machines. To do this, open the Control Panel, click Programs and then click Programs and Features. Click Turn Windows features on or off and select the Microsoft .NET Framework 3.5.1 check the box. You can do this before or after installing Nexus.

MATLAB/Nexus integration will not operate on Windows 7 unless the .NET framework 4.5 is installed. Attempting to run MATLAB pipeline operations reports:

Error Run MatLab Operation Error using NET.addAssembly

Install .NET framework 4.5 from microsoft.com.

Noraxon Telymyo DTS device halts camera and analog data delivery when Noraxon devices are housed/not charged.

Digital devices now have an Enabled parameter in their Properties pane. To prevent a given manufacturer's plugin from holding up the rest of Nexus, clear Enabled for ALL devices from that manufacturer.

Unable to run legacy Static Gait Model under Japanese Windows.

Log entry reads:

No parameter file found

The legacy Plug in Gait model does not support international character sets. Instead of using the legacy Plug-in Gait model, use the native Nexus 2 replacement gait model (found under Data Processing pipeline operations: Process Static Plug-in Gait Model and Process Dynamic Plug-in Gait Model).

Export c3d at the end of a pipeline does not clear the trial and leaves the trial with a dirty flag (*).

The Export C3D operation does not write out the subjects associated with the trial. To remove the dirty flag on a trial, save the entire trial, which saves all associated files (x2d, xcp, etc), using the Save Trial - C3D + VSK operation.

Video capture duration can be limited directly after deletion from SSD storage.

After deleting your video files, wait a few seconds before starting your next capture. This is because some Solid State Drives require a few seconds to recover full Write speed after file deletion.

Spaces in variable names can cause BodyLanguage to fail.

When creating subject parameters for use in BodyLanguage modeling, use underscores instead of spaces.

When deleting or renaming trials through the Eclipse interface, temporary video files remain on disk and still appear in the Transfer/Transcode tool. This can lead to confusion or overwriting of newly captured trial data if new trials are captured using the names of deleted trials.

Regularly transcode and delete raw video.

Nexus can suffer many problems if Eclipse databases are created in locations that are Read-only. These problems range from data silently failing to save to crashes.

NEVER create Eclipse databases in locations that require administrator privileges to read or write.

Starting a capture very soon after a change to the system frame rate, or a resynchronization, can result in erratic capture behavior (failure or dropped frames).

Avoid starting captures soon after changing the hardware setup.

PAL or NTSC camcorders are included in Active Wand camera calibration if the MX system is set to run at the same standard (i.e. PAL or NTSC).

Before performing active wand camera calibration, disable the camcorders.

Running the Butterworth Filter (Analog Devices) operation on a force plate may result in erratic noise in the Center of Pressure (CoP) output during periods where there is little or no force being measured. This is because the CoP is derived by dividing Moment by Force, which produces chaotic results when these numbers are approximately zero.

Only filter the force plate data over regions of time where a force is registered.