Game Animation Pop and Foot-Slide Diagnosis Lab

Diagnose {{symptom}} in a {{animation_system}} running in {{engine}}. Scope: {{occurrence_scope}}.

Reproduction and evidence: {{reproduction_evidence}}

1. Separate observations from interpretation and define normal behavior with measurable or observable criteria. Request only the minimum additional capture or logs.
2. Group causes by animation data, sampling/blending, root versus character movement, transitions, IK/collision, update order, and network authority; rank by likelihood × test cost.
3. For each hypothesis, create an experiment table with expected evidence, added instrumentation, one changed variable, falsification condition, and rollback. Start with a minimal repro and binary isolation.
4. Suggest real {{engine}} visualization, logging, and profiling points. Mark unverified commands or APIs as requiring verification.
5. For the three likeliest causes, separate minimal fix, quality-first fix, and architectural fix, including side effects and rollback.
6. Provide regression tests for the same symptom, adjacent transitions, low FPS, other terrain, and latency, plus a before/after evidence template.

Shared execution rules
- First restate the inputs and selectors as a work contract; label unresolved details as explicit assumptions.
- Prefer current official documentation for engine features and separate fact, inference, and recommendation. If browsing is unavailable, do not claim recency.
- Respond in the order analysis → architecture → deliverable → verification table, with testable acceptance criteria for every section.
- Do not copy protected characters, games, or a studio's distinctive expression. Generated video and images are production references, not engine-ready assets.
- Rights, rigging, collision, root motion, networking, performance, and accessibility require human validation in the actual engine and target hardware. Never invent measurements or APIs.