Blender Git Loki

typo in Text3d, weightpaint_invert wasnt working properly

simple weight invert script for the weightpaint menu, removed a print from weightpaint_average.py

#ifdef sse headers

fixed sse copy-paste glitch + #define __SSE3__ thanks to Lynx3d

== Sequencer ==

Well, added unnecessary pad variables after a fight with makesdna...

General cleanup in sequencer:

- Seperated StripData into
StripData
TStripData
where StripData holds only image-filenames and TStripData holds
the working information needed for ImBuf caching.
=> Large drop in memory usage, if you used a lot of movie and meta strips.
=> Fixed bugs in "duplicate" on the way (imbufs where copied around without
taking reference counting seriously...)
=> Code is much cleaner now
- Added defines for TStripData->ok
Finally figured out, what the magic values ment and named them properly :)
- Got rid of Sequence->curelem.
Reason: very bad idea(tm) for multi threading with more than one render
thread. Still not there, but this was a real show stopper on the way.

Fix for multimodifier commit breaking game engine compile.

Selecting an image in editmode now adds UV's if they are not there (before assigning the image)

wizard_curve2tree - more twig options
- gravity (like particles)
- follow parent (like gravity but use the parent normal)
- limit the number of twigs on each branch
- limit the radius that a twig may be placed on a branch
- trim the base of branches in a way that better deals with small branches on large branches

Long outstanding feature request: "Multi Modifier"

This allows to mix between the result of 2 modifiers, with both
using the same input state. This is useful for having a mesh deform
and armature deform working together.

However! This functionality could have been presented better...
this is actually Node editor stuff!

Now it works by adding a "MM" button, next to the "overall vgroup"
option. If MM is pressed, the input of this modifier is the same as
the input of the previous modifier.
Only the armature modifier has this option now...

* wizard_curve2tree.py - Automatic alpha blended, textured image joins using material textures and UV layers. Also added some detail options and made it easier to get low poly results.

* Mesh.c bugfix, "mesh.verts = None" didn't set the mesh->mselect pointer to NULL, wizard_curve2tree so would crash when in editmode.
* Texture.py - MTex.uvlayer doc was missing
* buttons_shading.c - Stencil tooltip was stupid.

svn merge -r 12496:12607 https://svn.blender.org/svnroot/bf-blender/trunk/blender

Fixed DNA issue, some optional SSE stuff in (experimental, only 2 functions => not likely to be ever in trunk), BE AWARE: not compatible with old cloth files, many fixes in general, deactivated selfcollisions due to WIP

= Fix for softbody collision mode selector =

This commit makes all softbody collision modes work as they should.

Thanks to Genscher for noticing the issue.

bjornmose, please check this commit.

Bugfix #7552

Panels with different width or height, should give a re-align call
when tabbed and tabs switch

Bugfix #7631

Outliner: change name of library path to become relative gave
incorrect warning.

put the revision number in the splash screen (scons and make)

Proxy fix:

Armature Proxy: the 'free pose channel' didn't restore the custom shapes
when reloading file.

* Fixed own bug: glossy reflections was erroneously giving a
distorted copy of the original face normal, meaning that on
smooth shaded faces, sometimes the check to keep rays
reflected out away from the face wasn't working, and the ray
would intersect when it shouldn't.

* New material option: TexFace Alpha

This is an additional option for 'TexFace', which uses the alpha of
the UV assigned faces as well as the colour. It appears in material
buttons as a little 'A' button next to 'TexFace', when 'TexFace is
switched on. It's a bit horrible, but no point tweaking that layout in
isolation at this stage.

This image is using texface alpha, with different assigned images, all
sharing the one material:
http://mke3.net/blender/devel/rendering/texface_alpha.jpg

Usually I consider texface (and teaching people to use it for UV
mapping) to be pretty evil, but in some cases, when you have lots of
separate images that you want to control in the one material, it can
be quite handy.