How to troubleshoot BricsCAD performance issues

Slow file opening or saving

When opening or saving DWG files takes longer than expected, the primary hardware resource bottleneck is typically the CPU, often exacerbated by network latency or disk read or write limitations.

Common causes

  • Low free space on C: (temporary files and virtual memory pressure).
  • Network latency (files on server, NAS or VPN).
  • Resource searches on network paths.
  • Antivirus scanning bricscad.exe or DWG access.
  • Network drive mapping overhead (custom solutions).
  • High DWG or Xref complexity.
  • Third-party plugins or LISP conflicts.

BricsCAD checks
  • Run the _RECOVER command on the DWG file.
  • Copy the DWG file to a local drive, then retest the open and save times.
  • Set the _MTFLAGS system variable to 4095. BricsCAD must be restarted after the change.
  • Validate Xrefs, custom resource paths and startup LISP files or plugins.

System checks
  • Set the Windows power plan to High Performance or Best Performance.
  • Monitor the CPU and RAM usage of bricscad.exe in Task Manager.
  • The C: partition must have at least 10% free space.
  • Launch BricsCAD in Safe Mode. Make sure add-ons are deactivated.
  • Boot Windows in Safe Mode to eliminate background process conflicts.

Sluggish Screen Operations (Zoom, Pan, Orbit)

When BricsCAD is slow or becomes unresponsive, its performance is influenced by CPU and/or GPU.

Understanding the CPU and GPU influence on performance:

  • Dominant scenario for CPU:
    • Typical context: the 2DWireframe visual style.
    • If slow: file complexity, background CPU load, or poor threading configuration (the _MTFLAGS system variable).
  • Dominant scenario for GPU:
    • Typical context: shaded or the 3D visual styles.
    • If slow: GPU throughput, VRAM pressure, or heavy visual style settings.

Common Causes

  • Multi-threading not active (the _MTFLAGS system variable bits 1 and 2 are not checked).
  • Heavily mixed 2D and 3D geometry.
  • High RAM usage.
  • Resource-intensive settings for the visual rendering style.

BricsCAD checks
  • Compare performance in the 2DWireframe and the Wireframe.
  • Test the GSDEVICETYPE2D values. BricsCAD must be restarted after each change.
  • Move xlines and rays to a frozen layer where possible.
  • Test the GSDEVICETYPE3D values. BricsCAD must be restarted after each change.
  • Test the _SHADEMODE command with the _GOURAUD mode.
  • Optimize rendered visual style:
    • Set Face style to Gooch (instead of Realistic).
    • Set Lighting quality to Smooth (instead of Smoothest).
    • Set Material display to Off.
    • Set Edge Settings > Show to Isolines or None.

System checks
  • In Windows graphics settings, set BricsCAD to High performance.
  • Disconnect USB docks and connect displays directly to GPU ports.
  • Monitor RAM, GPU and CPU in Task Manager during navigation.

How to gather data for a support request

If the issues persist, create a support request that includes the following information:

  • The DWG package created with the _ETRANSMIT command.
  • Exact reproduction steps.
  • A comparison of local and network performance.
  • The CPU, RAM and GPU usage screenshots.
  • The BricsCAD version, build and OS version.
  • The GPU model and driver (copy the output of the _REDSDKINFO command from the Command line).
  • Whether the issue reproduces in BricsCAD Safe Mode or Windows Safe Mode.