1Overview
infrADAC BCAD mirrors the public ACAD command catalogue but compiles against BricsCAD/Teigha APIs. The installer targets a selected local BricsCAD profile, adds a tagged on_doc_load.lsp startup block and deploys the partial CUIX.
The BCAD ribbon is missing, the wrong BricsCAD profile loads, or a Teigha/drawing behaviour needs to be separated from AutoCAD instructions.
2Product differences
The task is shared where possible, but selection, interface integration and model operations follow the host shown below.
This article describes the active product: BricsCAD owns geometry, selection, CUIX and Teigha database operations.
3BCAD ownership boundaries
The command names are shared, but BricsCAD owns the local profile and Teigha model runtime.
| Feature or choice | Current behaviour |
|---|---|
| Loader | A tagged on_doc_load.lsp block loads the BCAD assembly for the selected local profile.Different BricsCAD profiles can have different startup results. |
| CUIX | The BCAD implementation extracts and loads the infrADAC partial CUIX and refreshes the workspace.The command surface remains familiar to ACAD users. |
| Shared task set | ACAD and BCAD use the same user-facing command names for equivalent workflows.Users can follow the same task guide while applying the host-specific selection and profile notes. |
| Entity API | Geometry, XData, blocks and transactions use Teigha/BricsCAD types.Behaviour is equivalent without assuming Autodesk runtime details. |
4Start and verify BCAD
Confirm the local profile, loader and CUIX before investigating a shared task.
Confirm the selected local profile
Startup integration is profile-specific.
- Start BricsCAD with the intended user/profile.
- Allow
on_doc_load.lspto load the BCAD assembly. - Accept the disclaimer and open Settings to confirm the plugin is active.
Check the CUIX ribbon
BCAD uses the shared ribbon concept with BricsCAD APIs.
- Open the infrADAC ribbon tab.
- Run
ADACCUIXto add, reset or remove it when necessary. - Restart BricsCAD after repairing startup/profile integration.
Use the shared command set
ACAD and BCAD public command names are kept in parity.
- Follow the same task articles for project, asset, surface, audit and export commands.
- Apply BCAD host notes where selection, entities or integration differ.
- Use BCAD-specific logs when a Teigha operation fails.
Repair or retarget
Use the installer/updater rather than copying profile fragments.
- Open Modify Installation.
- Select BricsCAD and browse to the correct install or local profile/locale folder.
- Use Transfer to change the active registered target; understand Copy Install does not change the active loader target.
5Before you begin
- Use BricsCAD Pro at a version accepted by the current installer.
- Identify the exact local
V*x64and locale profile used by BricsCAD. - Close BricsCAD before Modify, software update or uninstall operations.
6Troubleshooting
The plugin works in one BricsCAD profile but not another
Use Modify Installation to target the active local profile/locale, or add the tagged loader and CUIX through supported installer repair rather than manual copy.
The ribbon resets after a workspace change
Run ADACCUIX Reset in the new active workspace and confirm the partial menu is loaded.
Uninstall leaves a loader block
The current full uninstaller does not explicitly remove the BricsCAD on_doc_load.lsp block. Remove only the infrADAC-tagged block or contact support; preserve unrelated startup content.
7Developer notes
These notes explain the technical boundary behind the visible product behaviour.
| Feature or choice | Current behaviour |
|---|---|
| Shared command layer | BCAD retains the same public command catalogue as ACAD while its implementation is compiled against BricsCAD and Teigha database types.Task names stay consistent without pretending the two CAD runtimes are identical. |
| Profile-scoped loading | The tagged on_doc_load.lsp entry and partial CUIX belong to the selected BricsCAD local profile and locale.A second BricsCAD profile can legitimately load without infrADAC until it is configured. |
| Geometry parity | Shared geometry and XData services use host adapters around BricsCAD entities and transactions.Small display or entity-class differences can be host behaviour even when the resulting ADAC data is equivalent. |