BricsCAD FAQ.
Practical answers for CAD users.

Compatibility always depends on the combination of BricsCAD release and macOS version. Support for a new BricsCAD release does not automatically extend to older releases.

Compatibility in the captured overview

Apple Silicon: The source describes V27 as a Universal Binary containing native code for Intel (x86_64) and Apple Silicon (arm64).

Before upgrading macOS

1. Identify your installed BricsCAD major release.
2. Compare it with the intended operating system in the table.
3. Check your add-ons separately and back up your data.

This table reflects the source captured on 15 October 2026. It is not an exhaustive list of all older macOS releases. An unlisted combination is neither confirmed nor conclusively ruled out by this overview.

TAA stands for the US Trade Agreements Act. For certain US government purchases, the relevant question is whether a product was made or substantially transformed in the United States or an eligible designated country.

The captured manufacturer statement describes BricsCAD as TAA-compliant.

What does this mean for procurement?

• The statement concerns the named product, rather than automatically covering every combination of software, add-ons and services.
• If a procurement requires evidence, request documentation identifying the actual product and solution being supplied.
• This answer explains the manufacturer's statement; the requirements of the particular procurement must be assessed separately.

There is no special TAA switch that ordinary users need to enable when installing or operating BricsCAD.

BricsCAD Solution Build (BSB) is the OEM offering used to deliver specialized applications on the BricsCAD platform. In this context, an OEM vendor uses the CAD platform as the basis of its own solution.

How does it work?

The captured overview describes a capable CAD platform to which application developers add industry-specific functionality. Application developers, distribution partners and the platform provider participate in this solution model.

What does it mean for users?

• A BSB-based application can have its own product name and interface.
• Features, approved versions and deployment depend on that particular solution.
• The term BSB alone does not establish which add-ons or license levels the individual product supports.

When requesting installation or compatibility help, identify the actual OEM solution and its version. Instructions for an unmodified BricsCAD installation do not necessarily transfer directly to a specialized application.

LGS 2D and LGS 3D are software components for managing constraints between geometric elements. Constraints preserve relationships or dimensions as a model changes.

Intended use

Developers can embed the components in CAD, CAM or CAE software. They help an application maintain design intent rather than treating every line and surface as unrelated geometry.

Who needs this information?

Software developers and companies building technical applications. These components are not a general BricsCAD system variable or a package every CAD user must install for everyday work.

The source describes binary components for multiple platforms and architectures. Availability and approval for a new project must be checked against the actual component distribution. Component licensing also differs from an ordinary CAD end-user license.

BricsCAD separates installation information, user settings, major release and language. Different major releases and language editions can therefore maintain their own settings.

Important registry locations

Replace Vx with the actual installed release identifier and LanguageCode with a value such as en_US or de_DE. Some older installations include an architecture suffix in the release identifier.

Inspecting an entry

1. Close BricsCAD.
2. Open Registry Editor and locate the correct release and language branch.
3. Export the relevant branch as a backup before changing values.

HKEY_CURRENT_USER applies to the signed-in account. Changing it does not automatically change other users' settings. Use the keys actually present on the machine rather than assuming every example path exists.

The English article defines the language identifier as la_CO: two lowercase language letters, an underscore and two uppercase country letters. A matching locale subfolder beside bricscad.exe identifies the installed language. Use the actual key spelling on the machine; the source itself contains an inconsistent doubled underscore in one example.

VBA must match the BricsCAD edition, release and architecture. A missing runtime is a common reason why VBA macros cannot run.

BricsCAD V17 and later

1. Close BricsCAD.
2. Open the installation directory of the intended BricsCAD release.
3. Open its VBA subfolder.
4. Run BricsCAD-VBA-Runtime.exe and complete the installation.
5. Restart BricsCAD and test VBA or the affected macro.

The source identifies BricsCAD Pro as a VBA-capable edition. BricsCAD Lite does not provide the required VBA environment. Installing a runtime does not add a feature entitlement missing from the edition.

Older releases

• V14 to V16: The VBA support described in the source required the 32-bit edition.
• Earlier than V14: The source describes restrictions on installing VBA in trial mode.

These historical rules are not instructions for installing a current release. For third-party macros, also confirm the BricsCAD and VBA versions for which the application was developed.

If ordinary Citrix users receive an empty interface or references to the administrator's folders, BricsCAD may have been launched while the server was in installation mode.

Why does this happen?

The first launch initializes user paths. In installation mode, the terminal server can propagate those settings to other accounts. LocalRootFolder and RoamableRootFolder may then point to the administrator's profile instead of the signed-in user's profile.

Correct procedure

1. Install BricsCAD using the server's required installation mode.
2. Return the server to execution mode.
3. Only then launch BricsCAD to initialize user settings.
4. Test an ordinary account and confirm that support files and paths belong to that user.

Repairing an existing setup

An administrator should inspect the propagated Bricsys entries beneath HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Terminal Server\. The source describes clearing the relevant Bricsys subbranch before additional users sign in.

Back up the affected entries first and change only the identified Bricsys settings. Do not delete the entire Terminal Server registry branch.

For the English V26 example, the affected user settings are under HKEY_CURRENT_USER\Software\Bricsys\Bricscad\V26\en_US\Settings. An access error mentioning C:\Documents and Settings\ADMINISTRATOR is a strong clue that administrator paths were propagated.

default.cui stores interface customization, while default.pgp stores command aliases. BricsCAD creates user copies so personal changes can be maintained separately from program files.

Compare these settings

1. Enter LOCALROOTPREFIX and record the local root directory.
2. Check ROAMABLEROOTPREFIX for the roaming root directory.
3. Inspect SRCHPATH: the actual support directory must be discoverable there.
4. Confirm that default.cui and default.pgp exist in the intended location.

Typical Windows parent directories are %LOCALAPPDATA%\Bricsys\BricsCAD and %APPDATA%\Bricsys\BricsCAD, followed by release and language subfolders.

Restoring the files

Original resources are stored in the installation's UserDataCache folder. Missing root-folder settings or a changed VersionCustomizableFiles value can trigger copying again. Changing SRCHPATH alone does not disable that initialization process.

Before reinitializing: Back up existing user files. Replacing them with defaults may remove personal menus and aliases. After restarting, verify which file is actually being found: another file with the same name earlier in the search path may still take precedence.

English-installation examples

%LOCALAPPDATA%\Bricsys\BricsCAD\Vxx\en_US\
%APPDATA%\Bricsys\BricsCAD\Vxx\en_US\

Replace Vxx with the actual release folder. If a root-folder registry value is missing, the source describes recopying all support files. After an update, copying depends on the internal file version and newer cache files; a modified destination file can prompt before replacement.

Different major releases can be installed independently. For different builds of the same major release, a normal update usually replaces the existing program installation.

Retaining an earlier build

1. Close BricsCAD.
2. Copy its existing installation directory to a separate folder, for example alongside the original under C:\Program Files\Bricsys.
3. Give the copy a name identifying its actual build number.
4. Install the newer build into the normal installation directory.
5. Create and clearly label a shortcut to bricscad.exe in the copied directory.

The source describes a similar general approach for Linux and macOS.

Important distinction

Copying the program directory does not automatically create separate user profiles or additional license rights. When comparing builds, also check which configuration each launch uses.

An installer may refuse to downgrade the normal installation. The source then describes uninstalling the newer regular build before arranging the intended parallel installations. Keep backups of settings and custom files when planning such a change.

At startup, BricsCAD performs three separate tasks: resolve user directories, provide customizable files and initialize empty resource paths.

1. Resolve root folders

LocalRootFolder and RoamableRootFolder belong to the user registry branch for the release and language. If values are missing or the required folder structure is incomplete, BricsCAD can initialize its standard AppData locations.

2. Copy files from UserDataCache

This happens during initial setup and, where required, following updates using VersionCustomizableFiles.

3. Populate resource paths

Empty values such as PLOTSTYLEPATH, PLOTCFGPATH, TEMPLATEPATH and SRCHPATH are initialized from these locations.

Using custom locations: Create the expected subfolders first. The roaming support directory must contain files; the local root needs at least one subfolder. Otherwise the validation may replace your custom path with a default. Close BricsCAD and back up the configuration before editing registry values.

The English source uses HKCU\Software\Bricsys\BricsCAD\V26x64\en_US\Settings as an example. It also initializes empty DRAWINGPATH, BLOCKSPATH, RECENTPATH and XLOADPATH values from the user Documents location. Adapt the release identifier to the keys actually installed.

The captured article states that registration information survives a build update, including an update that first uninstalls the previous program version.

This concerns an update to the existing installation. It does not mean every customized support file remains unchanged: menus and command aliases have their own update process.

Before updating

1. Record the current release and build.
2. Back up your CUI, PGP and other customized support files.
3. After updating, check the license display and personal customizations.

If an ordinary build update unexpectedly requests activation, record the actual message. The general statement about preserved registration information does not by itself explain every activation problem.

BricsCAD creates installation and user data at different stages. This distinction matters for managed installations and terminal servers.

During installation

Program files go into the selected installation directory. Under HKEY_LOCAL_MACHINE\Software\Bricsys\Bricscad, the appropriate release and language branch contains values such as InstallDir and FullVersion. The source does not describe a fully initialized personal configuration under HKEY_CURRENT_USER at this stage.

On a user's first launch

BricsCAD initializes personal settings and copies customizable resources from UserDataCache.

SRCHPATH, PlotStylePath, PlotCfgPath and TemplatePath identify these resource locations. User settings belong to the release/language branch under HKEY_CURRENT_USER.

During updates

The installer updates the program directory and build information. Personal resource files undergo a separate version check. Inspect program and user directories separately when old menus or missing resources appear after an update.

Example user configuration branch

HKEY_CURRENT_USER\Software\Bricsys\Bricscad\VX[x]\en_US\Profiles\Default\Config

VX[x] is notation, not a literal folder name: substitute the release and any architecture suffix. The source describes storing expanded full paths rather than the symbolic root-folder expressions used in its explanations.

Multiple Linux installations may share render materials in /var/bricsys/RenderMaterials. A package manager can refuse an update if the new package replaces files already owned by an installed package.

Confirm the conflict first

1. Read the complete installation error.
2. Verify that it actually names files under /var/bricsys/RenderMaterials.
3. Identify the installed release and package format.

Use distribution-specific handling

For RPM-based systems, the source describes replacing the confirmed conflicting files:

sudo rpm -ivh --replacefiles BricsCAD-*.rpm

Use the intended package's actual filename rather than an ambiguous wildcard.

For Ubuntu, the captured source contains a questionable dpkg command syntax. It is not repeated here as a verified executable instruction. Have the appropriate package repair or installation procedure determined for your distribution.

Scope matters: Replacing files is an approach for the confirmed material-file conflict. It is not a general solution for unrelated package conflicts or missing dependencies.

Errors 25 or 27, or messages about creating, opening or writing a registry key, can indicate insufficient process privileges. The English article specifically identifies writes under HKEY_CLASSES_ROOT.

Why is an administrator account not enough?

Windows does not automatically elevate every application launched by an administrator. The license manager may therefore lack access to a protected registry area.

Procedure

1. Close BricsCAD.
2. Right-click its shortcut.
3. Select Run as administrator and approve the Windows prompt.
4. Open license management and enter the valid key again.
5. Close the elevated session and test a normal launch.

The source addresses Windows 8.1 and later. If the problem remains, capture the exact message and have the relevant permissions checked. A different activation error code can have a different cause.

If a failed computer no longer starts, its license cannot be deactivated through the normal BricsCAD interface. An emergency revocation of that activation may be needed to release its activation slot.

Information to prepare

• The affected license key.
• The old computer's identity and known host ID.
• Any available LIC file and the reason normal deactivation is impossible.
• A clear statement identifying other activations that must remain active.

Provide this information to the responsible license administrator or support contact. Revoking one machine's activation is different from removing every activation of a product.

Source limitation: This particular captured article states a limit of two revocations per key but does not include the complete procedure. This refers to the restricted-operation revocation described there, not a general claim that ordinary online deactivation is limited to two uses. No unsupported sequence of account menus is supplied here.

_SETLICENSELEVEL lets you select a lower feature level to evaluate whether an edition provides the commands your workflow needs.

Procedure

1. Save your work.
2. Enter _SETLICENSELEVEL at the command line.
3. Choose the level to evaluate and follow the prompts.
4. Exit and restart BricsCAD so the selected level takes effect.
5. Test the commands required for your work at that level.

A trial initially provides the full feature set. Without selecting a lower level, a trial can therefore make a smaller edition appear more capable than it is.

Changing the setting does not purchase a license or grant rights to a higher edition. Record the original level so you can restore the intended configuration after testing. The leading underscore invokes the English command name on localized installations where supported.

LicTool automates license operations for BricsCAD and Communicator. It is located in the installation directory and runs from a command prompt or terminal.

Requirements

On Windows, keep LicenseManager.dll and its dependencies alongside the tool. The source also specifies Microsoft Visual C++ 2015–2022 Redistributable, x64. macOS and Linux require the corresponding Dylib or SO dependencies. Copying the executable alone is insufficient.

Windows examples

.\lictool hostid
.\lictool activate -p=bricscad -k="YOUR-LICENSE-KEY"
.\lictool deactivate -p=bricscad
.\lictool store -s="RLMServer" -pt=5053 -f="C:\ProgramData\Bricsys\Server.lic"

On macOS and Linux use ./lictool instead of .\lictool.

Parameters

• -p: product, bricscad or communicator.
• -k: activation key.
• -f: destination file; optional for activation.
• -s and -pt: server and optional port.
• -l: existing license file used by a store copy operation.

Replace example values and quote paths. A complete destination path determines the output location; an existing destination file may be overwritten. Use deactivate only for the product activation you actually intend to release.

Copy a license file

.\lictool store -l="C:\LicenseSource\BricsCAD.lic" -f="C:\ProgramData\Bricsys\BricsCAD.lic"

Use real paths. Without -f during activation, the source uses the default license location and product filename. For store, omitting -pt produces a server reference without an explicit port. The Windows dependency examples include curl.dll, libcrypto.dll, libssl.dll and zlib.dll; macOS uses libLicenseManager.dylib and Linux libLicenseManager.so, with their dependencies.

The source recommends normally deactivating an online-activated local license before a Windows upgrade. The same key can then be used to activate again afterward.

Before upgrading Windows

1. Start BricsCAD on the original system.
2. Open Help → License Manager.
3. Select Manage License, then Deactivate.
4. Confirm success and retain the key for reactivation.
5. Upgrade Windows and activate BricsCAD again.

If Windows has already been upgraded

For V15 and later, the source normally expects no corresponding license problem. If an activation dialog appears, it describes entering the existing key again. V14 and older are associated with possible host-ID errors such as -4.

These are release-specific historical notes. The article treats manual activations separately from the online-deactivation recommendation. Do not reset host-ID files without establishing the actual cause.

A trial license file takes precedence over other license files. BricsCAD may therefore continue using trial mode even though a commercial key is available.

Identify the trial file

1. Close BricsCAD.
2. Open C:\ProgramData\Bricsys on Windows. ProgramData may be hidden.
3. Inspect the LIC files with a text editor.
4. Look for contract=Trial.
5. Back up the clearly identified trial file and remove only that file from the active license directory.

Use the commercial license

Start BricsCAD, add the commercial license using License Manager, and check the displayed license type and level.

Do not remove other files merely because of their names. Several products or activations may coexist on a machine. If the trial file cannot be identified confidently, have the contents checked by the license administrator first.

Error -4 can mean the rehostable host ID does not match the machine or cannot be read. These are local activation-binding data.

Locations in the source

Establish the cause

1. Were these files copied from another computer or drive?
2. Are the directories present and accessible to the intended user?
3. Did the error follow a failure or system restoration?

Further action

The source describes removing incorrect copied binding data and activating again. Corrupted data may additionally require revocation of the previous activation. Coordinate this with the license administrator and preserve the existing state before changing it.

Do not transfer these files between computers: They are machine-bound, and copying does not create a valid activation. This captured restricted-operation article mentions up to two revocations per key. If the error occurs only for another user account, inspect permissions before resetting an otherwise working activation.

In this context, 2002, 2009 and 2 mean the license file cannot be created or overwritten.

Windows

1. Check that C:\ProgramData\Bricsys exists and has the required user permissions.
2. Inspect the installation's shared Bricsys/Reprise license areas too.
3. Remove accidental read-only protection from the affected LIC and close editors holding it open.
4. Test activation once with Run as administrator. If it works only elevated, permission diagnosis is especially relevant.

Linux

The source identifies /var/bricsys as a required license directory and /var/tmp as a necessary temporary area. Archive-based installations may lack directories or permissions normally created by the installer.

macOS

Check /var/tmp/bricsys. /var commonly points to /private/var, so the two spellings may resolve to the same place.

Repair permissions deliberately

Have the required access granted to the affected users. Making every file writable by everyone is not a prerequisite for every repair. Record the full path in the error: it identifies the operation that actually failed.

Shared Windows locations listed by the source

C:\ProgramData\Bricsys
%SystemDrive%\Users\All Users\Reprise
%SystemDrive%\Users\All Users\Bricsys

Use the actual shared locations on your system. The Windows XP paths in the source are historical and should not replace current installation paths.

-3 identifies an expired license. The source focuses on a trial already used on the machine.

Trial behavior

The article describes one 30-day trial per major release and host ID. Reinstalling the same major release on the same computer does not restart that period.

Check in order

1. Establish whether you intend to use a trial or a commercial license.
2. Determine whether this major release's trial was already activated on the machine.
3. If it has never been used there, investigate the applicable manual activation procedure.
4. If a commercial license exists, check whether an old trial file is taking precedence.

Other license types

The general Reprise code -3 is not exclusive to trials. For another license type, inspect its actual validity period. The message, license type and major release matter alongside the numeric code.

If the administrator account works but an ordinary account reports -4 or -1, the cause may be access to shared license data.

Procedure

1. Confirm both accounts launch the same program installation and intend to use the same license.
2. Have the administrator inspect the shared Reprise and Bricsys directories.
3. On Windows, the source mentions locations under %SystemDrive%\Users\All Users, which may be reached through ProgramData locations depending on the installation.
4. For Linux/macOS, the article explicitly identifies /var/tmp/Reprise and /var/tmp/Bricsys. Case matters on case-sensitive filesystems; do not silently substitute differently capitalized directory names.
5. Grant the intended account the required access and test a normal launch.

Paths and capitalization can vary by system and release; inspect the locations actually used. Do not begin by revoking a working activation if the issue is simply another user's inability to read it.

The source associates -103 during activation with no usable internet connection. License management cannot complete the required online communication.

Check

1. Confirm that the computer is connected and the intended internet connection actually works.
2. Investigate whether a VPN or company configuration changes access.
3. Retry after connectivity is restored.
4. If it fails again, record the complete message and time.

Without online access

Use the manual/offline activation procedure for the applicable license type. Single-user and network licenses can use different workflows. Prepare the key and complete host ID.

This particular article does not supply the full offline sequence. Do not substitute copied local host-ID files from another machine. Activation must identify the actual intended computer.

In the described environment, -153 concerns the rehostable local host-ID data. Inspect the full error alongside existing activations.

Relevant directories

• /var/bricsys
• /var/tmp/bricsys
• On macOS, potentially /Library/Application Support/reprise

Controlled procedure

1. Close BricsCAD and activation dialogs.
2. Record the existing license files, permissions and machine assignment.
3. Have the administrator check whether binding data already exist, are damaged or are inaccessible.
4. If reinitialization is required, back up and modify only the identified directories as part of a planned reactivation.
5. Retry; if online activation still fails, investigate the appropriate manual procedure.

Why not use broad deletion commands?

The original includes wide deletion patterns and unrestricted permissions that may affect more than an individual repair requires. The specific locations above support targeted diagnosis. Existing activation data should not be removed blindly merely to attempt activation again.

The key has reached its allowed number of activations. An additional machine requires a released activation slot.

If the previous machine still works

1. Open its license management.
2. Deactivate the activation no longer needed.
3. Confirm success.
4. Activate the intended new computer.

If deactivation is unavailable

Prepare the following for the license administrator or support contact:

• key and reason deactivation is impossible;
• available LIC or relevant host ID;
• exact computer to retire;
• other activations that must remain active.

Locate supporting files

The source identifies %SystemDrive%\ProgramData\Bricsys\ on Windows and /var/tmp/bricsys/ on Linux/macOS. Actual paths can depend on the release.

Where several machines are activated, label their assignments carefully. Providing a working machine's license file must not accidentally result in revoking that machine. Share license information only with the intended administrator or support service.

The English article separately covers a website/manual activation with a disabled Deactivate button. In that case, supply its LIC file or the host ID used for that specific activation. If only another machine's LIC is available, clearly identify that machine as the activation to keep.

The activation service cannot interpret the host-ID type correctly. The identifier may have been truncated, surrounded by spaces or entered without a required prefix.

Formats

These examples are not valid substitutes for your computer's actual identifier.

Correct the entry

1. Obtain the host ID on the intended machine.
2. Copy the entire identifier.
3. Remove only unintended spaces before or after it.
4. For a disk serial number, include disksn=.
5. Retry manual activation with the complete value.

Do not reduce it to what looks like the underlying serial number. If the error persists, provide the type and full error message to the responsible license administrator rather than trying random format variations.

In Reprise, -1030 identifies a disabled activation key. The BricsCAD article gives an old key replaced by a license upgrade as a possible cause.

Check

1. Compare the entered key against the current license inventory.
2. Establish whether it was upgraded or replaced.
3. Use the valid replacement key for the appropriate product version.
4. Have the assignment checked if uncertain.

Important distinction

This does not imply that the new upgraded license is invalid. The superseded old key may no longer be activated. Removing local files or reinstalling does not make that key valid again.

When requesting help, identify the product, desired release and code. Do not publish the complete activation key in a public error description.

The activation call cannot find or use the required server-side license generator. The source mentions an incorrect path or a missing or non-executable generator.

User procedure

1. Confirm the error occurs during activation with this code.
2. Record product, license type, release, time and complete message.
3. Try the applicable manual activation procedure, as the article suggests.
4. If that also fails, provide the details to the responsible licensing contact.

What is unlikely to repair it automatically?

A local reinstall does not restore a missing server-side generator. Do not reset local host-ID data without evidence that they are involved.

The short source article does not contain complete offline instructions for every license type. No supposedly universal menu sequence is invented here.

Reprise License Manager distinguishes license checkout, runtime/network failures and internet activation. This selection provides initial guidance rather than reproducing every code in the extensive original reference.

License checkout

Runtime and activation

Record the code, complete message and operation. A fully occupied pool requires a different response from an unreachable server. Use the individual answers for the common BricsCAD scenarios.

For -153 specifically, the English Reprise reference identifies an already-existing rehostable host ID. For -1012, it describes a client clock outside seven days of server time. Read the matching BricsCAD-specific answer before changing activation files.

A failover server takes over a license pool when the primary server fails. Two ordinary server installations alone are insufficient: signed failover license files are required.

Preparation

1. Collect host IDs and IP addresses for both servers.
2. Obtain the corresponding signed failover files.
3. Allow the server-to-server TCP/UDP traffic identified in the source on ports 5053 and 5054.

File placement

Install the Network License Server on the backup machine without performing an ordinary new network activation. Then copy the prepared files. On Windows, the client references belong in C:\ProgramData\Bricsys.

Complete setup

Reread the configuration or restart the RLM services on both servers, then test a client connection.

Limitation: Roaming is unavailable for a license pool taken over by failover. A functioning backup server does not remove that restriction.

Release the previous activation, then activate the new server. Copying a license file to a different machine is not an equivalent procedure.

Plan the move

1. Identify the existing server license and intended replacement.
2. Revoke the old activation using the applicable procedure.
3. Activate the key on the new server.
4. Verify that its service provides the required licenses.
5. Stop the old license manager and remove its now-obsolete license file deliberately.
6. Update client references as required and test a workstation.

If the old server has failed

Have the license administrator or support contact resolve the machine assignment and revocation. The captured restricted-operation source mentions up to two revocations per key.

Follow a controlled sequence and coordinate any service interruption. Do not remove the old server's files prematurely while release and assignment of the activation are still unresolved.

A Communicator network license can be returned to RLM while BricsCAD remains open. This releases the occupied Communicator seat.

Procedure

1. Enter _LICENSEMANAGER.
2. Locate Communicator for BricsCAD.
3. Choose Manage License in that section.
4. Click Return.
5. Confirm with Yes.
6. Verify the successful-return message.

Scope

This action concerns the Communicator license in the selected section. It differs from deactivating a local BricsCAD installation or closing the entire CAD application.

If Return is unavailable, inspect the actual license type and state. The procedure assumes the corresponding Communicator network-license scenario.

Without specific pooling rules, the source describes license assignment in order of pool ID numbers.

Example

A workstation may therefore receive a higher level even if its tasks need only a lower one. In this example, the relevant factor is ID order rather than the filename alone.

Control allocation

1. Identify active pools, levels and IDs.
2. Inspect existing server options, such as those in bricsys.opt.
3. Decide which users or workstations should use which pools.
4. Apply the appropriate license-pooling configuration and test clients.

The short source article does not provide complete advanced pooling syntax. No rule is invented from the example. Configure it for the RLM/server version actually installed.

Its concrete example pairs BricsCAD.lic containing Pro with id=1, and BricsCAD(1).lic containing Ultimate with id=2. These filenames illustrate separate pools; inspect the IDs rather than inferring priority from the numbering in filenames.

On Windows, a LIC reference file can provide the server address. Clients must reach the server through the LAN or intended VPN.

Create the file

1. Determine the actual server name and RLM port.
2. Create a plain-text file, for example Server.lic.
3. Insert a suitable line:

HOST RLMServer ANY 5053

1. Replace RLMServer and, if necessary, 5053 with the real configuration.
2. Place the file in C:\ProgramData\Bricsys on clients.
3. Test one workstation before wider deployment.

Common problems

Do not accidentally save it as Server.lic.txt. ProgramData may be hidden. A correct reference does not open blocked network ports: connectivity and the server service must work independently.

This file points to the server. It does not activate a new license pool or replace server-side configuration.

A shared folder must be mounted in the Linux filesystem before BricsCAD can access its license file through a local path. A Windows-style network browser is not automatically available for this purpose.

Check the setup

1. Identify the server and share containing the file.
2. Have the share mounted at a stable local mount point.
3. Confirm the intended user can read the file there.
4. Select that local path in BricsCAD.
5. Repeat after rebooting.

Persistent mounting

The source refers to a suitable /etc/fstab entry. Its exact syntax depends on the share type, server, account mapping and mount options; it is not universal.

Use protected credential mechanisms rather than copying a clear-text password example into a readable configuration file. The share must be available when BricsCAD starts; mounting it manually only afterward can leave startup licensing unresolved.

Access denied to Service Control Manager indicates, in the described case, that rlm.exe was not launched with the privileges needed to install a Windows service.

Retry correctly

1. Close the existing RLM window or process.
2. Right-click the license server shortcut.
3. Choose Run as administrator and approve elevation.
4. Open its web administration interface.
5. Repeat the service installation.
6. Check the resulting service status.

Why is the web interface insufficient on its own?

The running server process performs the requested service installation. Clicking a web administration button cannot supply Windows privileges the process lacks.

If it still fails, capture the exact message and have service permissions or company policy checked. Avoid starting multiple competing server processes on the same port.

They are normally in the Network License Server installation directory, rather than the BricsCAD client's license folder.

Windows example

C:\Program Files\Bricsys\Bricsys Network License Server

The source identifies BricsCAD.lic as the default filename. Multiple activated keys can produce additional numbered files such as BricsCAD(2).lic. Use the actual installation path; Explorer may display localized folder names.

Before changing anything

1. Identify the installation used by the running service.
2. Confirm which license files it reads.
3. Back up the files and record their pools.
4. Change or remove only the identified affected file.

A workstation LIC file may instead contain only a server reference. It serves a different purpose. When inspecting a signed license in a text editor, avoid unintended changes that can invalidate its contents.

-17 indicates that the client and license server cannot communicate successfully. Possible causes include a stopped service, network access or blocked ports.

Check connectivity

1. Is the workstation connected through the intended LAN or VPN?
2. Is RLM running on the correct server?
3. Are its RLM port, commonly 5053, and the actual ISV port reachable?

Example Windows test:

Test-NetConnection -ComputerName RLMServer -Port 5053

Replace the server name and repeat for the configured ISV port. PowerShell tests TCP here; any required UDP rules need separate checking.

If a test fails

Have server firewall rules and RLM/ISV service status checked. Reaching one port does not confirm the other works.

Proxy environments

The source mentions HTTP_PROXY=server:port and, for basic authentication, HTTP_PROXY_CREDENTIALS. Coordinate these with the administrator and keep credentials out of public scripts. First establish whether a proxy is involved in this particular licensing connection.

-18 means the addressed server does not provide a license satisfying the request. The source identifies a changed server host ID as one possible cause.

Before changing activation

1. Confirm that the client references the correct server.
2. Check that its service runs and the required pool is loaded.
3. Verify product and version coverage.
4. Check whether the license binding still matches the server host ID.

Confirmed invalid server binding

The source describes a controlled revocation, removing the old BricsCAD.lic, activating again with NetworkLicenseManager.exe, and using Reread/Restart in RLM administration.

Back up the file and establish its assignment first. With several pools, do not remove an arbitrary LIC. The captured restricted-operation article mentions up to two revocations per key.

After rereading, check server status before testing the client. Restarting a service does not regenerate an absent or incorrectly bound license.

-43 points to an invalid or unresolved server name in the licensing configuration.

Check step by step

1. Compare the configured name with the actual license server.
2. Check spelling and name resolution on the intended LAN/VPN.
3. Have the server reread its configuration or restart.
4. If name resolution is suspect, test the correct server IP in the client's server field.
5. Also verify the configured port.

Interpret the outcome

If the IP works but the name does not, investigate name resolution. If neither works, also inspect network reachability, port and service status.

The IP must belong to the intended server and be reachable in your environment. Editing a signed license line is not the same as changing a client server reference. Identify the affected configuration type before altering it.

-46 means the available license does not allow terminal-server or Remote Desktop operation. The article describes it when attempting a local trial activation on a terminal server.

Required arrangement

The source calls for a network license in this deployment so the license server manages concurrent use.

Procedure

1. Confirm that BricsCAD is actually running on a terminal server.
2. Establish the license type with the administrator.
3. For testing there, obtain an appropriate trial network license.
4. Alternatively, evaluate an ordinary local trial on another suitable computer.

Different launch privileges do not change the operating mode permitted by the license. This code concerns a licensing condition, rather than merely a missing Windows write permission.

For sharp 2D plans, distinguish vector output from rendered image output. A rendered visual style can cause content to be printed as a raster image.

Configure viewports

1. Select the affected viewport in the layout.
2. For ordinary 2D plans, choose 2dWireframe (the 2D Wireframe visual style).
3. Set Shade plot to As displayed.
4. Use rendered styles only for viewports that actually need a rendered appearance.

Disable JPEG compression for PDF printing

1. Open Print or Page Setup and select Print As PDF.pc3.
2. Open Edit Plotter Configuration.
3. Select the Settings tab, then Custom Properties.
4. Open the custom properties and clear JPEG image compression.
5. Save the configuration and create a new test PDF.

Choose the relevant resolution

Vector DPI affects 2D vector output; image DPI affects rendered or raster content. Increase the relevant setting and compare results at the same zoom level. Higher resolution and disabled JPEG compression can considerably increase PDF size.

JPEG compression affects both embedded raster images and rendered viewport images. Disabling it embeds their raw bitmap data rather than applying lossy JPEG compression.

Without embedded fonts, the PDF viewer or printer must find suitable fonts itself. This can produce substituted fonts, incorrect characters or inconsistent results between machines.

Recommended procedure

1. Create a new PDF with font embedding enabled in the properties of the chosen PDF output method.
2. Inspect the font list in your PDF application's document properties. Used fonts should be identified as embedded or embedded subsets.
3. Open the PDF in a second viewer.
4. Check a physical print if the document will be distributed for printing.

The embedding option depends on the PDF printer or export method. The captured article does not provide one universal dialog sequence.

Why is checking your own computer insufficient?

The correct font may already be installed there. Another computer or printer may not have it. Embedding makes the PDF less dependent on its environment, although it may increase file size.

This answer concerns text stored as text. Converting text into geometry is a different output method.

The English article separately identifies rotated individual characters as a different case. It also notes that a viewer can substitute a missing font even when text remains readable. Its lists of particular viewers describe the source-era behavior, not a guarantee about current viewer releases.

When only certain images, PDF underlays or OLE objects print black or incompletely, the cause is often transparency handling in the printer driver.

Test in order

1. Update the affected system printer's driver.
2. Print the same drawing using another device or PDF output to identify whether the problem follows the print method.
3. For system printers, inspect ImagePrinting.xml in the plotter configuration path. Its comments describe alternative image-printing methods; back it up before editing.

Transparent OLE objects

ImagePrinting.xml does not control this OLE transparency. Use one of these combinations:

• PLOTTRANSPARENCYOVERRIDE=1 with Plot transparencies enabled in the Print dialog.
• PLOTTRANSPARENCYOVERRIDE=2 to force transparency plotting.

Other cases

The built-in PDF methods use PDF export and do not read ImagePrinting.xml. Black gradient hatches also need separate investigation. For very large prints, the source additionally identifies insufficient memory as a possible cause; its especially low memory limits concern historical 32-bit environments.

An assigned CTB is applied only when layout options, visual style, resource path and object colors are compatible.

Check four things

1. Open Print or Page Setup for the affected layout and enable Plot with plot styles.
2. Confirm that the selected CTB can actually be found. Check the plot-style search path if necessary.
3. Use a supported visual style, such as 2D Wireframe.
4. Inspect object and layer colors: TrueColor is not mapped through a color-dependent CTB in the same way as indexed colors.

Example

An object using an indexed CAD color can be plotted black through the CTB. A visually similar RGB/TrueColor object may retain its original color. If CTB mapping is required, adjust the relevant color definition deliberately.

Enable Display plot styles in Page Setup to assess their effect in the layout, then compare the print preview. A rendered view can behave differently from pure 2D output.

The English source also names Wireframe and the applicable legacy Hidden/Wireframe shade-plot modes. _PAGESETUP and _CPAGESETUP provide layout-related settings; the article explicitly distinguishes the current-layout dialog from the Print dialog.

BricsCAD searches the locations in PlotStylePath and PlotCfgPath for plot styles and configurations. Very large folder trees can therefore delay opening the dialog, even if printing itself is fast.

Typical example

A plot-style path points to an entire project drive with many subfolders. BricsCAD must search a large collection for a few CTB files. Network latency can make this slower still.

Improve the paths

1. Create a dedicated directory for CTB/STB files.
2. Create a separate directory for PC3 configurations.
3. Confirm that the required files are present.
4. Point PlotStylePath and PlotCfgPath to those directories.
5. Reopen the Print dialog and compare the delay.

The default resource directories already follow this separation. If the dialog remains slow with small local resource folders, investigate other causes, including unreachable network printers.

Some system printer drivers mishandle gradient fills. A hatch may print black, disappear or print only partially even though the drawing looks correct on screen.

Procedure

1. Install a suitable current driver for the printer.
2. Repeat a small test print containing an affected hatch.
3. If the problem remains, create a PDF using the built-in PDF device.
4. Inspect the gradient in the PDF and print it from a PDF application.

Why can the PDF route help?

The built-in PDF output uses a different path from direct printing through the system driver. It can avoid the driver's problematic gradient operation.

The source does not identify one BricsCAD setting that fixes every affected driver. A successful PDF test is therefore also useful diagnostic evidence: it helps separate a drawing issue from a device-dependent output issue.

A PLT or PRN file contains output for the selected printer driver. The extension alone does not define the format; a PLT is not necessarily HPGL/2.

Configure file output

1. Open Print or Page Setup.
2. Choose the driver for the intended destination plotter.
3. Open Edit Plotter Configuration.
4. Select the Ports tab.
5. Enable Plot to file.
6. Save the settings as a separate PC3 configuration.
7. Print using that PC3 and specify the output filename.

Relevant paths

PlotCfgPath locates PC3 configurations. PlotOutputPath controls the intended output directory.

Before handing over the file

Ask which printer data format the recipient needs. Renaming .prn to .plt does not convert the contents. For an already suitable driver output, it may merely provide the expected extension; an unsuitable format remains unsuitable.

The source distinguishes a PC3 file-output configuration from a Windows printer definition already set to Print to File. The latter can write into the BricsCAD program directory. Check which configuration you selected if the output appears in an unexpected folder.

The direct method is _EXPORT. The captured article identifies 2D and 3D DWF support; it does not describe a separate universal Publish to DWF workflow.

Export

1. Open the intended drawing.
2. Run _EXPORT.
3. Select the required DWF format from the offered file types.
4. Specify a filename and location, then follow the prompts.
5. Open the result in the recipient's DWF application and inspect geometry and appearance.

Multiple sheets or special plotting workflows

The source mentions PDF followed by conversion and a historical Autodesk DWF printer driver as alternatives. These depend on operating system, software versions and available tools. An old 32-bit driver is not a general recommendation for a current installation.

Establish whether the recipient expects DWF, DWFx or another exchange format. Changing an extension alone does not produce the required format.

The English article notes that historical driver workflows may create DWFx rather than DWF, and that another tool may be needed to save the required format. Test the actual recipient format rather than assuming every DWF-related printer produces identical data.

SHORTCUTMENU determines when a right-click opens a context menu. It is a bitcode: add the values for the functions you want to combine.

Change the setting

1. Enter SHORTCUTMENU.
2. Record the previous value.
3. Enter the intended value. For example, 3 combines the default and edit menus (1 + 2).
4. Test without a selection, with selected objects and during a command.

For time-sensitive behavior, also inspect SHORTCUTMENUDURATION, which sets the hold threshold. Shift + right-click opens the Entity Snap menu.

Edit menu contents under Tools → Customize → Menus → BRICSCAD → Context Menus. Object-specific menus can also be inserted through OBJECT_ and OBJECTS_ entries.

A keyboard shortcut connects a key combination to a tool or command. Store additions in your own partial CUI where possible so they can be reloaded more easily after updates.

Example: Drawing Explorer on Ctrl+Alt+E

1. Open Customize.
2. Select the Keyboard tab.
3. Select the intended customization group on the left.
4. Open its context menu and choose Insert Shortcut.
5. Check Select available tool in Add keyboard shortcut.
6. Choose Available tools → BRICSCAD → Drawing Explorer and confirm.
7. In the new shortcut's properties, activate the Key field.
8. Press Ctrl+Alt+E and confirm the customization.

Verify the result

Close the dialog and press the combination in BricsCAD. If the tool does not open, check the assignment and any existing shortcut using the same keys.

Selecting a tool alone does not assign a key combination. The keys must be captured in the intended property field. Labels can differ slightly between interface versions.

Mouse assignments belong to MouseButtonRoot in the CUI. Within each group, BricsCAD uses the first button entry for right-click and the second for middle-click.

Prepare the customization

Back up the CUI. Choose the relevant group and assign the intended menu macro to the button entry. BlankLine=True retains the default action; otherwise the assigned MenuMacro is used. This mechanism does not freely reassign the left mouse button.

If the assignment is ignored

• SHORTCUTMENU: enabled context menus can override a custom right-click.
• CTRLMOUSE: built-in Ctrl/mouse functions can take precedence.
• MBUTTONPAN: enabled panning occupies unmodified middle-click.
• CTRLMBUTTON: temporary tracking-point behavior can take precedence during commands.

Record the original settings and change only the functions needed for your assignment. Test the button both outside a command and while a command is active.

Older MNU menu files can be converted to CUI format when loaded. This imports the menu and toolbar definitions they contain.

Using MENULOAD

1. Enter _MENULOAD.
2. Browse to the existing MNU file.
3. Load it and check the resulting menus and toolbars.

Using Customize

1. Open Customize.
2. Choose File → Load Partial CUI File.
3. Set the file type to MNU.
4. Select the file and confirm the conversion.

Check separately

Command aliases in a PGP file are not automatically imported by this procedure. Referenced images and external applications must also remain available.

If individual tools are missing after import, compare the spelling of their internal IDs, including uppercase and lowercase letters. Keep an unchanged copy of the original file so the conversion can be repeated from a known starting point.

MENU and MENULOAD load menu definitions such as CUI and MNU. PGP files hold command aliases, which use a different mechanism.

Edit aliases in the interface

Open Customize and use the Command Aliases or Shell Commands tab for the corresponding assignments.

Edit default.pgp directly

1. Locate the default.pgp actually used by the user configuration.
2. Back it up.
3. Edit the intended alias definitions in a text editor and save.
4. Return to BricsCAD and run _REINIT to reload the aliases.
5. Test an alias you changed.

If nothing changes, inspect SRCHPATH. A file with the same name earlier in the search sequence may be used instead of your edited file.

Selecting an ICA or PGP file in MENULOAD does not turn it into a menu definition. Use the appropriate alias editor and reload procedure instead.

Direct changes to default.cui can conflict with a newly supplied standard file. Otherwise, you may have to choose between retaining your changes and accepting the updated interface features.

Store customizations separately

1. Back up default.cui and default.pgp before updating.
2. Place personal menus, toolbars and shortcuts in a separate partial CUI where possible.
3. Continue using the supplied default.cui as the main customization file.
4. Accept the updated standard file when your backed-up customization arrangement allows it.
5. Reload your partial CUI if its reference is no longer present.

Why might reloading be necessary?

The reference to the partial CUI is stored in the main CUI. Replacing the main file can remove that reference even though your separate file still exists.

The source discourages the reverse arrangement of making your own main CUI and attaching default.cui beneath it. After updating, check aliases and resource paths as well as visible toolbars.

A damaged default.cui can cause a Xerces error and leave BricsCAD without its normal menus and toolbars.

Restore through BricsCAD

1. Start BricsCAD if possible.
2. Enter _CUI or _CUSTOMIZE.
3. Open Manage your customizations.
4. Choose Revert to defaults.
5. Confirm both the management dialog and the Customize dialog.

This replaces the user file with a clean standard copy from UserDataCache. Direct personal changes to that CUI are replaced too, so back it up first where possible.

Alternative for an unmodified default setup

The source describes renaming the release/language-specific user support area and restarting. This affects more resources than the menu alone. Use it only with a backup and a clearly identified user directory.

If the restored interface works, reload partial CUIs individually. This helps identify whether a particular customization reintroduces the problem.

For an English V26 user configuration, the source's roaming-area example is %APPDATA%\Bricsys\BricsCAD\V26x64\en_US\. Identify the actual support folder before renaming anything; the source labels this alternative for installations without personal customization.

Missing interface elements can result from workspace changes or damaged customization. Restoring defaults reloads the standard customization for the current workspace.

Procedure

1. Enter _CUSTOMIZE.
2. Open Manage your customizations.
3. Choose Revert to defaults.
4. Confirm the management dialog with OK.
5. Confirm the Customize dialog with OK.

Before restoring

Back up your own CUI files and note which partial CUIs are loaded. Direct changes to the standard interface may be replaced.

After restoring

Check the intended workspace and reload backed-up partial CUIs if needed. If symbols or menus are still missing, also inspect SRCHPATH and the actual CUI file being loaded.

Restoring the interface does not fix unrelated drawing corruption or third-party application failures. Keep those problems separate when assessing whether the reset helped.

Question marks often indicate that an old CUI references incompatible image resources. A missing support path or resource file may also be involved.

Check and restore

1. Identify the default.cui actually loaded.
2. Check SRCHPATH and the associated resource directories.
3. Back up personal CUI customizations.
4. Open Customize and choose Revert to defaults, through customization management if required.
5. Reload your partial CUIs afterward.

Restoring defaults copies the current standard file from the installation's user-data cache, allowing icon references to match the installed program.

After the test

If standard icons return, inspect your own menus separately. Their images may be stored in a DLL, RESZ archive or individual image files.

Keep personal additions in a partial CUI so future updates can replace the standard file without requiring you to discard your custom work.

A regular pull-down menu in the main CUI needs a POP alias. Without one, it can exist in the customization but remain absent from the menu bar.

Check the alias

1. Open the relevant main customization in Customize.
2. Inspect the missing menu's alias.
3. Use an appropriate value from POP1 to POP32 without displacing an existing required assignment.
4. Confirm and inspect the menu bar.

An example CUI entry is:

<Alias>POP10</Alias>

Main and partial CUI behavior differs

Regular menus from partial CUIs do not have the same main-menu requirement. Context menus are separate types, including CMCOMMAND, CMDEFAULT, CMEDIT, OBJECT_ and OBJECTS_ aliases.

The source also describes MENUCMD in LISP for controlling menus at runtime. That is a distinct customization mechanism, rather than a replacement for checking a missing POP alias in an ordinary main menu.

A runtime example in the English article uses MENUCMD:

(menucmd "P5=+MENUGROUP.ALIAS")

Replace the menu group and alias with your actual identifiers. The example is a deliberate customization operation, not something to paste unchanged for every missing menu.

The CUI stores initial values for toolbar position and visibility. After an ordinary session, BricsCAD stores the actual interface state in the user's configuration.

Why is my change ignored?

You change a toolbar's CUI setting to Top or Visible, but the next launch restores its previously saved personal position and visibility. The initial CUI value no longer takes precedence.

Test a changed default

1. Back up the customization.
2. Change the initial toolbar properties in Customize.
3. Start BricsCAD with a new test profile.
4. Check position, docking and visibility there.

If the setting works in the new profile, the CUI property is not necessarily defective; an existing saved state was overriding it.

The source identifies the registry as the Windows storage location and a configuration file on Linux. Do not delete an entire working profile simply to test one toolbar position.

BricsCAD checks user folders and customizable-file versions at startup. If expected resources are absent, it may copy default.cui from the installation cache again and report that a backup was made.

Known triggers

• Missing local root directory.
• Missing roaming root or its support directory.
• Empty support directory.
• A VersionCustomizableFiles value below the expected program version.
• A version/time comparison identifying a newer standard CUI.

Investigate repeated resets

1. Back up the current CUI and partial CUIs.
2. Inspect LOCALROOTPREFIX and ROAMABLEROOTPREFIX.
3. Check directory availability, contents and required permissions.
4. Restart and confirm the created files remain after closing.

A one-time refresh following an update differs from the same reset on every launch. Repeated resets particularly suggest user directories are not persistently available. Simply copying your personal CUI back does not fix incorrect root-folder initialization.

Tool IDs are case-sensitive when MNU/MNS definitions are converted. Different capitalization can produce different internal identifiers.

Example

A menu uses ID_MkBom, while a toolbar uses ID_Mkbom. These look almost identical but are distinct references. The menu can work while its toolbar button is missing or reports a macro-group error.

Repair

1. Back up the original MNU/MNS file.
2. Find the ID from the error in the file.
3. Compare the definition with every reference to it.
4. Use identical spelling everywhere, for example ID_MkBom.
5. Reload or reconvert the corrected file.
6. Test both the menu item and toolbar button.

Do not change only the visible label. The internal tool ID is what matters. When several tools fail, check references systematically and avoid introducing duplicate names for unrelated tools.

A resource DLL or RESZ archive can bundle images used by your CUI. Its base filename must match the menu file.

RESZ example

1. Your customization is named MyMenu.cui.
2. Put its image files directly at the top level of a ZIP, without an extra enclosing image directory.
3. Rename the archive MyMenu.resz.
4. Place it beside MyMenu.cui.
5. Reload the customization and inspect the icons.

Search order in the source

1. Built-in resources in bricscad.exe.
2. DLL matching the loaded menu's base name.
3. RESZ matching that name.
4. Individual image files in the CUI directory.
5. Individual files found through SRCHPATH.

Renaming a ZIP produces a RESZ archive, not a genuine resource DLL. A DLL requires appropriate development tools. If icons remain missing, check their names and CUI references; creating an archive does not repair incorrect image references.

This article concerns Windows 10 and the BricsCAD file dialog. Policy or registry permissions may prevent customized Places Bar locations from persisting.

Administrator policy check

1. Close BricsCAD.
2. Open gpedit.msc if available in the Windows edition.
3. Navigate to User Configuration → Administrative Templates → Windows Components → File Explorer → Common Open File Dialog.
4. Inspect Items displayed in Places Bar. The source describes enabling this policy.

BricsCAD configuration

1. Start BricsCAD elevated for setup if needed.
2. Set USESTANDARDOPENFILEDIALOG=0 for the dialog addressed by the article.
3. Set PLACESBARFOLDER1 through PLACESBARFOLDER4 to the intended directories.
4. Close, reopen and check the entries.

Check company policy before changing local settings. Not every Windows edition supplies the same policy editor, and a historical Windows 10 procedure is not a universal menu sequence for every current system.

In this case, the message occurs while BricsCAD customizes its file dialog. It tries to save information in the configured drawing directory, but the folder is missing or not writable.

Correct the drawing path

1. Open Settings.
2. Search for DRAWINGPATH.
3. Use the browse button next to the setting.
4. Select an existing directory where your account can write.
5. Confirm and try opening a drawing again.

If the path is on a network drive

Check that the drive is connected in the current session and that the subfolder still exists. An obsolete project path or another user's folder can explain the error.

Do not start by editing arbitrary Desktop.ini files. The relevant issue here is the location configured in DRAWINGPATH and whether BricsCAD can access it.

BricsCAD may update its OLE/COM registration at startup. If the process cannot access the protected registry location, it can report that the system registry could not be updated.

Repair attempt

1. Close BricsCAD completely.
2. Right-click the program shortcut.
3. Choose Run as administrator.
4. Approve the Windows prompt and allow startup to complete.
5. Close BricsCAD and test a normal launch.

An administrator account alone is not enough: the particular launch must be explicitly elevated.

If the message remains

Record the release, message and point at which it appears. Have the administrator check the required registration and policies. If several major releases are installed, identify which executable is actually being launched.

This procedure does not call for permanently changing the privileges of the account used for ordinary drawing work.

This concerns an older VBA 6 environment. Installing another application using VBA 7 can change a shared library reference so a macro looks for a nonexistent file.

Registry entry to inspect

HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\6.0\9\win32

The source describes a possible incorrect reference to C:\Windows\SysWOW64\msvbvm60.dll. It identifies this as a possible VBA 6 library location:

C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL

Administrator procedure

1. Confirm that VBA 6 and this particular error are involved.
2. Check whether the intended library actually exists.
3. Back up the registry branch.
4. Correct only a confirmed incorrect reference, or repair the affected VBA installation.
5. Test the macro again.

An example path is not proof that the file exists there on every machine. Do not apply this historical repair indiscriminately to newer VBA runtimes.

In the releases described, REDSDK handles rendering and certain visual styles. A REDSDK error can involve the graphics driver or a particular display path.

Initial checks

1. Save your work if possible.
2. Install a suitable current driver for the GPU actually being used.
3. Reproduce the problem with the same drawing.
4. Collect REDSDKINFO output for diagnosis.

Temporary test avoiding the affected path

With GSDEVICETYPE3D=0, the source's Hidden, Flat and Gouraud styles use a non-REDSDK path.

These variables and graphics systems depend on the release. Record original values before changing them. If the problem remains, provide the actual error, BricsCAD build, driver and reproduction sequence rather than only reporting a generic graphics problem.

Windows may recognize a dock's video chipset as an additional display adapter. If BricsCAD selects it instead of the intended GPU, startup or rendered 3D views can fail.

Isolate the dock

1. Close BricsCAD.
2. Connect a monitor directly to the computer's HDMI or DisplayPort output.
3. Test with the built-in notebook display set as the main display.
4. Compare startup and switching to the affected 3D style.

If the direct connection helps

Have the GPU assignment and monitor wiring reviewed. The source also suggests a suitable USB-C-to-HDMI adapter without the problematic dock video chipset.

Disabling integrated graphics is another intervention mentioned in the original, but can affect other displays. Direct connection is a clearer initial diagnostic test.

Record the dock model, GPU, driver and affected connectors so the relationship can be reproduced rather than inferred from one unexplained crash.

A report is most useful when the problem is reproducible with the same file and sequence of actions.

Narrow down the sequence

1. Record commands and actions immediately before the crash.
2. Test a new profile and /SAFEMODE.
3. Explain whether the application closes, freezes or displays a message.

Collect these items

• Drawing and dependencies: _ETRANSMIT packages Xrefs, images and relevant resources.
• User profile: export the active profile using _PROFILEMANAGER.
• Graphics details: _REDSDKINFO output.
• Windows/Linux: crash_report.txt and available DMP files; check user, drawing and program startup directories.
• macOS: the corresponding BricsCAD IPS report.
• Command log: enable _LOGFILEON before reproduction; inspect LOGFILEPATH for the location.

Make the report readable

Identify the operating system, release and build. Provide numbered steps, expected behavior and actual behavior. State whether the issue also occurs without add-ons and with a new profile.

Check the project files included before transmitting a package to the intended support contact.

The English crash guide additionally suggests Windows Safe Mode when needed to isolate background-process conflicts. This is a separate operating-system test from BricsCAD /SAFEMODE; record the result of each independently.

Safe mode suppresses third-party plugins, enablers and user LISP for the session. It helps determine whether an extension is involved in a failure.

Create a Windows test shortcut

1. Copy the existing BricsCAD shortcut.
2. Open its Properties.
3. Add a space and /SAFEMODE after the complete executable path in Target.
4. Start BricsCAD through this copy.

Example; adjust the release and language directory:

"C:\Program Files\Bricsys\BricsCAD V26 en_US\bricscad.exe" /SAFEMODE

Further isolation

• DEMANDLOAD=0 suppresses demand-loaded modules.
• Use _VBAMAN and _VBARUN to inspect VBA applications and macros.
• Check autoload.rx, appload.dfs, startup/document LISP files, default.dvb and additional MNL files for custom additions.

Do not delete these files wholesale. Back up or rename individual custom additions and record changed settings. If the error disappears, re-enable extensions one at a time until the cause becomes clear. Retain the ordinary shortcut for normal work.

The English checklist expects no applications in VBAMAN, and only default.dvb with no listed macros in VBARUN. Use these observations to confirm the clean session, rather than assuming every application has been suppressed.

Investigate profiles, add-ons, graphics and installation files separately. Reinstalling alone often leaves a faulty user configuration in place.

Test sequence

1. Launch with /SAFEMODE to isolate extensions.
2. Try a new profile, for example:

"C:\Program Files\Bricsys\BricsCAD V26 en_US\bricscad.exe" /p TestProfile

1. Start with a 2D template. BIM or Mechanical templates may use a different graphics path.
2. Check security software history for quarantined program DLLs.
3. If COM registration is suspect, try one explicit Run as administrator launch.

Isolate support files

Back up the user support directory matching the account, release and language. A temporary rename can help identify involvement of CUI, PGP or LISP files. Restore the contents selectively afterward.

If a new profile works, retain the original profile for diagnosis. If startup still fails, collect crash files, build information and reproduction steps. Recording the result of each individual test is more useful than changing several things simultaneously.

The English support-folder example is %APPDATA%\Bricsys\BricsCAD\V26x64\en_US\Support. Rename only the actual affected folder, keep the original contents, and restore individual files for comparison if the clean setup starts.

A BAK backup or SV$ autosave may contain a recoverable earlier state. Neither guarantees recovery of every unsaved change.

Locate and test candidates

1. Look for the drawing's .bak file.
2. Use SAVEFILEPATH to identify the autosave directory and locate a relevant .SV$ file.
3. Compare names and modification times.
4. Copy the best candidate to a safe working location.
5. Change the extension of the copy to .dwg.
6. Open and inspect it before continuing work.

Reduce future loss

• Save regularly with Ctrl+S.
• SAVEBAK controls backups of the previous drawing state when saving.
• SAVETIME sets the autosave interval in minutes; the captured source identifies 60 as its default at that time.

Check the actual interval in your installation. For repeated crashes, a new profile created with profilemanager_app.exe can help isolate configuration issues. Preserve the recovery candidates independently of that test.

Create a clean test profile

Open profilemanager_app.exe in the installation folder. Choose Create, enter a new profile name, confirm, select the new profile and choose Set Current. Confirm the dialog and restart BricsCAD. Keep the previous profile so you can return to it.

Automatic startup files can load commands, LISP functions or modules. For troubleshooting, identify which event triggers loading.

autoload.rx supports startup loading of BRX modules. appload.dfs relates to application loading. User LISP files must be discoverable through the relevant search paths, particularly SRCHPATH.

Investigate unexpected loading

1. Test /SAFEMODE first.
2. Compare the files above against your intended customization setup.
3. Back up suspect additions and disable them individually for testing.
4. Note whether the behavior starts with the program, a drawing or a menu.

BricsCAD also loads many internal binary modules. Their names vary by release and feature set. An old list of module names is not a list of files to delete from an installation.

If text has the correct style but incorrect characters, ambiguous selection within a font family may be involved. The source describes a small number of families with similar font files, including certain Gill Sans configurations from V18 onward.

Diagnose the font setup

1. Identify the family and style used by the text style.
2. Compare with another known-working font family.
3. Inspect the installed styles of the affected family.
4. Test a backed-up, simplified font setup initially containing Regular, Bold, Italic and Bold Italic.

Example in the source

For Gill Sans, extra Light, Light Italic, SemiBold, SemiBold Italic and UltraBold files are identified as possible contributors. This does not mean every installation containing them is faulty.

Do not remove system fonts without a backup. Other documents and applications may depend on them. The relevant issue is the family metadata and resulting file selection, not simply how many fonts are installed.

The English source also mentions Linux Libertine G. Its Noto Sans example explains the distinction: Noto Sans Italic and Noto Sans Light Italic can belong to different families despite similar names, avoiding the particular ambiguity. Inspect family metadata instead of removing fonts solely because they share a display-name prefix.

The captured article concerns a historical Windows 10 version 1709 display problem. Dragging floating or dockable windows can leave gray outline remnants.

What is happening?

The dragging outline is not fully redrawn. This differs from a lost toolbar or damaged drawing. The source observed similar behavior in other applications.

For a current case, record

1. Windows version, BricsCAD build and graphics driver.
2. Whether only dragging dockable windows is affected.
3. Whether other applications show the same behavior.
4. A short screen recording of the reproduction steps if useful.

The historical article does not provide a confirmed universal repair for current Windows releases. Its old discussion of avoiding a particular Windows update should not be read as a present-day recommendation to remove system updates. Current diagnosis must use the actual system combination.

An add-on must match the BricsCAD major release and required runtime. Successfully installing an add-on does not prove it can run in the BricsCAD version you launch.

Check in order

1. Record the exact BricsCAD release and build.
2. Identify the add-on and its version.
3. Confirm the application vendor supports that major release.
4. For VBA applications, verify that the appropriate VBA runtime is installed and working.
5. Capture the complete loading error.

After changing major releases

Use the add-on build intended for the new release. A runtime change may require recompilation. Merely copying old application files into a new program directory does not establish compatibility.

If BricsCAD starts without the extension but the extension fails, provide the vendor with these release and error details. This helps distinguish application incompatibility from a general BricsCAD fault.

An undo step may cover too much work if the internal command-history grouping becomes inconsistent. An add-on can be involved, but is not automatically the cause.

Isolate the behavior

1. Work on a drawing copy.
2. Record the exact command sequence preceding the unexpected _UNDO result.
3. Repeat with /SAFEMODE.
4. If the issue disappears, re-enable applications and customization gradually.

Diagnose a reproducible case

• Temporarily set QAFLAGS=256 for additional diagnostic messages.
• If BricsCAD reports a damaged command history, run DUMPSTATE and retain the report from the startup directory.
• Use LOGFILEMODE=1 to record commands; LOGFILEPATH identifies the destination.

Record and restore previous values after testing.

Distinguish different symptoms

Missing screen redraw, a crash during UNDO, an unavailable undo mechanism and genuinely excessive reversal are different cases. Ordinary undo cannot reverse creation of objects from a previous session merely because those objects are still in the drawing. Record what actually disappears rather than grouping all undo-related behavior together.

First distinguish slow opening/saving from slow screen navigation. They can have different bottlenecks.

Opening and saving

1. Compare the same DWG locally and on the network.
2. Check Xrefs and resource paths for unreachable network locations.
3. Test a copy with _RECOVER.
4. The source proposes _MTFLAGS=4095 as a test; restart BricsCAD afterward.
5. Monitor CPU/RAM and free space on C:. The source recommends at least 10% free space.

Zoom, pan and orbit

Compare 2D Wireframe with rendered styles and verify which GPU is used. For 3D, test:

• Gooch face style instead of Realistic.
• Smooth lighting instead of Smoothest.
• Material display Off.
• Edge display Isolines or None.

The source also suggests separate tests of GSDEVICETYPE2D, GSDEVICETYPE3D and _SHADEMODE/_GOURAUD; restart after graphics-variable changes where required.

Document comparisons

Test /SAFEMODE and direct monitor connections without a USB dock. Record timings, build, driver and original settings. Useful diagnostic information includes _ETRANSMIT, _REDSDKINFO and the local/network comparison. Revert unsuccessful test changes.

The English checklist also calls for the Windows High Performance/Best Performance power plan, a High performance graphics assignment for BricsCAD, and freezing layers containing xlines/rays where practical. Include CPU, RAM and GPU observations when comparing results.

BricsCAD saves through a sequence: create a temporary file, rename the existing DWG to BAK, then rename the new file to DWG. Blocking any stage can cause saving to fail.

Separate file and location tests

1. Save a new empty drawing in the same target directory.
2. Save the affected drawing to a short local path such as C:\Test, if writable.
3. Compare with the network location. If local saving succeeds, inspect the share and connection.
4. Check read-only attributes and permissions to create, write, rename and delete.

Further tests

• CHECKDWLPRESENCE=1: drawing-lock checks.
• /SAFEMODE: isolate plugins and LISP.
• _AUDIT and _PURGE: inspect and clean a drawing copy.
• LOADMECHANICAL2D=0 and DEMANDLOAD=0: limit optional modules for diagnosis.

Record original values. Do not delete lock files while another session may still be using the drawing.

Also investigate controlled folder access, long paths and synchronization/VPN drive mappings. If needed, use QAFLAGS=256 and capture the F2 command history. Retain the complete error, target path and test outcomes.

Operating-system checks from the English guide

In Windows Security → Virus & threat protection → Ransomware protection, inspect Controlled folder access for a blocked bricscad.exe. For a problematic mapped share, compare a native Windows SMB mapping with a third-party synchronization/VPN mapping. Record the mapping method and short-local-path result for support.

Security software can incorrectly block a program file, affecting startup, activation or performance. An exclusion should address a confirmed false positive involving a trusted installation.

Open Windows Security

1. Open Windows Settings.
2. On Windows 11 select Privacy & security; on Windows 10 use Update & Security.
3. Open Windows Security → Virus & threat protection.
4. Inspect Protection History and the exact file involved.

Create a targeted exclusion

1. Under virus and threat protection settings, choose Manage settings.
2. Open Add or remove exclusions.
3. Choose Add an exclusion and the relevant file option.
4. Select the actual bricscad.exe of the intended installation.
5. Repeat the original test.

With multiple releases installed, the path must match the executable being launched. Controlled folder access is a separate protection mechanism; a virus-scanner exclusion does not automatically resolve a blocked folder write.

Managed company devices may require an administrator to change policy.

A backtrace shows nested function calls at the time of failure. It is more informative than a segmentation-fault message alone.

Check the existing report first

From V24.2, the source describes crash_report.txt containing diagnostic information and possibly a backtrace.

Investigate with GDB

Replace vXX and the directory with your actual installation:

LD_LIBRARY_PATH=/opt/bricsys/bricscad/vXX GDK_BACKEND=x11 QT_QPA_PLATFORM=xcb gdb /opt/bricsys/bricscad/vXX/bricscad

1. Enter run in GDB.
2. Reproduce the problem.
3. Return to the terminal and enter bt.
4. Capture disas if required.
5. Save the complete output, including additional pages, in a text file.

If the application hangs rather than crashes, interrupt it in GDB using Ctrl+C, then try bt. Exit with q and respond appropriately if asked to terminate the debugged process.

GDB must be installed. Include the build, distribution and reproduction steps. The X11/xcb environment in this example comes from the source and must fit the Linux environment being tested.

Windows System File Checker (SFC) examines protected system components. It can help when damaged Windows files are suspected of contributing to an application failure.

Run the check

1. Save open work.
2. Open Command Prompt using Run as administrator.
3. Enter:

sfc /scannow

1. Let the scan finish.
2. Record its final message.
3. Repeat the original test, restarting first if Windows requires it.

Interpret the outcome

SFC checks Windows components, not automatically your DWG, CUI or third-party plugins. A clean result therefore does not rule out other BricsCAD causes.

If Windows reports damage that could not be repaired, pass the message to your system administrator. The captured article does not provide a complete follow-on Windows repair procedure.

Some hatch definitions contain inaccuracies that become visible at large coordinates. The same pattern may look correct near the origin and distorted far away.

Work with a local UCS

1. Create a user coordinate system with its origin close to the area to be hatched.
2. Create the hatch in that UCS.
3. Check the pattern, scale and appearance.
4. Return to the world coordinate system if needed.

The source describes correctly created hatches retaining their appearance after returning to the WCS.

Alternative

Test another hatch pattern. This helps establish whether the definition is involved.

Do not begin by moving an entire project or georeferenced model to the origin. A local UCS lets you test creation at favorable local coordinates without relocating the project geometry.

A multileader using block content may align unexpectedly when its Attachment setting is Insertion point and the source block has no suitable intersection for the intended alignment.

What does BricsCAD use instead?

If no suitable intersection is found in the block geometry, the insertion point is used. The leader may then appear attached at an unexpected location.

Adjust the source block

1. Confirm that the affected multileader style uses insertion-point attachment.
2. Edit the content block definition.
3. Add geometry providing the required intersection for left attachment.
4. Place alignment-only helper lines on a No Print (non-plotting) layer.
5. Check a newly created or updated leader.

The original article explains the intersection using a diagram. Its position depends on your block geometry; no single coordinate can be prescribed for every block. Inspect the attachment point actually provided by the geometry.

The message can be caused by changed endpoints, an expired API key or incompatible referrer restrictions.

BricsCAD V24.2 and V25.1: inspect endpoints

ESRI changed these addresses on 26 February 2025. Under Settings → Online Maps Services, compare the metadata and tile addresses with the following complete values.

Streets metadata:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/streets/static

Streets tiles:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/streets/static/tile/{level}/{row}/{column}

Light gray metadata:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/light-gray/static

Light gray tiles:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/light-gray/static/tile/{level}/{row}/{column}

Dark gray metadata:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/dark-gray/static

Dark gray tiles:

https://static-map-tiles-api.arcgis.com/arcgis/rest/services/static-basemap-tiles-service/v1/arcgis/dark-gray/static/tile/{level}/{row}/{column}

Keep the placeholders in braces as part of each tile address.

Check the key

In ArcGIS Location Platform, open My dashboard → Developer credentials → Manage credential → Settings → Application. Inspect API Keys for expiration and Referrers for restrictions.

The source identifies referrer entries as a possible blocker. Have the key configured appropriately for desktop use. The English article states that changing referrers invalidates the existing key, so regenerate it or create a new one afterward. Replace an expired key as well.

Drawing Explorer transfers definitions such as blocks and layers between open drawings. Copying definitions does not automatically copy every drawn entity from the source plan.

Procedure

1. Open the source and destination drawings.
2. Open Drawing Explorer.
3. Select the source category, such as Blocks or Layers.
4. Select the intended definitions; use Ctrl for multiple selections.
5. Drag them onto the destination drawing's name in Open Drawings.
6. Release the mouse button there.
7. Review any prompts about existing definitions with the same name.

Why does the prompt matter?

Overwriting a same-named block or layer can change a definition already used in the destination. Decide deliberately which version should apply.

Inspect the destination definitions afterward. For blocks, inserting a block reference into the drawing is a separate operation after copying its definition.

Choose between a native CAD table and an Excel/OLE object. This determines how the content will be edited later.

Native table

1. Run _TABLE.
2. In Insert Table, choose Upload file.
3. Select a supported CSV, XML, XLS or XLSX file and inspect the imported data.

Alternatively, copy Excel cells and use _PASTESPEC with XML Spreadsheet. This imports a native BricsCAD table.

Excel OLE object

1. Choose Insert → Insert Object.
2. Select Create New for a new spreadsheet or Create from File for an existing one.
3. Enable Link if the external file should remain linked.
4. Confirm and place the object.

Ctrl+C in Excel followed by Ctrl+V in BricsCAD can also insert an OLE object. Edit OLE object... opens the associated application.

A link requires continued access to its source file. OLE availability depends on the operating system and installed applications; the described Excel workflow requires a compatible environment.

For a new OLE spreadsheet, the English dialog uses Create New → Microsoft Excel in Object Type. For an existing one, use Create from File → Browse.... Saving edits in Excel updates the embedded OLE object.

MTEXTED selects the editor used for multiline text. An external editor must be reachable through a valid executable path.

Set an external editor

1. Locate the complete path to the installed editor.
2. Record the current MTEXTED value.
3. Enter the executable path as the new value.
4. Edit an MText object to test it.

A program name alone may fail when BricsCAD cannot find it in the search paths. The source also mentions adding the application directory to SRCHPATH.

International characters or input methods

The article describes oldeditor as an alternative internal editing dialog that can help with composed characters or input-method problems.

WordPad paths in the old article are examples from historical Windows installations. Use them only if the executable actually exists. The source generally recommends the standard in-place editor for normal work; report reproducible input issues with the operating system and precise keystrokes.

The historical English WordPad example is:

C:\Program Files\Windows NT\Accessories\wordpad.exe

Use this only if the file actually exists on the intended system. The original symptom is “The specified value is not within the system variable range” when the editor cannot be resolved.

_DRAWORDER controls which 2D objects appear in front of others. Typical uses include hatches, text and masking objects.

Standard method

1. Select the affected objects.
2. Run _DRAWORDER.
3. Choose the required front/back or relative-order option from the prompts.
4. Inspect the result in the intended view and print preview.

Check the visual style

The source describes limitations with rendered styles in model space and rendered layout viewports. For pure 2D output, compare 2D Wireframe before concluding the order setting is defective.

Alternative mentioned in the original

Cutting objects and pasting them back at their original position recreates them as newer objects, which can bring them forward. Use this deliberately: recreating objects is not equivalent to changing the order of existing ones. For drawings containing dependent data, test the approach on a copy first.

The older article describes a failure when unpacking a password-protected e-book ZIP because the selected archive application could not process its encryption.

Procedure

1. Confirm that the ZIP download completed.
2. Use an archive application supporting the relevant encrypted ZIP format.
3. Open the archive there and enter the supplied e-book password.
4. Extract into a writable directory.
5. Open the extracted e-book file.

The source names StuffIt Expander as a historical example. Check compatibility with your macOS release before installing it, or use an existing suitable archive application.

An unpacking failure does not automatically mean the e-book itself is corrupt. An incorrect password or incomplete download would need separate investigation.

Lightweight 2D polylines store suitable geometry more compactly. PLINETYPE controls both newly created polylines and automatic handling of existing ones when opening a drawing.

Test the setting

1. Save a drawing copy.
2. Record the current PLINETYPE value.
3. Enter the intended value.
4. Check a new polyline or reopen the drawing to inspect the relevant effect.

For deliberate conversion of existing entities, use _CONVERTPOLY.

The setting concerns eligible polylines. It does not mean every spatial polyline or other curve can be converted to the same compact representation without conditions. Inspect the geometry after conversion, particularly when other software will use the drawing.

Imported DGN linetype data can increase drawing size and processing time. The source describes cases where ordinary purging does not remove this special data.

Historical solution

An additional .NET tool, DgnLsPurge.dll, supplies DGNPURGE after being loaded with _NETLOAD.

Use only a suitable tool

1. Back up the DWG and work on a copy.
2. Check the DLL's origin and approval for your BricsCAD release.
3. Verify its .NET requirements. In particular, an older DLL may not run unchanged in V26.
4. Load the verified DLL with _NETLOAD.
5. Run DGNPURGE.
6. Save, reopen and compare file size and content.

This FAQ does not supply the old DLL. The name DGNPURGE alone is not a standard command available without a compatible tool. Ordinary _PURGE may be insufficient for the specific data described.

Incorrect characters and misplaced columns usually involve two separate settings: encoding and delimiter.

BricsCAD export settings

A BOM is a marker at the start of a file that can help applications recognize its encoding.

Import deliberately

1. Use your spreadsheet application's text/CSV import rather than simply double-clicking.
2. Select UTF-8.
3. Select the delimiter actually used, such as a semicolon or comma.
4. Inspect the preview for characters, columns and numbers.
5. Import only when the preview is correct.

A double-click often relies on automatic assumptions. If all data appears in one column or accented characters are wrong, repeat using the import dialog before altering the CSV contents themselves.

BricsCAD can load an attachment only when it can find its file. Moving a project can separate the stored reference from the actual location.

Three approaches

• Keep attachments in a clear project structure, optionally beside the main drawing.
• Add required locations to PROJECTSEARCHPATHS or SRCHPATH.
• Use the extended search for missing attachments.

Extended search

1. Open the main drawing and the Attachments panel.
2. Select the missing Xref or image.
3. Choose Run extended search for missing attachments from its context menu.
4. Review the found file and corrected reference.

The source describes this for relatively attached files. It searches matching names in the relevant subdirectories and support paths, and can process several attachments together.

Check duplicate filenames: Inspect the actual referenced content. A formally valid repaired path might otherwise point to another project's version of a same-named file.

MIRRTEXT=0 does not protect every text entity inside a block. Ordinary TEXT/MTEXT and constant attributes can still be mirrored with the entire block reference.

Use a nonconstant attribute

1. Edit the block definition.
2. Create the required label using _ATTDEF.
3. In Define Attribute, ensure Constant under Attribute Flags is not enabled.
4. Set MIRRTEXT to 0.
5. Test mirroring a suitable block reference.

Why does this help?

A nonconstant attribute is handled differently from ordinary text geometry inside the block. The variable can therefore keep attribute text readable even when ordinary block text would appear reversed.

Inspect the actual attribute definition. If Constant remains enabled, or the content is still ordinary MText, the solution's requirements are not met. After modifying the definition, check existing references as well as a new test insertion.

The English article also identifies Constant under Misc in the Properties panel when the attribute is selected. Use that to inspect the actual definition rather than judging from the visible label alone.

BricsCAD V26 uses .NET 8. Plugins built for .NET Framework 4.8 must be adapted and rebuilt; installing a newer runtime does not convert them automatically.

For users

1. Install .NET 8 Desktop Runtime, x64.
2. Use the plugin build explicitly intended for BricsCAD V26.
3. For error 0x80131515, inspect whether Windows blocked the DLL: Right-click → Properties → Unblock, if offered and the file's origin is trusted.
4. Retry loading and capture the complete error.

For developers

Install the .NET 8 SDK, x64, use an SDK-style project and appropriate BricsCAD assemblies. A project target can be:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net8.0-windows</TargetFramework>
  </PropertyGroup>
</Project>

Rebuild with the updated references.

Installation notes

The source points to the .NET API README, for example:

C:\Program Files\Bricsys\BricsCAD V26 en_US\API\dotnet\README.txt

Adjust release and language paths. The runtime executes applications; the SDK additionally provides development/build tools. They serve different purposes.

The English guide describes legacy .NET Framework support as deprecated in V26 and requires rebuilding Framework-based plugins for .NET 8 before loading them. Use the README shipped with your installed build for migration specifics.