Open questions

What are records 0 (38.9 MB) and 1120 (1.4 MB)? Both have flat entropy near 8 bits per byte, no known signature, and no code that loads them.

What codec do the FMV records (47 to 74) use, and the title-screen images in records 105, 106 and 116?

Do raw (unflipped) custom sound banks and alias records, which point two index entries at the same sectors, work in game? Both follow from the code but neither has been tried.

Does anything other than the request routine read the per-kind size caps? If not, they protect nothing.

What do tables T7, T9, T12, T14 and T16 to T19 hold?

Where are hit boxes and hurt boxes defined? No condition opcode reads them; the T1 action table and T7 are the candidates.

What do the special transition inputs 0x8001 and 0x8002 mean?

Does a maximum-size moveset load for player 2 in the versus and arcade layout, not just in Practice?

Does a transplanted moveset survive throws and being hit, and does it work as player 2?

Is there juggle damage scaling? The notes show the claim that there is none was never established.

What do floor flags 0x2000, 0x8000, 0x10000 and 0x4000 do? The current reading is camera-only floors and a camera ceiling, but it’s untested.

What are the stage file’s section 5 (hittable objects) and section 12 (a packed motion-bank container) for?

What do the per-node extra fields mean? Copying them from a node with the wanted behaviour works; zeroing them has never been tried.

Why does rebuilding a stage’s texture uploads from scratch hang the stage load, when replacing them in place works?

Can a stage’s textures use more than the 6,552-block window the stock stages fit in?

Can stages 18 to 25 be made selectable? Their table entries exist, but the select-card picture file can’t grow.

Which moves and game events request which sound ids?

What code plays the announcer clips and the fighters’ main-memory sound clips?

Does a longer announcer clip work, or only one of the same length?

Is sound memory above 0x1B2E10 free, or part of the reverb work area?

Does the project’s ADPCM encoder match real hardware? Its rounding comes from references and hasn’t been checked against a console.

Do the in-game results sound right? None of them has been listened to.

How are animation clips encoded, and which of the 23 animated bones drives which skeleton joint?

Where are hit boxes and hurt boxes defined, and what do the remaining moveset tables hold?

Are the stock fighters’ memory overruns as player 2 harmless in versus and arcade modes?

Can the 20-cell select grid grow, so that more than one new fighter fits?

What does the vector-unit microcode expect, so that models can gain vertices and bones?

Where in the executable is there room for new code?

What codec do the videos and title images use, and what are records 0 and 1120?

Where does the stage size really fail above 7.7 MB? The region the stage sits in is 8,146,528 bytes, so the limit lies somewhere between.

What does losing the pose cache and shrinking buffer B cost in frame rate, and what does each buffer do?

What do the limit table’s two distance values (X and Y) control?

What do the bone table’s fields mean, and which skeleton bone does each per-mesh palette slot stand for? Nothing in the model file links the two. The planned route is a dump of vector-unit memory mid-fight.

Are 144 vertices per block and 20 matrices per palette hardware limits, or just the largest values Namco used?

What would it take to add vertices, meshes or bones, which needs the vector-unit microcode understood?

What exactly are model sections 6, 9 and 16? Their structure is known; their roles (collision volumes, a hair and cloth chain, an energy-ring effect) are inferred.

Can the same driver be generalised into a reusable harness for other PS2 games?

Should evidence status be tracked per claim inside an entry, rather than once per entry?

Should an AI hypothesis that a person has examined, but not yet tested, get a status of its own?