PCD-147567 - Fixed I++ errors for Technology Server 1.x in the self-centering code.PCD-147370 - Fixed an issue where the Mesh Colormap scale did not appear in the Graphic Display window and the Text and CAD, CAD Only, and CADOnly Landscape report templates.PCD-146558 - Fixed an issue where it wasn't possible to calculate the form error for laser cylinder features extracted from a COP command.PCD-146494 - It is now again possible to execute directly-measured laser features offline.PCD-146476 - Fixed an issue that caused the layout toolbar to always appear after a toolbar was customized.PCD-146366, PCD-147443 - The auto wrist toggle got enabled when linear open scan commands were edited.PCD-146159 - The trapeze that represents the working area of the laser sensor is no longer shown for features that are extracted from a COP command.PCD-145264 - Fixed an issue for the Leica LMF interface AT960 tracker where PC-DMIS 2018 R2 Release Notes 2.PCD-140952 - Fixed an issue with the displayed datum bonus value when the datum was shifted to its limit.
#PC DMIS 2018 DOWNLOAD PATCH#
PCD-140115 - When a new patch scan is created, all points taken for previous patch scan are deleted so as to create patch scan at new location.PCD-138257 - Fixed an issue where PC-DMIS stopped working when executing a measurement routine that already contained extra instances of commands (extra instances of commands are created by executing the measurement routine with commands such as Loops, Goto, etc.).PCD-135514 - Ring light intensity migration will now only be attempted for features where the top and bottom lights are not in use.It fixes the issue of the tip not patterned. PCD-128933 - Improved the logic to determine the appropriate tip when it is part of block for the copy and Paste With Pattern.This alternative way to calculate COP/CAD cross sections could give better results when the medium distance between the cloud and the CAD model is relevant in the section zone, and the nominal section is strongly curved in this zone (distance is greater than 2 or 3 mm). It is possible to obtain better results by changing the registry entry's value to 0 and recreating the cross section so that it uses this new setting. By default, the PointcloudOperator CrossSectionCopCadCrossSectionDrivenB圜ad registry entry is set to 1. PCD-125813 - When the pointcloud is not well aligned to the CAD model, the resulting measured cross section (yellow polyline) may not be computed as expected and may produce the incorrect shape.Here's the list of bug fixes for anyone who is interested: Looks like the second service pack for 2018 R2 is good to go.