AutoCAD Core Console batch processing

For a reference to each control, see BatchDraft settings, including worker limits, timeout behavior and log retention.

AutoCAD Core Console is the primary AutoCAD execution path in BatchDraft. It runs the selected drawing work without the full AutoCAD window. BatchDraft launches and supervises the CAD processes, applies the configured timeout and retry settings, and records drawing-level outcomes.

Select the correct executable

Open Settings, select AutoCAD / Headless, and use Detect installed versions. Choose the installed AutoCAD product you intend to automate. If you browse manually, select its genuine accoreconsole.exe.

DWG TrueView alone is not a supported automation runtime. BatchDraft’s release evidence covers AutoCAD LT 2026 Core Console; other valid AutoCAD/Core Console installations can be selected but have less recorded real-run coverage.

Understand headless limitations

Core Console cannot answer desktop dialogs or make interactive selections for you. A CAD command may need its command-line variant and an explicit response for every prompt. A routine that depends on desktop-only document automation, including some ActiveX/COM behavior, needs compatibility checking in the selected host.

Test your routine with representative disposable drawings before an unattended batch. Detected commands identifies callable definitions; it does not certify their compatibility.

Keep SECURELOAD on Respect AutoCAD unless you understand the alternative. Use reviewed scripts in locations permitted by your AutoCAD policy. The optional relaxation setting applies only to a runner-owned isolated Core Console profile; it is not a reason to run untrusted files or weaken your normal profile.

Configure parallel processing

In Settings → Execution, configure the parallel worker count, maximum retries, no-progress warning and hard timeout. Save your settings.

Each active Core Console worker handles a drawing attempt in its own process. Several drawings in one batch can therefore run concurrently. Choose a worker count that fits your drawings and workstation resources, and inspect the outputs of an initial small run.

A warning about no progress is useful evidence to investigate. Simply increasing a timeout will not resolve a command that is waiting for a dialog or an omitted prompt response.

Compare execution modes

Mode in the published trial	Behavior and current evidence
AutoCAD / Headless	Uses accoreconsole.exe. Configurable parallel workers. Recorded installed-runtime evidence covers AutoCAD LT 2026 Core Console.
AutoCAD / Windowed	Uses the desktop AutoCAD host. One worker. Experimental; it does not have the same acceptance status as Core Console.
BricsCAD / Headless	Uses the installed desktop host with its window hidden through /Automation. Configurable workers in Trial 0.2.0. Focused V26 engine evidence; verify individual routines separately.
BricsCAD / Windowed	Uses the visible BricsCAD host. One worker. Focused V26 evidence.

BricsCAD headless mode is not a separate console executable. BatchDraft keeps the host selection explicit and does not silently fall back to a different application or mode.

Check failures at drawing level

Use History to select the failed drawing and its attempt. Review readable output first, then raw logs when you need complete retained evidence. Check the last command and expected prompt response, the output mode and destination, and any reported save or validation issue.

Continue with troubleshooting for common symptoms, or build an AutoLISP batch once the runtime is configured.