Blender plugin for io_export_diffmap, original authors have apparently abandoned the project. This effort is intended to update io_export_diffmap to the latest Blender release (2.7+).
After a little time working with this code I decided it's just too poor a baseline, but given I've learned everything involved in making blender UIs, tools for blender and unity etc... I've rewritten the project entirely it works a lot more reliably and has a sensible data file format which is descriptive.
I'll be publishing io_export_shape_keys and shape keys for unity shortly.
It's annoying to have to export multiple objects which exist on the same animation timeline. It would be preferable to iterate over selected objects, or all objects in the scene. A checkbox should be included in the export window for "Selected Objects"
The file format used is cumbersome and seems to leave out vital data such as scales for the shape keys. Replacing the file format with a textual format which describes both the shapekeys and the animations would solve this problem. It would also reduce the amount of code used for parsing to almost nothing and clean up some poor type encoding (strings where floats should be).
Extra things we want to encode include scales, image files and start shapes and allowing multiple animations in a single data file, thereby reducing significantly the complexity of setup. This would mean that the diffMaps and animationRecordings would be automatically generated when loading the JSON file.
Figure out a way of pre-building the diffMaps into an output format of some kind with the scales data so we can test that we've got the correct scales computed.
Playback on the Unity side doesn't match the animation that's being exported. I have a feeling this is related to "scale" for each of the diffmaps. I need to learn more about how the old script was calculating these to ensure that I get the correct output result.
Line 187 onwards used to target color1 through color4, the crack happy hack was just to target 'color' but the documentation is unclear about proper update process.