The following is a list of critical bugs or important limitations that users should be aware of which affect MicroSurvey CAD 2022. 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 16, 2022
Problem: Single-seat USB license or floating SOLO license no longer skips License Options dialog
Workaround: Press Available licenses, pick the available license then press Run.
Status: Will be fixed in a future update.
Reported: December 28, 2021
Problem: The user sees the error message "No points to process ()" when attempting to export a range of points in ASCII format. This happens because a prompt in the command line to specify point ranges is suppressed.
Workaround: Once you identify this issue, there is a simple alternative. Open the Active Coordinate Editor and export an ASCII file using the method shown at 03:31 in this movie.
Status: Will be fixed in a future update.
Reported: Dec 03, 2021
Problem: Intermittent display of error code 998 for command failures and registration errors.
Solution: Remove NVIDIA drive.
Reported: July 7, 2021
Problem: Entering a Network Floating License results in "There was a Problem Activating the License"
Solution: This was resolved by releasing a new installation to take the place of the June 2021 release, and the June 2021 release was removed from the downloads page. Please check Help | About MicroSurvey CAD. If your installation Date is June 2021 please uninstall and reinstall with using the July 7 release.
Reported: Sept 02, 2021
Problem: reactors don't start if you run a command too quickly in a new drawing
Workaround: Wait for the new drawing is completely started and the command line stops loading commands before type in any command in the command bar.
Status: Will be fixed in a future update.
Reported: July 30, 2021
Problem: Transfer Between Drawings does not work. Error Message: _ms_start_transferError while extracting file (File Name).msj\ch.dat
_Error opening coordinate database: 70
Workaround: This problem only occurs when drawings are opened using the Start Page or the File | Open menu. If you open the drawing using Project Manager the function works properly.
Status: Will be fixed in a future update.
Reported: July 15, 2021
Problem: Opening MSCAD prompts error Message: the code execution cannot proceed because MSVCP110.dll was not found, Reinstalling the program may fix this problem
Workaround: This problem is related to the windows 10 update KB5004237 associated with Visual C++, install the redistributable file will fix it.
https://www.microsoft.com/en-au/download/confirmation.aspx?id=30679
Status: Will be fixed in a future update.
Reported: October 28, 2020
Problem: When exporting from an imperial (International Feet or US Survey Feet) project to shapefile, the projection file is written as metric. This units mismatch is not accepted by some GIS programs, such as Google Earth or QGIS, wherein the projection file units are used to assume the units for the entire shapefile, making the shapefile appear to have incorrect units.
Workaround: The .prj (projection) file is an optional file in the shapefile. In imperial projects, uncheck the checkbox to write projection data and import the shapefile into a GIS project that has had the coordinate system manually set. The remainder of the shapefile data is correctly written in the appropriate imperial units.
If you must have a .prj file as part of the shapefile, you can modify the exported shapefile in a text editor manually, converting the projection units and noting the units and conversion factor in the file, as described in the following online article from ESRI: https://support.esri.com/en/technical-article/000001897. Most projection details are available online at epsg.io or georepository.com, so you may be able to simply input the projection details as written there, ensuring units and conversion factor to metric are noted as described in the ESRI article.
Status: Partially fixed in MicroSurvey CAD 2021 Hotfix. Coordinate systems with units matching project units will now be exported as expected. Will fully fix in a future update.
Reported: January 15, 2022
Problem: Images are not shown in Print or Model space, but image itself is still there.
Workaround: This problem is related to the CAD engine. As a workaround, use the 2021 version to get Prints completed until the hotfix is released.
Status: Will be fixed in a future update.
Reported: October 9, 2020
Problem: When inserting some blocks using insert command or Automap, an error "Duplicate Record name" is displayed and insertion fails.
Workaround: The issue is caused by the *IPN_INTERNAL layer which MSCAD always creates in order to display IPNs. In some cases, when the block has the layer (which is normal with MSCAD) this issue arises. If you have a non-MicroSurvey CAD program you can remove the *IPN_INTERNAL layer from the block, purge the destination drawing, and then reinsert. 1. Open the block in MSCAD. 2. _WBLOCK. 3. Configure the output path and file name. 4. Set insertion units to "undefined" 5. Select all visible elements of the block and select "OK." This will create a new version of the block without the *IPN_INTERNAL layer. Replace your old version of the block with this one.
Status: Will be fixed in a future update.
Jeran Hopfe
Comments