Troubleshooting

Common problems, log files, and what to include in a bug report.

The window opens then immediately closes

One possible cause is a failure to start the renderer, the part of the game that draws the picture. Run the program from PowerShell or Command Prompt so the error message remains visible:

Capture stderr

# PowerShell
.\LoA.exe 2>&1 | Tee-Object -FilePath last_run.log
# cmd
LoA.exe > last_run.log 2>&1

Then check the last-run log alongside logs/loa_runtime.log for the renderer startup message. It names the graphics processor, or GPU, selected by the game. A missing message can indicate a graphics-driver problem, but the log is needed before concluding that is the cause.

Black screen but the window is alive

Press F1 to force the default render mode.
Press F11 to toggle borderless fullscreen — sometimes the swapchain re-initializes.
Try moving with W to confirm input is live.
If movement works but you still see black, try F2 (wireframe). If wireframe is visible, the issue is shader-side; file a bug with the GPU model.

Chat panel won't focus

Confirm the window is focused (click into it). Background windows do not receive keyboard input.
Check that the keyboard layout is the one you expect. The / key is the literal "/" character.
If you are in pause state (Tab/Esc), unpause first.

"Intent classified as Unknown"

The classifier is deterministic and conservative — it falls through to Intent::Unknown when no rule matches. The chat scrollback will echo the normalized input so you can see what the classifier saw. Common fixes:

Use a verb the rule-table knows · see /docs/intents for the full vocabulary.
Spell room or material names from the alias tables (e.g. color, brass, qr).
Try a simpler phrasing: spawn cube at 5 5 5 instead of could you place a cube at 5 5 5 please.

Snapshots don't appear

F9 (burst) and F12 (single screenshot) write into snapshots/ next to LoA.exe. The directory is created on first capture. If you placed the binary in a write-protected location (e.g. C:\Program Files\), capture will fail silently. Move the binary to a folder you own.

Note

Administrator access is not expected

The public test build is intended to run without administrator access. If Windows asks for it, stop and confirm the file name and SHA-256 fingerprint against the download page before continuing.

Log locations

File	Purpose
`logs/loa_runtime.log`	Engine startup + per-frame anomalies + audit emissions
`logs/intent_recent.jsonl`	Up to sixteen recent requests recognized by the game
`snapshots/snap_<frame>_<ts_ms>.png`	Images captured with F9, F12, or the snapshot request

The KAN classifier seems wrong

Some development builds can use a Kolmogorov-Arnold Network (KAN), a compact mathematical model, to influence a bounded generation choice. If your build supports that experiment and you suspect it is making a poor choice, you can disable it before launch:

Disable KAN steering

# Set this env-var before launch · KAN nudge becomes a no-op,
# stage-0 fallback is exclusive. The engine still emits the
# attempted-classify audit row so you can see what KAN would have done.
$env:LOA_DISABLE_KAN_NUDGE = "1"
.\LoA.exe

How to file a useful bug

Open an issue at github.com/Apocky with:

The version (visible in the title bar; also at the top of logs/loa_runtime.log).
OS version + GPU model (Windows + the wgpu adapter line from the log).
Steps to reproduce, including any chat-panel inputs you typed.
The last ~50 lines of logs/loa_runtime.log.
(Optional) the relevant snapshot if visual.

Do not attach a log or image until you have reviewed it for private information. The normal bug-report flow requires you to choose and upload those files yourself.