Kai Kostack
Aug-16-08	Experimental

Please report bugs at http://blenderartists.org/forum/showthread.php?t=119216.

Latest on top:

UPDATE (2008-08-16):
- SVN update only

UPDATE (2008-05-07):
- now the current render size/defined size settings will be taken into account (those 100,75,50,25% buttons)

UPDATE (2008-05-05):
- i have included blenderplayer and ffmpeg

UPDATE (2008-04-27):
- fixed loss of vertex colors
- improved backface culling
- extended limits for subdivision rate

UPDATE (2008-04-20):
- fixed loss of UV-data
- fixed compiler warnings
- small speed improvements
note that for this release i temporary disabled the game engine.

UPDATE (2008-04-13):
- cleaned up code and renamed some functions to meet naming conventions
- changed default division rates to 8 and 2
- added new option to enable/disable backface subdivision
- fixed some mblur issues left over
- fixed wrong rotation correction

UPDATE (2008-04-06):
i found that i used a wrong copy function in two places and one of them can cause memory corruption by writing over the end of a vector structure.
hopefully this is the reason for all problems.
other fixes:
- now the modifier doesn't need original data anymore. this means you can have subsurf above it or whatever you want. :) to achieve this i extended editmesh.c by a new function make_editmesh_from_derivedmesh(). i'm infiltrating the whole blender code.
- the modifier won't overwrite scaling and rotation data any longer.
- the division rate now will behave a bit more realistic. a division rate of 1 should mean one triangle per pixel^1, at least approximately.

UPDATE (2008-04-04):
Heavily improved, optimized and ready for both types of motion blur, this is the new build. :)

FIRST RELEASE (2008-04-01):
This is the first test build and there are a still a few known issues left to solve:
- There is no motion blur correction and optimization so far. The modifier is calculated for each subframe for regular motion blur and vector blur won't work at all so far.
- When rendering the modifier is always calculated three times per frame, even when vector blur or speed verctors are disabled. i don't know why blender does this, it's strange.
- In the viewport on time changes the animated camera position and rotation is somehow always one frame behind. i don't think the modifier is the reason for this, G.scene->camera->obmat simply returns old values.
- And some for the end-user invisible hacks were needed to bypass some strange behavior of a meshtool function. I need to talk to some blenderdev about this.
It's slow but it should work.