Blender Git Commits

Compute homographies when creating new plane tracker

When new plane tracker is creating, blender will go
over tracked sequence of point tracks, compute homography
between neighbor frames and deform plane rectangle using
this homography.

This makes rectangle plane follow tracked plane quite
nicely. But as an additional homographies will be
updated after corners were slided with a mouse.

Additional changes:

- Display keyframed/tracked information in the cache line
for plane tracks (the same way as it's done for point tracks).
- Fix couple of buys in homography C-API.

Add Procrustes PNP ("PPnP") resection algorithm to libmv

This adds a new Euclidean resection method, used to create the
initial reconstruction in the motion tracker, to libmv. The method
is based on the Procrustes PNP algorithm (aka "PPnP"). Currently
the algorithm is not connected with the motion tracker, but it
will be eventually since it supports initialization.

Having an initial guess when doing resection is important for
ambiguous cases where potentially the user could offer extra
guidance to the solver, in the form of "this point is in front of
that point".

brought accross a lot of the comments from the wiki for snap.c

Initial code layout for real plane tracker

This commit includes:

- DNA structures layout. It's not completely finished
yet, and at some point files could become broken,
but we'll try to avoid this as much as we can.

- Basic RNA code layout for new data structures.
Not completely finished in terms it's not possible
to define plane tracks from Python just yet.

- Operator to define the plane.

- Deletion and selection operators are aware of planes.

- Plane marker's corners could be slided with mouse.

Still lots of thing to be done, but we need to commit
at some point so we could share the code work.

* Show spacing in UI for polylines
* On Confirm, last line point is dangling, don't use for polyline.

Merge trunk -r58813 into soc-2013-paint

Polyline becomes a separate stroke mode. Rationale for this is that
artists like the quick drag and release for quick lines and requiring
the user to keep the shift key pressed for new line segments would be
cumbersome and inconsistent because it would mean that first line
additionis done on release and subsequent get added on key press.

So, lines now use a drag-release paradigm and polylines use regular
clicking. To confirm, use space or enter like on any operator. Polyline
bit was used for fixed textures on earlier blender versions, meaning
that I'll have to make sure that flag is not used anymore. I will do a
commit for this on trunk.

In progress applying GPU_simple_shader to implemented shading on ES/COre

Broken build because I ran out of steam while replacing calls to glShadeModel.
Will resume after I get some sleep :-)

Merge trunk -r58805 into soc-2013-paint

WIP. gradient code

Merge trunk -r 58803 into soc-2013-paint

Fix compilation error after recent merge.

Merging r58363 through r58794 from trunk into soc-2011-tomato

- added a map to keep track of open volume files;

Merging from trunk r58769 into soc-2013-motion_track

Mostly to have the cleaned up libmv C API from r58765.

- added the library "cycles_kernel_textures" to build target;
- isolated OSL Services from VDB Volumes by adding the class VDBTextureSystem to hold API;

* Rearrange UI to hide colour wheel when gradient is active
* Palette colour goes to active color band color if gradient is active

UI for color ramps that will be used as gradient source for colors
during stroking and gradient filling. Still not functional.

got mapped vbo working in ES and Core

Support polylines for line strokes.

This commit changes the way line strokes work. Instead of dragging, user
now clicks on end point to end the stroke. If shift is pressed during
that click, a new line is added instead.