Compatibility

All programs presented on this site cannot work independently but are plugins (that is, add-ons, extensions, or inserts) for engineering CAD programs.

System requirements

• • Windows 8 and older.

  • AutoCAD 2025 | BricsCAD V26 and newer requires Microsoft .NET 8.0. Older versions require Microsoft .NET Framework 4.8. 

Localization

• • Plugins are fully localized in English, Italian, German, Russian, Chinese (PRC), Spanish, French, and Turkish.  Source codes for self-localization into any language are publicly available.

  • The language is selected automatically depending on the language of AutoCAD|BricsCAD, but you can switch the plugin language. 

  • In all versions, the names of commands in the command line should be written in English. 

  • Articles and this website are translated into English and Russian only.

AutoCAD

• • A>V>C> plugins are compatible with AutoCAD 2013 and up. However, AutoCAD 2020 and later is highly recommended for stable performance.

  • Both x32 and x64 bit versions are supported. Starting with AutoCAD 2020, only x64 systems are supported.

  • Plugins can be used in "vertical" solutions such as AutoCAD Mechanical and AutoCAD Architecture. But plugins will only work with regular objects of pure AutoCAD; specific objects are not supported.

  • AutoCAD LT is not supported.

  • AutoCAD for Mac is not supported.

BricsCAD

• • All A>V>C> plugins work in BricsCAD PRO from V21 and newer.

  • For BricsCAD versions V21-V25, use the Avc_Plugin_Br21.dll library; for V26 and later, use the Avc_Plugin_Br26.dll library. The AVC_Starter_Br.dll plugin launcher will automatically select the correct library.

  • Both x32 and x64 bit versions are supported.

  • Requires at least a PRO version of BricsCAD that supports .NET plugins.

  • Plugins can be used in BricsCAD Mechanical and BIM. However, specific BricsCAD Mechanical and BIM objects are not supported. Their components are treated as unnamed blocks by A>V>C> programs.

  • BricsCAD for Linux and macOS is not supported.

  • The BricsCAD API does not know how to make flat shots from solids, so the plugin had to use a simplified algorithm for projecting solid edges. It has no way to determine the visibility of the edges and create the silhouettes of the surfaces.

  • BricsCAD does not have a system for automatically loading plugins from bundle folders. You will have to configure the launch of the plugin with the _AppLoad command or use the plugin installer.

  • For BricsCAD V26 and later, you may need to separately install .Net Core 8.0 or later.

  • It's possible to build a plugin for BricsCAD V19 and V20. Please send a request to avc.programming@gmail.com. This is a paid service.

ZWCad, GStarCAD

These popular Chinese programs support most of the APIs required by A>V>C> plugins. In theory, it is possible to port the plugins to these platforms, but doing so would require a massive amount of work in terms of conversion and debugging. You have the opportunity to become a sponsor for this development.

NanoCAD, IntelliCAD, ALCAD, CADian, Draftsight

A>V>C> plugins do not support these programs and other AutoCAD clones. The problem is that in these CADs, AutoCAD libraries for .NET development are not fully cloned, and BRep support is not implemented; that is, there is no way to analyze the structure of 3D solids. 

However, it is possible to convert some A>V>C> plugins that do not require deep penetration into the solid structures. Please submit your business proposals.

Draftsight is not 100% compatible with any AutoCAD plugins and requires you to create plugins from scratch.

MICROVELLUM, IMOS, Router-CIM, and other AutoCAD add-ons

These furniture programs, running on the AutoCAD engine, save models in DWG format as regular 3D solids, so these drawings are compatible with A>V>C> plugins. You will be able to create furniture models in these programs and then, for example, use A>V>C> to export the contours of parts to CAM programs for further programming of CNC machines. However, running plugins in the OEM version of AutoCAD is prohibited; you will need a separate full version of AutoCAD or BricsCAD to work with A>V>C> plugins.

Notes

• • As soon as a new version of AutoCAD/BricsCAD comes out, A>V>C> plugins immediately start porting to the new version. This usually takes about a month.

  • Porting to older versions of AutoCAD/BricsCAD is not possible.

  • Unfortunately, there are not enough testers to provide testing of A>V>C> plugins in all versions of AutoCAD and BricsCAD. Debugging of plugins is performed only on the latest versions of CAD. The set of test drawings is very limited. Therefore, it is critical that all users actively participate in testing A>V>C> programs and send drawings that programs cannot cope with to the technical support address avc.programming@gmail.com.

  • Help in catching bugs can bring you bonuses.