The following is a list of critical bugs or important limitations that users should be aware of which affect MicroSurvey CAD 2020. It is not intended as an exhaustive list of all issues.
Important Note: If you ever experience a crash when using MicroSurvey CAD, when you are asked if you would like to send an error report, please always select Yes to send the report. MicroSurvey and IntelliCAD programmers can use these error reports to help investigate and fix crashing problems that occur within the program, even if it is a problem that is not easily reproducible. Please note the crash reports are not actively monitored for technical support purposes.
Please contact technical support if you experience any problems.
Reported: March 4, 2019
Problem: When using the lot closure routine with Bearings and typing them in manually, it does not accept bearings between 359.5959 (S59°59'59"W) and 361 (S61°00'00W). Bearings past 361 work fine, as long as there is a . after the degree value. (Example, 365 will not work, but 365. or 365.0000 will)
Workaround: This issue is only when inputting values when the drawing is set to Bearings. If the user switches to Azimuths, then they can input their angles into the Lot Closure program. Then, you can switch back to Bearings, and finish the Lot Closure so that your report is in Bearings.
Status: This will be fixed in a future update.
Reported: October 31, 2019
Problem: Opening a drawing containing a point cloud may cause the program to crash.
Workaround: Open another drawing which does not contain a point cloud first, then open the desired drawing containing the point cloud.
Status: Fixed in Service Pack 1.
Reported: October 31, 2019
Problem: The AutoSave feature causes a message at the command history stating "0 files compressed". The AutoSave Drawing (.sv$ file) is saved correctly and is recoverable but its corresponding AutoSave Database (.mz$ file) does not contain a valid database and cannot be recovered.
Workaround: Several backup mechanisms are available: the MSBackup command will backup your drawing and database files to a backup folder on demand, these can be recovered; your dwg and msz files will be backed up (copied to .bak and .mbz files) every time you save your drawing, these can be recovered; if you absolutely need to recover the AutoSave files, the AutoSave Drawing (.sv$ file) can be recovered but the AutoSave Database (.mz$ file) cannot.
Status: Fixed in Service Pack 1.
Reported: November 1, 2019
Problem: The TEXTEDIT command is no longer available (replaced by DDEDIT), and double-clicking a DTEXT object does not allow the user to edit the text. Neither does selecting the text, right-clicking, and selecting "Edit Text".
Workaround: Add an alias for DDEDIT as "TEXTEDIT"; Type "CUI", then expand "ICAD" and "Aliases". Right-click in "Aliases" and select "Insert Alias", name the alias "TEXTEDIT", and in the properties for the alias on the right side of the dialog, add the "Command Name" DDEDIT.
Status: Fixed in Service Pack 1.
Reported: November 5, 2019
Problem: FieldGenius reports that DXF is corrupt when opening a project created by "Export FieldGenius Project" in MicroSurvey CAD 2020. A related error message may be reported by other software when trying to import a dxf as generated by the Leica iCON export utility.
Workaround: This routine is actually creating a dwg file but adding the extension dxf to the file. This is easy to fix: Before loading the file in the data collector open the dxf file inside the newly created project in MicroSurvey CAD and "Save as..." dxf. You will now be able to open the project.
Status: Fixed in Service Pack 1
Reported: March 18, 2020
Problem: Multi line text disappears or changes sizes when editing it. Sometimes program freezes while editing single line text with GRIPS on.
Workaround: This issue is due to a bug with the IntelliCAD engine on how it is handling text in the newer text editors. As a workaround, change the value for the MTEXTED variable to "oldeditor" and the TEXTED variable to "1". This will change the text editors to use the previous editing system.
Status: This has been confirmed fixed with a newer version of the CAD engine and will be fixed in a future update.
Brian Sloman
Comments