BricsCAD Performance Optimization: Large Files, Hardware Acceleration, and System Tuning

BricsCAD Performance Optimization: Large Files, Hardware Acceleration, and System Tuning

BricsCAD is generally faster than AutoCAD on identical hardware, but large drawings with heavy xref chains, dense hatch patterns, and complex 3D solids can still bring it to a crawl. This guide covers every performance lever available in BricsCAD, from graphics pipeline settings to drawing hygiene practices that keep files lean.

Diagnosing Performance Bottlenecks

Before changing settings, identify what is actually slow. BricsCAD provides built-in diagnostics:

1. Type GRAPHICSCONFIG and check whether hardware acceleration is active
2. Type SYSMON to open the System Monitor panel — watch CPU and memory usage during operations
3. Type TIME to check drawing load time and regeneration time
4. Use AUDIT to detect drawing corruption that may cause performance degradation

Common Performance Killers

• Excessive hatch density — hatch patterns with spacing under 1mm generate millions of line segments
• Unresolved xrefs — broken xref paths force BricsCAD to search all support paths on every regen
• Wipeout frames — large wipeout objects with frames visible cause excessive redraw
• Annotative scaling — hundreds of annotative scales per object multiply display calculations
• Solid history — keeping solid history on complex boolean operations stores massive undo data

Graphics Pipeline Configuration

The graphics pipeline has the most immediate impact on interactive performance (panning, zooming, orbiting).

Enabling Hardware Acceleration

1. Run GRAPHICSCONFIG
2. Set Hardware Acceleration to On
3. Select the appropriate rendering engine:
   • DirectX 11 — recommended for most Windows systems, best compatibility
   • OpenGL — use if DirectX drivers are unstable; common on workstations with Quadro GPUs
   • Software — fallback only, extremely slow

Graphics System Variables

Key variables to tune:

• GSSELECTION — set to 1 to use GPU for selection highlighting (faster on large drawings)
• GSPENPALETTE — set to 1 for GPU-based pen color calculation
• VSFAKEDRAW — set to 0 to disable fake draw mode (can cause visual artifacts but may improve speed on weak GPUs)
• VSCURRENT — use 2dwireframe for large 2D drawings instead of realistic

GPU Driver Update

BricsCAD relies heavily on GPU drivers. Update to the latest stable driver from your GPU manufacturer:

• NVIDIA — use the Studio driver (not Game Ready) for stability
• AMD — use the Pro Enterprise driver for Radeon Pro cards
• Intel — use the driver from Intel's website, not the Windows Update version

After updating drivers, run 3DCONFIG and click "Check for Updates" to verify BricsCAD recognizes the new driver.

Drawing Hygiene for Large Files

Purge Unused Objects

Run PURGE with All selected, including:

• Unused blocks
• Unused layers
• Unused linetypes
• Unused text styles
• Unused dimension styles
• Orphaned anonymous blocks (check Include unnamed objects)

For automated purging, use _.-PURGE _A * _N in a script or LISP routine.

Reduce Hatch Complexity

Replace dense hatch patterns with solid fills or gradient fills where possible. A 100mm x 100mm area hatched with ANSI31 at 1mm spacing generates approximately 200 line segments. The same area with a solid fill generates one entity.

If dense hatching is required for printing, place hatch entities on a no-plot layer during editing and toggle plotting only at output time.

Manage XREF Overlays

Use XREF command to audit external references:

1. Detach unused xrefs (do not just unload — unloaded xrefs still consume memory)
2. Convert Attach to Overlay for nested references to prevent circular references
3. Use XLOADCONTROL set to 2 (demand load with copy) for faster xref loading on network drives
4. Bind xrefs only when necessary — binding increases file size and reduces editability

Audit and Repair

Run AUDIT with Y (fix errors) on any file that feels sluggish. Drawing corruption often manifests as performance degradation before visible errors appear.

After auditing, run RECOVER on the file to rebuild the drawing database index. This can significantly reduce open time for files that have been through many editing sessions.

System Variable Tuning

Display Performance Variables

• DRAGMODE — set to Auto for best balance of visual feedback and speed
• QTEXT — set to ON during editing of text-heavy drawings (displays text as bounding boxes); set to OFF before plotting
• LWDISPLAY — set to 0 (off) when lineweights are not needed for visual editing
• FILLMODE — set to 0 to disable solid fill display during editing (traces, solids, wide polylines)
• MAXSORT — increase from default 200 to 1000+ if layer dropdown sorting is slow in large drawings

Selection Performance Variables

• SELECTIONPREVIEW — set to 1 (only highlight on hover, not during window selection) for large drawings
• PICKBOX — reduce from default 3 to 2 for drawings with dense entity placement (reduces accidental multi-selects)
• PICKADD — set to 1 for predictable selection behavior
• PICKSTYLE — set to 0 to disable group selection if working with many groups

3D Performance Variables

• FACETRES — set to 0.5 during editing (lower facet density = faster display), increase to 2.0 before rendering
• DISPSILH — set to 1 to display silhouette edges of 3D solids (improves visual clarity without full rendering)
• ISOLINES — set to 0 or 2 for 3D editing (default is 4, which adds display overhead)
• REGENMODE — set to 0 for large 3D assemblies to prevent automatic regen on view changes

Memory Management

BricsCAD is a 64-bit application and can access all available RAM. However, memory fragmentation can still cause slowdowns in very long editing sessions.

Monitoring Memory Usage

Watch the System Monitor panel (SYSMON). If memory usage exceeds 80% of your total RAM:

1. Save and restart BricsCAD — this clears the undo stack and defragments memory
2. Close unused drawings — each open drawing consumes 50-200MB depending on complexity
3. Reduce UNDO levels — set UNDOCONTROL to limit stored operations

Virtual Memory (Page File)

Ensure Windows page file is set to at least 1.5x physical RAM. BricsCAD can exceed physical RAM when working with multiple large drawings, and insufficient page file space causes hard crashes rather than graceful slowdown.

Network Performance

For files stored on network shares:

1. Use XLOADCONTROL = 2 (demand load with copy) — BricsCAD creates a local copy of xrefs, reducing network traffic
2. Set XREFPATH to the network share root to avoid path resolution delays
3. Use OFFLINE mode for xrefs when editing on slow connections — BricsCAD uses the cached copy
4. Consider using BricsCAD's DWGCOMPARE on local copies rather than network originals

Conclusion

BricsCAD performance optimization comes down to three pillars: graphics pipeline configuration, drawing hygiene, and system variable tuning. Start with hardware acceleration and driver updates for immediate gains, then implement drawing cleanup practices (purge, audit, hatch optimization) for long-term file health. Finally, tune system variables to match your specific workload — 2D production drafting has different optimal settings than 3D BIM modeling. By applying these settings systematically, you can keep BricsCAD responsive even on drawings exceeding 500MB.