The following are frequently asked questions and answers from new inCAD users...
Q) What versions of AutoCAD are supported?
A) MicroSurvey inCAD 2015 will run inside AutoCAD 2014/2015, AutoCAD Civil 3D 2014/2015, and AutoCAD Map 3D 2014/2015. AutoCAD Architecture 2014/2015, AutoCAD Map 3D Enterprise 2014/2015, and AutoCAD Civil 3D Land Desktop Companion 2014/2015 should also work but are untested. AutoCAD LT cannot be used with inCAD. AutoCAD OEM is included with MicroSurvey embeddedCAD.
Q) What operating systems are supported?
A) MicroSurvey inCAD 2015 has the same system requirements as the AutoCAD software it is running in. AutoCAD 2014 requires Windows XP, Windows 7, or Windows 8/8.1 (32-bit or 64-bit). AutoCAD 2015 requires Windows 7 or Windows 8/8.1 (32-bit or 64-bit). Further system requirement details AutoCAD, Civil 3D, or Map 3D are available on the Autodesk website.
Q) Are MicroSurvey inCAD 2015 and MicroSurvey inCAD 2014 (or earlier) project files compatible with each other?
A) Yes, inCAD 2015, inCAD 2014, and inCAD 2013 projects are completely forwards- and backwards-compatible, so projects from one can be opened directly with the other. Projects from previous inCAD versions (2012 or earlier) are completely forward-compatible and can be opened directly with inCAD 2015, but inCAD 2015 projects must be saved as an appropriate previous format in order to open them with inCAD 2010-2012. Please see the MicroSurvey inCAD 2015 Upgrade Notes article here for additional details.
Q) Are MicroSurvey inCAD 2015 and MicroSurvey CAD 2015 project files compatible with each other?
A) Yes, inCAD 2015 and MicroSurvey CAD 2015 projects are completely cross-compatible with each other. Both programs use the latest AutoCAD DWG 2013 drawing format by default.
Q) Are MicroSurvey inCAD 2015 and MicroSurvey embeddedCAD 2015 project files compatible with each other?
A) Yes, inCAD 2015 and embeddedCAD 2015 projects are completely cross-compatible with each other. Both programs use the latest AutoCAD DWG 2013 drawing format by default.
Brian Sloman
Comments