thanks for pointing that out. I misunderstood the "frames" value in the bizarre fcm spec so all FCM percentages were incorrect. The number of frames I thought the movie had was only the number of times that the controller state changed. your Solstice example had near 17k frames, not 4k. Also since no one was posting I didn't bother to continue updating but now I'm up to v0.6, and it
supports FCM (correctly now, thanks!), FM2, GMV(no support for XYZ buttons yet), SMV, M64 (the analog stick is considered one button, either used or unused per frame), and writing out the data to a text file. This should work with any supported replay format* but it will only show stats for player 1.
TODOs: add vbm support, add GMV's XYZ support, make tabs for movies with multiple controllers, clean up display code, post source
Proof that it works:
and link to v0.6:
http://www.mediafire.com/?a0chh0i0vqi
*If there is a two-player+ run of a nintendo64 game, with actual input on more than 1 controller, the stats are likely to be extremely inaccurate through no fault of my own. Blame the m64 spec creator or mupen's input API writers.