Addressed issues

For information on the fixes included in each point release since the launch of Vicon Nexus 2.0, see:

     Nexus 2.2 solved issues

     Nexus 2.1.1 solved issues

     Nexus 2.1 solved issues

     Nexus 2.0 solved issues

Nexus 2.2 solved issues

Vicon Nexus 2.2 contains fixes for the following issues:

     Kinematic fill operation can now be performed on multiple segments. The All option works as expected.

     Export ASCII operation now exports the frame numbers for frames with no visible markers.

     Digital device plug-ins are now stored in a common location for all 2.x releases (C:\Users\Public\Documents\Vicon\Nexus2.x\DigitalDevices). Nexus prompts to upgrade the install location.

     New Nexus SDK command GetTrialRegionOfInterest(), which returns the cropped trial range.

     Removed components of an analog device no longer reappear after a save and reload.

     Device channel names no longer prepended by the output component names.

     SCoRE and SARA operations can now be run on subjects where marker names include an underscore character.

     Marker order now respected when saving the subject as a VST file.

     Default offline streaming rate increased to 120Hz. Option available from the timebar context menu to stream every frame.

     Events no longer generated from forceplates that are marked as invalid.

     X1D files with non-English characters are now supported.

     Labeling template builder assigns more appropriate joint location parameters to newly created joints.

     Nexus no longer becomes unresponsive when running the Calculate Gait Cycle Parameters operation.

     Head offset angle now calculated from the selected frame range

     Cross-plate strikes work correctly when segments are manually assigned to a footplate

     Crashes no longer occur where the Noraxon vdd attempts to write to a privileged location. VDDs are now stored in a common location that does not require elevated privileges.

Nexus 2.1.1 solved issues

Vicon Nexus 2.1.1 contains fixes for issues that were reported following the release of Nexus 2.1, including the following:

     SCoRE and SARA dynamic calculation operations now produce outputs.

     The issue of the cross-plate strikes option in the dynamic Plug-in Gait operation always combining data from plates if the foot strikes are manually assigned to a segment has been corrected. The Static Head Offset values are now calculated by the Plug-in Gait Static operation.

     The Run Python operation completes successfully, even if non default pathways contain scripts or required files.

     Focus now returns from ProEclipse data manager to Nexus.

     An issue related to OpenGL, which caused transparent subject items to be rendered in the wrong order, has been corrected.

     When running the Generate Gait Cycle Parameters operation, events for a previous trial are no longer used in calculations, even if the current trial has no event present.

     An update in the Plug-in Gait native operation prevents a small discrepancy that can occur in ankle moment when compared to the legacy Plug-in Gait operation.

     Updates to the Fill Gaps - Rigid Body pipeline operation prevent bad fill suggestions.

     An issue that affected processing when more than one instance of Nexus is open at the same time has been corrected.

     The Process Static Plug-in Gait Model operation now uses the First-Last frame range for calculating the static head offsets.

Nexus 2.1 solved issues

Vicon Nexus 2.1 contained 65 solved issues, including the following:

     There is no longer a difference in frame selection / filtering for analog sub-frames between PiG and Vicon Gait Model.

     The Labeling Template Builder does not now cause crashes on linking segments.

     Auto-correlate no longer creates double events with multiple forceplates.

     Markers that are Calibration only or Optional that had been removed and were not present in trial are no longer displayed.

     Bounding boxes are now available for Polygon use.

     A MKR file is exported to the session folder.

     The Aim camera feature no longer crashes Nexus.

     The issue that SCORE could crash with multiple subjects has been fixed.

     Attaching a different VST to a labeled subject no longer un-labels the subject.

     F7 now works after a loading a trial.

     Ctrl+S now saves as expected.

     The issue of potential latency when using Dikablis eye tracker has been corrected.

     A marker added to a segment now contains scalable parameters.

     Nexus no longer becomes unresponsive when running Filter Model Outputs - Butterworth pipeline.

     Running a BodyLanguage model without data loaded no longer crashes Nexus.

     In the Plug-in Gait model, the Reaction Reference Frame now defaults to Distal instead of to Proximal.

     Modeled markers are stored in the C3D in a more user-friendly format.

     Center of Pressure (CoP) coordinate frame output is now global instead of local.

Nexus 2.0 solved issues

The following issues were fixed in Nexus 2.0:

     Pausing a pipeline operation no longer causes a hang.

     Nexus AMTI force plate – When RAW data channels are captured, voltage is now correctly scaled.

     The presence of a Noraxon EMG digital device no longer causes a crash.

     The issue that the Start Capture button could be disabled for unconfigured videos, even when video cameras were disabled, has been corrected.

     When digital and analog devices are present, a device no longer goes missing if the devices arrive in a different order.

     Bonita Video camera masks are now retained correctly on restarting.

     Analog channel monitor threshold settings now load properly when a monitor is reloaded.

     If the classification, patient, or session name was in Japanese, then recording a trial no longer fails to create an x2d in the session folder.

     Static subject calibration does not now require you to look at the frame you were calibrating in order to run.

     Plug-in-Gait joint force and moment units indicate that they are normalized to body weight.

     Subject measurements are no longer incorrectly populated automatically, even when the previous dependent parameters are not cleared.

     The Graph pane no longer incorrectly switches to trajectory count during analog filtering operations.

     You can now delete a model when model outputs or generated trajectories are present.

     Docking/un-docking windows multiple times no longer results in a crash.

     View Lock: Lock function in camera view is now correctly saved as part of a view type definition.

     The presence of a dummy subject no longer causes monitor loading issues.

     The preferred segment angle format is now correctly stored in a view type definition.

     The issue that the Y axis for force plate graphs did not scale until the threshold value was broken has been corrected.

     Long captures no longer cause Nexus to crash.

     Selecting Remove Subject now removes model outputs.