Blender Git Commits

Fix more crashes when removing facemaps. Indices of leftover facemaps
above the deleted one could become invalid

More silly mistakes in widget move code.

Stubs for new facemap widget, fixes for facemaps.

Move/remove facemap not working well (probably was never working but by
displaying them has actually made the issue apparent)

Fix crash with decimate modifier on zero.

Fixes to facemaps:

* Test display code that displays the active facemap. Will not work on
subsurf modifier yet (crash)
* Fix loading of files with facemaps
* Facemap data now reside on polys instead of tessfaces.

Merge branch 'master' into wiggly-widgets

Code that will draw a transparent overlay of a facemap over the mesh
(crashes atm).

Add code that copies sorted per facemap vertex indices to a VBO buffer

Initial VBO code for GPU subsurf.

This commit adds a few generalizations to the VBO
code so that modifiers can create and populate their own GPU objects.

The VBO code originally supported CDDerivedMesh only. The design moves
slightly towards the viewport refactor where the rendering system
requests data from modifiers.

What we do have is support for solid shading with multiple
materials, flat/smooth shading and a big performance boost.
Performance could

In this commit only basic support for vertices and normals is provided
and some features from blender's VBO system, such as mapping to
original faces, unique element indices for vertices and loose vertex/
and can be added later. The one feature that is missing now is the quick
navigation feature of the multires modifier (which uses the same code).

- Why this commit is made on the widget branch -

Facemap widgets need to avoid drawing the whole mesh when we do
collision detection on them. For subsurf drawing we need to iterate
through the whole mesh every time. What we need instead is sort
indexed elemet drawing according to the facemap each face belongs to.
This screams VBOs but since I was going to add that, I thought that
I could push it a bit further and add proper solid shading support.

Revert "Initial VBO code for GPU subsurf."

This reverts commit 7163ddf53e6f5f67c59a8dfc14f60515f8f577c7.

Initial VBO code for GPU subsurf.

This commit adds a few generalizations to the VBO
code so that modifiers can create and populate their own GPU objects.

The VBO code originally supported CDDerivedMesh only. The design moves
slightly towards the viewport refactor where the rendering system
requests data from modifiers.

In this commit only basic support for vertices and normals is provided
and some features from blender's VBO system, such as mapping to
original faces, unique element indices for vertices and loose vertex/
and can be added later. The one feature that is missing now is the quick
navigation feature of the multires modifier (which uses the same code).

What we do have is full support for solid shading with multiple
materials, flat/smooth shading and a big performance boost.
Performance could

- Why this commit is made on the widget branch -

Facemap widgets need to avoid drawing the whole mesh when we do
collision detection on them. For subsurf drawing we need to iterate
through the whole mesh every time. What we need instead is sort
indexed elemet drawing according to the facemap each face belongs to.
This screams VBOs but since I was going to add that, I thought that
I could push it a bit further and add proper solid shading support.

Merge branch 'master' into wiggly-widgets

Placeholder GPU functions to get GPU facemap index buffer. API should
allow a widget to draw a specific facemap bound to a mesh quickly.

Fix selection id not getting incremented in face-map bones

Deactivate irritating shapekey widget while it's still under
development.

Hook up facemap property to bones.

A bone using a facemap will not be displayed at all, rather it will use
the facemap of the mesh as an interaction area. The facemap still does
nothing since it's not yet hooked up to the customdata and widget code.
That will come next.

Support for custom cursors for widgets.

They are set when a highlighted widget intersection is detected and on
area level.

There's a discussion about using owners and a stack or array for cursors
but that needs some more thought and design.

More changes to overdrop transform operator.

* Calling key press confirms
* Change name of operator accordingly.

Gooseberry request draw sequencer backdrop on -top- of everything.

Due to this we -obviously- rename this to overdrop

I am not sure if others would agree here, but it's pretty safe to do
this on a branch first. Rationale is that it's much nicer to work on
full screen with this.

Minor adjustments to the cage transform widget and sequencer operator.

* Bigger scale handler for widget.
* Operator has description on area
* Cancelling resets position.