Issue 10: Make FBM intelligible
Status:  Accepted
Owner: ----
Project Member Reported by dammi...@hotmail.com, Nov 3, 2009
Currently the frame data of fbm is undocumented:

01A: frame input data. The format varies depending on which inputs the game
supports and may be compressed (unknown).

=(

This makes movies totally uneditable outside of rerecording. Some
documentation could help fbm be supported by something like TAS movie editor.

As with input display, the button names don't have to be descriptive,
because you would be able to figure out from the context what maps to what.

(Ultimately we want a plain text format like fm2.)
Nov 9, 2009
Project Member #1 mauzus@gmail.com
If I understand the source-code correctly, each button/dipswitch needs one byte per 
frame. That would make, for example, ~53 bytes per frames in Metal Slug X, which 
would make the 20-minute movie by AngerFist 3,902 KB, instead of just 16 KB.

I hope I'm getting something wrong, but so far this doesn't look very good. Also, 
analog inputs use 2 bytes instead of 1, if I recall correctly..
Status: Accepted