| 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.
|
|
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
|
|
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.
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
|
|
|
|
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.
|
|
or not
If render engine has bl_use_texture_preview set to truth blender wouldn't fallback to
the blender internal rendering for previews.
|
|
|
|
|
|
The solution is to do the multiplication with the energy in the shader
after texture application.
We might be able to avoid setting dyncol completely, but this needs
better investigation. Some shader paths also look a bit redundant.
Also, texture mapping is not supported very well for light lamps, might
also need investigation.
|
|
BM_face_point_inside_test assumed the face center was inside the face.
|
|
|
|
config profile
When patching a keymap with a 'UserPref' diff one, do not add keymap items from diff
if they already exists in patched keymap.
|
|
|
|
Do not generate materials/images/UVs if they are missing.
Now we spawn a panel ("Missing Data") with operators to generate the missing data and
pop a warning if user tries to paint without them.
The reason we have reverted this is that it is too easy to end up with more textures
than we wanted. It was impossible to enter texture paint without having textures added,
and code makes too many assumptions about what user may want.
Discussed during Sunday's meeting.
This might be a candidate for 2.72a but I'm not sure how other artists will take this
(and how refined and crash-free it is), better make a few iterations first.
And for interested parties...test please, don't wait until after a release to poke with such issues.
Also, add slot operator now adds a new unconnected image node in cycles. Only
used in the "Missing Data" panel. This should be a separate commit but I am squashing it into the same commit because
it relies too much on changes done here and can be reverted easily if complainstorm occurs again.
|
|
|
|
|
|
|
|
(border-zoom in 3DView).
Thanks to jensverwiebe (jens verwiebe) for investigations too!
|
|
We messed up previous fix, in 'simplified' translated merge case... :(
|
