= MeshFlow Instrumentation = == Insrumentation == svn co -r 39615 https://svn.blender.org/svnroot/bf-blender/trunk/blender cd blender patch -p0 < ../instrument39615.patch # modify the appropriate config file to fit your system configuration # build_files/scons/config/ python scons/scons.py == Instructions == to record, process, view: blender --instrument python exportdata.py ModelingViewer --tvmeshfile steps.tvm --stepsfile steps.txt ModelingViewer --tvmeshfile steps.txt this instrumentation will write out a step??????.blend file for almost every action the artist performs. the exportdata python script will export the data from each step??????.blend file to a set of .ply files. the first ModelingViewer line will read all of the individual files, process the data by adding labels, and write out a single time-varying model file (steps.tvm in this ex). the final line views the file if you wish to continue modeling from where you left off, add the last step??????.blend filename to the first line (ex: blender --instrument step000103.blend). to start over, delete: *.blend, *.ply, steps.txt, stepcount.txt, *.tvm == Current Limitations == MeshFlow does not handle cameras, lights, textures, materials, etc. it only handles modeling. however, MeshFlow does not understand all modeling commands. it does understand the basic modeling commands: extrude, transform, loopcut, subdivide, merge, duplicate, create. the only modifier that MeshFlow understands is the mirror modifier. MeshFlow will only properly handle one 3d view. (no quad view)