# Text pose sequences

[Open the channel viewer](index.html).

The reference disc ships 110 `.ROT` files in `3DDATA`. They contain whitespace-separated ASCII integers. The first line begins with a signature, followed by either three or four integers. Its first integer is the number of frame rows. Every file matches that declared count, and each file has a consistent number of channels per row.

| Signature | Files | Channels per frame |
| --- | ---: | ---: |
| `HI` | 69 | 27 |
| `HC` | 17 | 27 |
| `HS` | 10 | 27 |
| `IC` | 4 | 29 |
| `II` | 2 | 29 |
| `GI` | 3 | 26 |
| `GC` | 2 | 26 or 14 |
| `S` | 2 | 24 |
| `I` | 1 | 24 |

For example, `AQUIRE.ROT` starts `HI 9 1410 0`, followed by nine rows of 27 integers. `WAIT.ROT` starts `GC 2 1000 0 2`, followed by two rows of 14 integers. The remaining header integers are duration in milliseconds and motion speed. Non-H formats also store a component count. [The editor trace](loader-trace.md) identifies the body, arms, legs, feet and held-weapon channels. The viewer shows the original editor figure, the animation timeline and the raw values.

## Connection to Apache

The animated figure shown here belongs to MANEDIT's preview window. It does not appear in Apache's missions, and the January 1998 software engine does not use the shipped `.ROT` sequences.

The model archive separately contains `TestMan` (640, with LODs 731 and 855), Russian soldiers (916–918), and US infantry (984–989). Their original actor-header entries have class and flags both zero, with no weapons or ammunition configured. None has a placement in the four terrain maps, any of the 110 loaded mission scenes, or the formation uses recorded in `models/usage.json`. These unused archive models are distinct from the nineteen-part preview figure constructed inside MANEDIT.

The reference game executable has no `.ROT` filename extension or MANEDIT reference. Its retained source-unit and symbol names contain no human pose-loader or joint-animation subsystem. The supplied `MANEDIT.EXE` has the `.ROT` loader, saver and figure constructor traced in [loader-trace.md](loader-trace.md).

These files belong to Digital Integration's shared development work. Hind's demo ships the identical editor and 79 byte-identical pose files, and its engine loads 54 of those sequences for its infantry. [The Hind connection](hind-connection.md) records the file comparison, runtime loader and contemporary accounts. `3DDATA/RGB` is a DOS directory listing of `E:\HIND\3DDATA` containing entries dated 13 March 1996.

Evidence: `models/index.json`, `models/drone-headers.json`, `models/usage.json`, `models/catalogue.json`, and `executables/6ee5028c9ede0f3b.symbols.json`.

## Extraction and verification

`tools/poses.py` records exact file hashes, duplicate groups, headers, all frame values and channel ranges. Source files are preserved unchanged.

The bundled MANEDIT executable is identical across all six supplied copies, including the Hind demo. Its constructor builds nineteen parts directly in code; no separate figure model is loaded. Type I is a single motion, C is cyclic and S is the editor's split-cycle mode. Playback uses each file's duration. Six files use the newer II/IC format, which this MANEDIT version does not accept; they retain the channel-table view.

`tools/native_manedit.py` exports the generated geometry and checks 104 supported files at ten times each against the original instructions. `node tools/check_pose_viewer.mjs` compares the browser's interpolation and rotation matrices with 312 original samples. `tools/check_pose_browser.cjs` checks every entry and the playback controls in a local browser.