ACTUSERINPUT command in AutoCAD : Pauses for user input in an action macro

If you’re using AutoCAD’s Action Recorder to automate repetitive tasks, the ACTUSERINPUT step lets a recorded macro pause and request user input at runtime. This guide explains what the ACTUSERINPUT command is, how to use it step‑by‑step, common reasons it may fail, practical alternatives, troubleshooting fixes, and optimization tips for reliable automation.

What is the ACTUSERINPUT command?

ACTUSERINPUT is an action macro step in AutoCAD’s Action Recorder that pauses a macro and waits for the user to provide input before the macro continues. The input can be:

• a picked point,
• a selected object or objects,
• a typed value (length, angle, number),
• or another interactive response required by a command.

Use ACTUSERINPUT when you want a macro to run most of its steps automatically but still allow the operator to supply one or more interactive pieces of data during playback.

Why and when to use ACTUSERINPUT

• To record automation that still requires a human decision (for example: choose an insertion point or select a target object).
• To build flexible macros that work across different drawings where a fixed coordinate or object cannot be predetermined.
• To combine automation speed with occasional manual control for precision or judgment calls.

How ACTUSERINPUT works (high-level)

1. You record an action macro using the Action Recorder.
2. During recording, insert an ACTUSERINPUT step at the moment you want the macro to stop for user input.
3. Save the macro. When you play back the macro, it will run until the ACTUSERINPUT step, then display the same prompt (or wait for the same type of input) you originally provided during recording.
4. After the user provides the input, the macro continues with its remaining steps.

Step-by-step: Using ACTUSERINPUT in AutoCAD

1. Open Action Recorder: Ribbon > Manage tab > Action Recorder panel > Record (or type ACTRECORD if available).
2. Begin recording and perform the automated steps you want before the user input.
3. When you reach the point that should be interactive:
   • Insert the action or record the interactive command that requires a response (click a point, select an object, enter a value).
   • The recorder will capture that interaction as a user input step (often logged as ACTUSERINPUT).
4. Finish the remaining steps of your macro and stop recording.
5. Name and save the macro in the Action Recorder list.
6. To run the macro, choose it from the Action Recorder list and click Play. When the macro reaches the ACTUSERINPUT step it will pause and prompt you to supply the required input.
7. Provide the input (click/select/type) and the macro continues.

Shortcut tip: There is no universal built‑in keyboard shortcut specifically for ACTUSERINPUT. To speed usage:

• Create a custom Action Recorder toolbar button or ribbon button for your macro.
• Or create a Command alias in acad.pgp to launch the macro (for example add an alias like AMY to run your action macro). This provides a one‑key command to start playback.

Examples (simple scenarios)

Example A — Insert and prompt for insertion point:

• Record: Start recording → Insert block (choose block) → When prompted for insertion point, pick a point (this is recorded as a user input) → Finish → Save macro.
• Playback: Macro inserts the chosen block and pauses at insertion point for the user to pick the actual point.

Example B — Copy with user-selected base point:

• Record: Start recording → COPY command → Select source object(s) → When prompted for base point, pick point (ACTUSERINPUT) → Specify second point (recorded as follow-up) → Stop recording.
• Playback: Macro selects object(s) automatically and then asks you to pick the base point.

Common reasons ACTUSERINPUT doesn’t work and fixes

1. Macro plays but does not pause for input

   • Cause: The recorder recorded a non‑interactive value (hard-coded coordinates) rather than a user prompt.
   • Fix: Re-record the step ensuring you deliberately use an interactive selection or click the point when recording so it is captured as user input.

2. Prompts appear but clicks are ignored

   • Cause: A variable or system setting is suppressing dialogs or interactive prompts (for example, CMDDIA, FILEDIA, or dynamic input settings).
   • Fix: Ensure CMDDIA = 1 (dialog prompts enabled) and check DYNMODE and PICKFIRST are set appropriately. Restore defaults if unsure.

3. Macro fails on objects that don’t exist or layers are locked

   • Cause: The macro depends on specific layers, blocks, or object names not present in the current drawing.
   • Fix: Use more generic selections or add pre‑checks in your workflow. Keep source drawings consistent with the objects expected by the macro.

4. Different units, scale, or UCS causes wrong results

   • Cause: Recorded coordinates or scale‑dependent steps don’t match the target drawing’s units or UCS.
   • Fix: Use relative user input (pick points during playback) rather than hard-coded absolute coordinates; standardize unit settings, or include a UCS switch in the macro.

5. Macro blocked by security or version incompatibility

   • Cause: Action macros or customization may be restricted by company policy or not compatible across AutoCAD versions.
   • Fix: Check AutoCAD product documentation, trust settings, or re‑record macros in the target AutoCAD version. Confirm Action Recorder is supported in your AutoCAD product (some limited/alternate versions may not support it).

6. ACTUSERINPUT unavailable in scripts or non‑interactive run modes

   • Cause: Script execution or automated batch processing typically runs non‑interactively and won’t stop for user prompts.
   • Fix: Use scripting only for fully automated steps; for interactive steps, run macros manually or use an AutoLISP/.NET routine that explicitly prompts and waits.

Alternative methods to get user input in automation

• AutoLISP: Use functions like getpoint, getint, getstring, entsel to prompt and capture input with full control. Best for advanced/customized automation.
• .NET / VBA: Create custom commands with explicit user prompts and richer UI.
• dynamic blocks & Parameters: For repeated geometry adjustments that users can change without macros.
• Fields & Attributes: Use Block attributes or fields for predefined input that can be edited manually at insertion.
• Script files (.scr): Use when you have a fully predictable, non‑interactive sequence (no ACTUSERINPUT).
• Action Macro with precondition checks: Use small helper macros or prompts before running a larger macro to set context.

Tips to create reliable ACTUSERINPUT macros

• Record macros in a clean test drawing to isolate the actions you want captured.
• Use descriptive names for macros and include version notes (so you know what the macro expects).
• Test macros across a few target drawings to confirm prompts and object availability.
• Avoid hard-coded coordinates when possible — favor recorded user picks or relative steps.
• Keep one macro purpose‑specific rather than mixing many unrelated operations into a single macro.
• If you need custom prompts or logic, consider converting the macro to an AutoLISP or .NET routine for greater control.

FAQ

Can I customize the prompt message shown during ACTUSERINPUT?

Yes and no. The Action Recorder reproduces the prompt generated by the original command recorded. You cannot directly set a custom message string from the Action Recorder interface. For fully customized prompt text, use AutoLISP or a .NET/VBA routine where you control the message shown to the user.

Does ACTUSERINPUT work in AutoCAD LT?

Action Recorder availability can vary by product and version. AutoCAD LT historically has limited customization compared with full AutoCAD. Check your product documentation—if Action Recorder or macros are not available, use supported alternatives (manual steps, block attributes, or templates).

Can I use ACTUSERINPUT in a script (.scr) or batch file?

No. Script files run non‑interactively and do not pause for user prompts. If you need interactive pauses, run the macro manually or use a macro that begins playback and includes ACTUSERINPUT steps.

How can I debug a macro that fails during ACTUSERINPUT?

Run the macro step‑by‑step on a test drawing. Re-record the problematic step ensuring you actually perform the interactive pick or selection. Check system variables (CMDDIA, PICKFIRST, DYNMODE) and make sure required objects/layers exist.

Is there a way to create a keyboard shortcut to run an action macro with ACTUSERINPUT?

Yes. Create a command alias in acad.pgp, or add the action macro to the ribbon/quick access toolbar. The alias can launch the macro with a short command name; toolbar or ribbon buttons provide one‑click access.

Can ACTUSERINPUT accept multiple inputs (e.g., pick multiple points)?

Yes if the recorded command originally required multiple inputs and those interactions were recorded as user inputs. The macro will pause for each recorded input in sequence and resume after each is provided.

Bolded throughout this guide are the key commands and concepts to help Google and users quickly find and act on the most important information: ACTUSERINPUT, Action Recorder, record, playback, CMDDIA, AutoLISP, and macro. Use the steps and troubleshooting checks above to build dependable, interactive automation in AutoCAD.