MOTIONLLM ASSISTANT / 12
Troubleshooting
Resolve connection, prompt, constraint, retarget, bake and save problems without losing valid outputs.
Connection and cloud access#
| Symptom | What to check |
|---|---|
| Plugin panel is missing | Check that MotionLLMAssistant is enabled, restart the editor and resolve any module/version error. Open Window → MotionLLMAssistant. |
| Sign-in does not complete | Start a fresh sign-in from the panel, use the intended account and authorize that connection in the browser. An expired request needs a new connection. |
| Account connects but generation is unavailable | Check your credit balance, account standing and the error shown in the plugin. Refresh the connection, then contact support with the job ID and error if the issue continues. |
| Credits are missing | Check that the plugin and web portal use the same account, then Refresh connection and credits. |
| Waiting for GPU | After a long period without server use, a worker that shut down due to inactivity may take several minutes to start again. This cold-start delay is not required for every generation. Read the phase and job ID rather than repeatedly submitting. |
| Balance ran out before the job started | Jobs execute sequentially per account. Check the latest balance and retry only after resolving the balance requirement. |
Prompt and constraint validation#
| Symptom | What to check |
|---|---|
| Overlapping prompt sections | Remove overlaps within the scope you are generating. Use the row action when you intend to generate only one row. |
| Invalid duration / invalid job request | Use 2–10 seconds per plugin prompt section and at most 30 seconds per cloud block. Check prompt length and generation settings. |
| Constraint outside every prompt block | Move the captured key inside the relevant prompt range, before the end boundary, or remove it. |
| Key has no captured payload | Use Edit XY for a Root 2D point or Capture Pose for a Full Body key. |
| Stale or unsupported pose snapshot | Recapture the pose using the current retarget pair. Recreate unsupported old Root 2D waypoints. |
| Smooth Path disagreement | Set the same Smooth Path value on all Root 2D tracks contributing to the block. |
| No active rig / ambiguous capture | Activate the intended rig section at that frame. Use Capture from Existing Control Rig when multiple rigs are active. |
Retarget, playback and saving#
| Symptom | What to check |
|---|---|
| Skeleton mismatch | The character binding must use the effective forward retargeter’s target Skeleton. Verify source and target preview meshes. |
| Full Body reverse-pair error | The reverse retargeter must resolve the exact forward mesh pair in the opposite direction. Recapture after correcting it. |
| Animation appears unchanged | Check the active animation section, playback range and active Control Rig tracks. Deactivate authoring rigs when reviewing generated Skeletal Animation. |
| Control Rig bake failed | Verify rig compatibility and Backwards Solve. Preserve the generated AnimSequence and retry with Bake Control Rig after fixing the rig. |
| Download succeeded but import failed | Read Pipeline Stage and Output Log. A valid cloud result may exist even though Unreal import failed; do not assume another generation is needed. |
| Asset or sequence save failed | Check output-folder permissions, read-only assets and source-control checkout. Retain any assets already written by earlier stages. |
Collect a useful problem report#
- Plugin package and Unreal Editor version.
- The action you ran and whether it was a row or aggregate generation.
- Job ID, pipeline stage and the exact error message.
- Prompt durations and the relevant retarget/rig asset names.
- A short relevant Output Log excerpt and steps to reproduce.
Do not include authentication tokens, passwords or private credentials. For a pose problem, also explain which rig was active and whether the key was recaptured after your last edit.