Troubleshooting
Start with the tray icon: its tooltip says what state Input.Observer is in (The tray icon), and the console's System section says what went wrong (Where to look).
Nothing happens when I draw a gesture
No trail appears and the button behaves as if Input.Observer weren't there.
| Cause | How to tell | Fix |
|---|---|---|
| Input.Observer isn't running | No tray icon (check the hidden icons too) | Start Input.Observer from the Start menu (It doesn't start) |
| It is switched off | Tooltip "i.o - disabled" | Tick Enabled in the tray menu |
| The program in front pauses everything | Tooltip "i.o - auto-disabled (…)" naming the group | That app group has Pause everything while focused on (App groups) |
| The window is in an ignore group | Only in some programs | Check Ignore groups (Ignore groups) |
| Safe Mode | Tooltip "i.o - Safe Mode (restart to resume normal operation)" | Restart Input.Observer without holding Ctrl (Safe Mode) |
| The stop-all hotkey was pressed, or too many actions ran at once | Everything stopped at once, hotkeys too | Choose Reload Config from the tray menu (General) |
| You held an ignored modifier key | Happens only while you hold Ctrl (the default) | That is what the key is for (General) |
| You used a button that isn't a draw button | Only the right button draws by default | Choose the buttons under Draw buttons on the General page |
| The program's app group has Draw buttons start gestures here off | Only in that group's programs; the draw key still draws there | Turn the switch on in App groups (Advanced mode), or draw with the draw key (App groups) |
| The draw key doesn't draw | On a Japanese keyboard, Caps Lock can't draw. Over a Remote Desktop or virtual machine window, the remote program may take the key | Pick another key under Draw key on the General page (The draw key) |
| The pointer is in an exclusion zone | Only in one area of the screen | Check Exclusion zones (Exclusion zones) |
| A program running as administrator is in front | Only while such a window has the focus | See Programs running as administrator |
| The window belongs to no app group and Fall back to Global is off | Only in programs without their own group | Turn Fall back to Global on (General) or add a group (Scope and fallback) |
| Another program sent it while a sandboxed program's window was in front | Only for input another program sends | See Input other programs send |
The trail draws but no action runs, or the wrong one
- Watch the hint. While you draw, the hint names the action the stroke matches. No hint means no match. Hints and messages lists when it appears.
- The stroke isn't close enough to the saved gesture. Practise it, add another example of it, or make matching more forgiving on the Gestures page (Matching).
- The action doesn't apply here. It may be in another app group, limited to some screen regions, limited to a gesture profile that isn't active, or switched off (Scope, Profiles, Regions).
- The action ran but did nothing visible. Open the console: a script that failed says why in the System section. Keys an action sends go to the window in front; Activate the window under the gesture (General) brings the window you drew over to the front first. A program running as administrator may not accept them (below).
- The gesture was cancelled. If you pause with the button held for longer than the Cancel timeout (half a second by default), the gesture is cancelled and the press goes to the window (General).
A right-click feels late or doesn't work in a program
While the right button is a draw button, Input.Observer holds each right-button press until it knows whether you are drawing. If you release it without moving more than Minimum gesture movement (5 pixels), the press and release are handed to the window as an ordinary click. So:
- Context menus open when you release the button, not when you press it. This is expected.
- Right-button dragging in a program (a game, a design program, dragging files with the right button) becomes
a gesture instead. Any of these fixes it:
- hold Ctrl (an Ignored modifier key) while you press the button;
- press the button and hold the pointer still for the Cancel timeout (half a second by default) before you drag: the press is then handed to the program;
- put the program in an ignore group (Keep a program out), or ignore it only while it runs full screen (Ignore groups).
- Remote desktop and virtual machine windows (Remote Desktop, Hyper-V, VMware, VirtualBox, TeamViewer, AnyDesk, Parsec) are ignored by the starter set, so the computer inside gets the right button untouched.
A hotkey doesn't fire
- Another program already uses the key combination. A hotkey reserved with Windows can be held by only one program. The action shows "Windows or another program already uses these keys". Choose another combination, or close the other program and choose Reload Config from the tray menu (Hotkeys).
- The hotkey belongs to another app group. It works only in windows of its group (or everywhere, from Global, unless a group overrides it).
- The hotkey uses the draw key. Where gestures work, pressing the draw key starts a gesture instead, so the hotkey runs only where gestures don't. The action shows This key is the draw key. Choose another key, or another draw key on the General page.
- The window in front is ignored or pauses everything.
- A gesture, a macro recording or gesture training is in progress. Hotkeys don't fire during them. The stop-all hotkey is the exception: it always works.
- The window in front runs as administrator (below).
- Another program sent the keys while a sandboxed program's window was in front (below).
- Safe Mode, or Input.Observer is switched off. No hotkeys are registered then.
Text expansion doesn't fire in a program
- Text expansion is off, or the key that should end the abbreviation (Space, Tab, Enter or a punctuation mark) isn't enabled: see the Settings tab of Text expansion (Text expansion).
- The abbreviation contains a period, comma, exclamation mark or question mark while Expand on punctuation is on: that mark ends it. Turn the setting off on the Settings tab.
- The abbreviation belongs to another app group, or the window is ignored.
- The program runs as administrator (below).
- A Japanese, Chinese or Korean input method is turned on. Text doesn't expand while it is; switch it to direct input (Text expansion).
- The text comes out scrambled or with characters missing. Raise Typing delay on the Scripts page (Script settings).
Programs running as administrator
Windows keeps ordinary programs from reading input to, or controlling, a program that runs as administrator. Installed with its setup program and started from its installation folder, Input.Observer is allowed to work with such programs. A copy started from anywhere else is not: while a program running as administrator has the keyboard focus, gestures don't start, keys you type there don't reach Input.Observer (so text expansion and some hotkeys don't fire), and actions can't send keys or clicks into it. The tray icon's menu may not open either.
- The System section of the console names each such program once per run, the first time it comes to the front.
- Click the taskbar or any ordinary window, and Input.Observer works again.
- To work with administrator programs, install Input.Observer with its setup program and start it from the Start menu. A portable copy always has this limit.
Input other programs send
Gestures, hotkeys and abbreviations that another program sends for you — AutoHotkey, a keyboard-and-mouse sharing program, a remote-control program — work like your own. The exception is while a window of a sandboxed program (one Windows runs with fewer rights than your ordinary programs) is in front: then Input.Observer passes input that programs send straight on to that window, so a sandboxed program can't use it to run your actions. Your own mouse and keyboard always work. Click an ordinary window, and input from other programs works again.
Input.Observer doesn't start
| What you see | Cause | Fix |
|---|---|---|
| "Input.Observer is already running." | Another copy runs in your session. | Look for its icon in the notification area. |
| The password prompt, then nothing after Cancel | Your configuration is protected; it can't start without the password. | Start it again and enter the password (Security). |
| "Input.Observer can't load your configuration" | The configuration file is broken or missing. | Choose one of the dialog's options (Recovery). |
| The license agreement, then nothing after Decline | The agreement must be accepted. | Start again and choose I accept (About and license). |
| "Your 30-day trial has ended." | The trial is over. | Enter a license key, or choose Exit (About and license). |
| A message naming a Windows version | Input.Observer needs Windows 10 version 1809 or later. | Update Windows. |
| Windows protected your PC, for a portable copy | The portable programs aren't signed. | Choose More info, then Run anyway (Portable copy). |
| It starts, then something in your configuration hangs or misbehaves at once | A Config loaded event or an action | Start in Safe Mode and fix it (Safe Mode). |
The configuration window can't connect
The configuration window needs Input.Observer running.
- "Input.Observer isn't running" when you open it: start Input.Observer, then open the window from its tray icon.
- "The configuration window couldn't connect to Input.Observer": Input.Observer didn't answer. Choose Try again once it runs.
- "Engine not reachable — retrying" in the window's status bar: Input.Observer stopped answering while the window was open. Your edits stay; saving is unavailable until it answers again, and the window keeps trying. If you close the window meanwhile with unsaved changes, Save to file… keeps them in a file you can refer to later; it can't be imported.
- A configuration file larger than 8 MB can't be opened in the window; Input.Observer warns about it at startup.
A plugin doesn't start, or the trail looks plain
- The Appearance page says at the top when the renderer isn't drawing and why, with Restart when it stopped (Appearance). Meanwhile the classic trail, hint and message window draw.
- On the Plugins page (Advanced mode), check the plugin's status. Not in use is normal for a drawing plugin that isn't the renderer. Auto-disabled -- failed to start and Closed by the plugin need Retry (Plugins).
- No plugin runs in Safe Mode.
- A style you chose draws Neon glow instead: the style is locked, for example because the license changed (Appearance).
Drawing makes a full-screen game or video stutter
Turn on Keep the drawing layer behind windows between gestures — in Customize… for the Styles plugin, or on the Trail options tab for the classic line — or put the game in an ignore group that applies only while it runs full screen (Keeping trails light).
Safe Mode
Safe Mode starts Input.Observer with nothing that could cause trouble running, so you can fix your configuration.
- Exit Input.Observer (tray menu, Exit).
- Hold Ctrl while you start it, and keep holding until "Start Input.Observer in Safe Mode?" appears.
- Choose Yes.
In Safe Mode there are no gestures, hotkeys or text expansion, no plugins, and none of your actions or Config loaded / Engine shutting down scripts run. You are still asked for your password and license as usual. The tray icon shows Safe Mode, and the configuration window works normally, so you can change whatever caused the problem and save it. Scripts you run yourself in the console's Script section do run.
Safe Mode lasts until Input.Observer restarts; holding Ctrl at startup is the only way in.
Recovering from a bad change
- Still in the configuration window: Discard puts back everything since the window opened, including changes you already applied.
- An action is running wild: press the stop-all hotkey, Ctrl+Shift+Alt+F9 by default (General). Then fix the action and choose Reload Config.
- It misbehaves as soon as it starts: use Safe Mode.
- Go back to an earlier configuration: restore a copy from the
Backupfolder (Backups). - You edited
config.tomlby hand and Reload Config shows Configuration Not Reloaded: the previous configuration is still in effect. The message says why: a mistake at a given line and column, a file that can't be opened, a file protected with a password, or a pointer to a file that doesn't exist (Reload Config, Editing the file by hand).
Where to look
- The console's System section (tray menu, Show Console) lists what the engine noticed: problems in your configuration, actions and scripts that failed and why, the renderer being unavailable. Lines that arrived while the console was closed are shown when you open it (Console).
- The configuration window shows "n notes from the engine about this configuration" above the save bar, with Show, whenever Input.Observer repaired or has advice about your configuration.
- What your scripts print with
UtilityPrintis in the console's User section. - Input.Observer writes no log files. For a bug report, copy the version from the About page (Copy) and the console's text. When that isn't enough to find the cause, support may ask you for a trace (Recording a trace).
Recording a trace
A trace is a detailed record of what the engine decides while you reproduce a problem: why a press started a
gesture or was passed to the window, which action matched, what a script did, why a plugin stopped. The setup
program installs a second copy of the engine for this, Input.Observer.Trace.exe, next to Input.Observer.exe; a
portable copy gets it from the Extras ZIP. It uses your configuration, license and plugins, and works
like Input.Observer in every other way.
- Exit Input.Observer (tray menu, Exit). Only one copy can run at a time.
- Open the installation folder,
C:\Program Files\Input.Observer(for a portable copy, its own folder), and startInput.Observer.Trace.exe. - In i.o - Trace Categories, choose the areas to record, then OK. The first time, every area except Input Hooks (very detailed) is ticked; keep that unless support names other areas. The window remembers your choice for the next run.
- Reproduce the problem. Note the time, so the lines that matter are easy to find.
- Exit the trace copy (tray menu, Exit), and start Input.Observer again from the Start menu.
Each run writes a file, Trace-<date>-<time>.log, in the Logs folder next to your configuration file
(%APPDATA%\Input.Observer\Logs unless you moved it: The configuration file). The file starts
with a short summary for support: the Input.Observer and Windows versions, the display language, whether it runs
as administrator, where the configuration is, and the areas recorded. When a file reaches 50 MB, the run
continues in Trace-<date>-<time>-2.log, then -3, and so on.
- Pick only the areas you need. Input Hooks (very detailed) records every mouse movement and every key you press, including what you type into password boxes. Tick it only when support asks for it, and don't type anything private while it records.
- Never in a trace without Input Hooks: passwords you give Input.Observer, license keys, the text that text expansion types or replaces, clipboard contents, the titles of other programs' windows. Program names and window class names are recorded.
- Check before you share. A trace is plain text. File paths in it include your Windows user name, and the names of your actions, app groups and scripts appear in it. Read it, and remove anything you'd rather not share, before you post or send it.
- It stays on your PC. Nothing is sent anywhere; the files are yours to delete. The
Logsfolder keeps the 20 newest trace files: when a new one starts, the oldest are deleted, so copy a trace elsewhere to keep it. - Skip the window next time: clear Show this window at every launch, and the trace copy records the same
areas at every start. To see the window again, delete
trace.toml, next to the configuration file. - Don't keep it running. The trace copy works normally, but writes to disk all the time, and with Input Hooks (very detailed) ticked it fills file after file quickly. Start with Windows always starts the ordinary copy.