Effect packs and the Xbox / PC effect comparison

Question tested: “the PC port is missing particle effects the Xbox has, perhaps a whole subtle layer on every effect”. Answer: no missing files, elements, element kinds or shaders; one proven PC-port loss (the point-sprite layer mseftbb01s of nine shot effects is drawn far too small on the PC), and one finding about our own pipeline (we convert the wrong effect files). Confidence H unless marked.

Effect packs (Effect/e.i, Effect/a0.e .. a7.e)

Read by converter/effectpack.py (list, extract; synthetic test in tests/test_effectpack.py).

File Layout
e.i u16 pack count (8), u16 entry count (496), then 12-byte entries sorted by effect id: u16 effect id, u16 pack number N, u32 offset in aN.e, u32 size
aN.e the entries back to back. One entry = the effect’s ALR (same layout as a loose effect .alr), zero padding, and the 412-byte slot file (the .eft) starting 0x800 bytes before the end of the entry

Ids in the index: 1–321, 512, 518–521, 600–606, 700, 701, 1001–1024, 71 ids in 2001+, 16 in 3001+, 31 in 4001+, 19 in 5001+.

Load path (PC). Load by id 0x14018cd10 → pack opener 0x14018d0b0 → binary search over the index 0x14018c4e0 (index object pointer at 0x1405bb2e8; entry count u16 at +0x8A, table at +0x8C) → the pack name is built from the pack number, offset and size go to the effect record’s +0x58 / +0x5C, and the slot-file pointer is buffer + size − 0x800. A missing id is not checked. The per-effect file-name templates in the executable are only default names copied into the 0x88-byte effect records (init 0x14018c940, reset 0x14018cfe0); no code path opening a loose effect file was found. The Xbox executable has the same strings and the same pack loader, and the disc has no loose effect files at all.

The loose eftNNNN.alr / .eft files of the PC build are an older revision that the game never opens. Compared per id with the pack entry (parsed materials, joints, elements, mesh data): 121 same-numbered effects match, 415 differ, in both directions (effect 4, model 0: 103 elements in the pack, 39 loose). Element kinds over all effects:

Kind Packs (played) Loose (not played)
mesh 22558 14719
particle01 / particle02 1182 / 406 1620 / 342
msparticle00 / msparticle01 286 / 977 291 / 626
light01 / light02 0 / 660 8 / 511
flair01 102 100
tale01 / tale02 90 / 1 100 / 0
thunder01 53 0
blade01 / blade02 4 / 12 6 / 14
msbillbeam00 / ykfade00 6 / 2 3 / 2

Only in the packs: ids 302–321 and all of 3001+ / 4001+. Only loose: 0, 501, 502, 505–511, 513–517, 522–550. Every count of effect elements elsewhere in this file and in PLACEHOLDERS.md that was taken with effectconv.py --stats over the loose files describes the older revision.

Xbox packs against PC packs

Effect code, Xbox against PC

Point-sprite meshes: shader mseftbb01s — proven PC-port loss

A “mesh” element whose material shader is mseftbb01s is not drawn as a mesh. Its vertex data is a dummy quad (4 vertices, 6 indices); the element is one point sprite, batched with all others of the frame.

Footage

No recording in the reference library shows any of the nine skills on either platform (the library has one fire shot only), so the on-screen result was not compared. Capture request, to locate only: skill records 42 and 53 (one multishot, one straight shot), Palace, cast at a dummy 5–10 m away with the camera behind the caster, 10 s each, once in xemu and once in the PC build; then one cast seen from the side at about 3 m. Expected: soft additive dots along the shot in xemu, none (or single-pixel dots) on the PC.

Not compared in this run

The draws of msparticle00 / 01 (1263 elements), thunder01, tale02, flair01, the blades and the full-screen filter; point-size limits and the other render states the PC’s layer over the Xbox draw calls may map differently; the per-frame behaviour of the frame copy used by the haze. The element data and the update code names are equal; a difference could only be in a draw translation like the one above.

Implementation notes for the rebuild

  1. Convert effects from the packs (built effects1: effectconv.py --pack <Effect dir> all <out root> [--pdconv <bin>] writes eftNNNN/effect.json + textures per pack id, reading the slot file through structs). effectpack.py extract <Effect dir> <id> <out> gives the .alr / .eft pair effectconv.py and pdconv --textures already read; the PC packs hold row-ordered textures (format byte bit 0x80), so no un-swizzle is needed when the PC copy is the source. Convert all 496 ids; stop using the loose files. Expect new element kinds in the output (thunder01, tale02) and different element counts in most effects; re-run effectconv.py --stats on extracted packs before trusting any count.
  2. Draw mseftbb01s elements as point sprites, not as meshes: one camera-facing square per element at the element’s world position, textured with the material’s texture × the element colour, the material’s blend; no mesh, no rotation.
  3. Size (Xbox look, the target): height in pixels on a 480-line screen = 5000 × s / w, s = min(1, 2 L²), L = the element matrix’s X-axis length, w = view depth in game units; scale by screen height / 480. That is a world-space square of side 5000 × s / 480 × 2 tan(vertical fov / 2) game units at any depth — a constant world size, so a plain billboard quad of that side does it. Limit to 64 px × (screen height / 480) for the console look.
  4. PC look (if ever wanted for comparison): divide the size once more by w.
  5. Fixes the statements in “Skill effects” (the loader does not open loose files) and “Xbox capsule shading” (what differs in the .e files).