Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Don't allow the add paint slot operator to redo. Also guard better against
excessive slot addition
|
|
Passing 'ar' to snapObjectsRayEx would apply a ray-offset.
|
|
Own mistake - not copying enough data.
|
|
Thanks to mont29 for finding the cause.
|
|
I would not have endured such a critical and monstruous bug one more femtosecond!
And even worse - active color was awfully wrong too! Shocking!
|
|
wrong values.
From soc-2014-shapekey branch, with minor edits by mont29 (Bastien Montagne).
|
|
|
|
its own PLAYER_TARGETDIR_VER
|
|
|
|
|
|
* Fill brush did not do proper srgb conversion for byte images (reported
by Sebastian Koenig, thanks!)
* Color sampling for palettes did not refresh the toolbar.
|
|
trash with float images.
Issue is uninitialized alpha in the clone brush + a clamping issue for
float images. There's still some 'swimming' and brightness issue here
but I have to do work for the weekly, will investigate further later.
|
|
|
|
|
|
|
|
'PROP_XYZ_LENGTH' subtype was missing from list of valid '.x/y/z/w' ones.
|
|
changes
|
|
to dedicated folder
|
|
Noise function's significant bits are up to 31st bit. This should now
give the same visual result as before, minus the stripes.
Issue pointed out by Anthony Edlin, thanks!
Conflicts:
source/blender/render/intern/source/render_texture.c
|
|
|
|
type instead of GPencilLayer
|
|
|
|
Wasn't acquiring the GIL.
|
|
Now use linear one, nearest is far too doggy.
|
|
This is so-called GPU limitation boundary hit, told compiler to NOT include
volume bound function, otherwise some real weird things used to happen.
We actually might want to do the same for CPU, inlining everything is not
the way to get fastest code.
|
|
The reported issue was caused by a backward incompatibility due to careless
code changes made when per-material Freestyle line colors were introduced
in rB7915d7277ac8c605f016f30f943080556244fb59. In 2.71 line style
Material color/alpha/thickness modifiers was retrieving alpha transparency
from Material.alpha, whereas in 2.72 Material.line_color[3] was referenced.
The present fix reverts the aforementioned code changes.
This issue is a regression from 2.71, so the fix is appropriate for inclusion in
the 2.72a release.
|
|
|
|
|
|
|
|
respondsToSelector to simplify the whole detection
|
|
|
|
|
|
smoke.
Reported by nudelZ
|
|
Navigation mesh object need to access the current scene at
creation time. This can be at scene start or when an object
is instantiated from an inactive layer. The method of getting
the scene differs in these cases. This fix handles both.
|
|
Issue was, parenting with operator, then unparenting would keep the inverse parent matrix.
So if you then parented again through the mere Object field of Object buttons, you'd still
use previous inver parent matrix, giving some weird behavior from user PoV.
This commit simply makes sure inverse parent matrix is always reset to indentity when clearing
parents.
|
|
make sure the window states are correct in the lion_fs animation phase.
This also assures the CTX_wm_window(C) is okay.
|
|
commit.
If we include the data cleanup commit to an alpha version for 2.72a this
should be included as well
|
|
The issues identified here are regression from 2.71, so the present code
revision is appropriate for backporting if 2.72a is planned.
|
|
only element.
A StrokeVertexIterator ignores the first element when it is the only element.
Such an iterator can be created by the .incremented() method from an iterator
over two stroke vertices.
This problem is a regression from 2.71. The present fix is appropriate to backport
if Blender 2.72a is planned.
Problem report by Kazuhiro Murakawa through personal communications, thanks!
|
|
Otherwise tweaking resolution/border would affect the way tiles are highlighted.
|
|
Not as if it gives noticeable changes render-time, but it's just weird to
convert float4 to float 3 to just access individual x/y/z components.
Plus some compilers might be more stupid than GCC and don't optimize this
out well.
|
|
We queried the wrong value when looking for the bound 2D texture. This
is not totally robust because currently bound texture may not be a 2D
one, but this should work for now.
|
|
|
|
|
|
Own mistake in previous fix here, was too greedy in finding an existing kmi of UserPref add diff kmi, we only want
to ignore exact same kmi's here.
|
|
|
|
|