Start a conversation

MicroSurvey inCAD 2017 Known Issues

Date Reported: December 18, 2009

Status: Confirmed (10.1.0)

Problem: MicroSurvey commands are not immediately added to the AutoCAD menus after install, until you open a drawing.

Solution: inCAD will always launch Project Manager on startup, and after a drawing is selected inCAD will load the MicroSurvey menus.

Date Reported: November 2, 2009

Status: Confirmed (10.1.0)

Problem: When running inCAD under Windows Vista or newer, the "What's This?" Help feature may not work.

Solution: If you wish to use the "What's This?" Help feature, you may need to download and install an update from Microsoft, because Windows Vista and newer does not ship with the WinHelp32 viewer. Please refer to the following Microsoft Knowledge Base article for more information. Please note, the main Help files will work without this update.

Date Reported: October 6, 2016

Status: Confirmed (10.0.0)

Problem: Computing an area using the FastArea command may preduce imprecise answers which may vary depending on your zoom level.

Cause The perimeter is determined using AutoCAD's Boundary Polyline command, which we discovered uses the displayed pixels to smooth the resulting polyline and eliminate small details around the perimeter that are not apparent at the current display level.

Workaround: Users are advised to verify their calculated areas using the "Calculate Area by Point Numbers" command.

Solution: The Fast Area command will be redesigned in a future update so as to not use AutoCAD's Boundary Polyline command for determining the boundary.

Date Reported: October 6, 2017

Status: Confirmed (17.0.0)

Problem: inCAD with Civil 3D can be unstable during certain routines that access the database, for example when opening up the Active Coordinate Editor to view the points database or when using the Single Point Editor to modify a point.

Solution: MicroSurvey will investigate and fix this for a future update.


Choose files or drag and drop files
Was this article helpful?
  1. Brian Sloman

  2. Posted
  3. Updated