| Age | Commit message (Collapse) | Author |
|---|
|
Regression in 2.76, order of tessellated vertices needs to follow MFace tessellation.
|
|
|
|
|
|
|
|
Not cherry picked, just included for release build.
|
|
|
|
image data
If the node output had only one layer, it would be detected as singlelayer, and it would miss the blender exr header string
|
|
'Distance from Object' color/alpha/thickness modifiers without a target
object were raising a run-time exception although it is not considered an
error condition.
|
|
The reported crash was confirmed as a segmentation fault in std::sort().
The cause of the crash was traced down to a binary comparison function
that was not satisfying the so-called strict weak ordering requirements of
the C++ standard sorting function. Specifically, the comparison operator
has to return false when two objects are equivalent (i.e., comp(a, a) must
be false), but that requirement was not met.
Since the binary comparison operator in question could be a user-defined
Python function, here a safety measure is implemented in the C++ layer to
make sure the aforementioned requirement is always satisfied.
|
|
shading in Texture paint mode and cycles
|
|
Should fix T46616 but will reintroduce T46284.
The second, original bug needs different handling
This reverts commit 904db487a7b14c31282fe0284612159a836657cd.
|
|
Seems was caused by the race condition in the stats printing, should be all fine now.
Nice for 'a' release.
|
|
Vertex parent was not registered as CPU data requirement.
Should be in the 'a' release.
|
|
|
|
progress bar at all).
|
|
Also fixed a potential crash in the copy constructor case.
|
|
BlenderFileLoader tries to find the smallest edge size but the computed value is not used.
|
|
from buttons
Previously, a warning was added to provide feedback to users trying to change the values
of driven properties why their edits would not have any effect on the propeerty. However,
it turned out that instead of only showing up when the user tried to increment/decrement/slide
the property's value, it was also firing everytime they were trying to edit the expression.
That however is not what we want at all!
This fix assumes that BUTTON_STATE_TEXT_EDITING is used for expression editing, and
BUTTON_STATE_NUM_EDITING (or everything else) refers to the user trying to adjust the
value normally.
|
|
When the "Use Y" option in the Copy Rotation constraint is disabled, the constraint
behaves eratically when rotating all the target on all axes at the same time.
This is partially to be expected due to the way that euler rotations work
(i.e. the rotation orders stuff - you should use a rotation order based on most to
least important/significant rotations). Hence, by locking Y, you're causing accuracy
problems for Z.
What was not expected though was that changing the rotation orders on the objects
involved (for the record, it's the constraint owner that counts) did nothing.
It turns out that for objects, the rotation order settings were getting ignored!
This commit fixes this problem, and this particular case can be resolved by using
"XZY".
Notes:
* Since all object constraints were previously working on the assumption that they
used XYZ (default) order, it is possible that this change may have the unintended
consequence of changing the behaviour of some rigs which relied on the buggy
behaviour. Hopefully this will be a rare occurrence.
|
|
Sometimes the timeline header didn't update after time-scrubbing in the graph
editor ends, leaving the "Pause" button visible until the next refresh of the
timeline (e.g. on mouse over)
|
|
"Drivers" mode
|
|
|
|
D1575 by @januz
|
|
UV Editor keymap is not bound to a given editor (spacetype)...
|
|
op invoke when prop is already set!
|
|
Don't use nan for comparisons.
|
|
- audio_stream wasn't freed.
- audio/video stream + context weren't freed on failure.
|
|
Was checking wrong length on string copy.
|
|
|
|
Related to T46503,
fix only worked when the snap target was axis-aligned.
|
|
|
|
Same as previous commit, just was missing in there.
|
|
It was possible to miss some intersection caused by wrong barycentric
coordinates sign.
Cases when one of the coordinate is zero and other are negative was not
handled correct.
|
|
direction under certain circumstances
The issue was caused by wrong sign check. It originally came from more optimized
Cycles code where because of other reasons it wasn't visible yet. But in fact it
should be solved there as well.
|
|
|
|
When children & parents were selected in the outliner,
it attempted to free the the object twice.
|
|
Rendering to a path that didn't have write permissions would crash.
Also fix error where `G.is_rendering` was left set when rendering failed.
|
|
Different issue actually, here RAWTGA was simply forgotten in the alpha-capable formats...
|
|
Previously meshes with modifiers were considerate as empty (no polys).
|
|
|
|
It fix T46381. Normally BL_Action::Update (manage action time, end, loop…) should be called the same number of times as BL_Action::UpdateIPO (update action position, scale ect… in the game object).
But the bug report shows that UpdateIPO is called one less time than Update. To fix it i revert the commit 362b25b38287cb75e4d22b30bdbc7f47e8eb3fdf and implement a mutex in BL_Action::Update.
Example file : {F245823}
Reviewers: lordloki, kupoman, campbellbarton, youle, moguri, sybren
Reviewed By: youle, moguri, sybren
Maniphest Tasks: T39928, T46381
Differential Revision: https://developer.blender.org/D1562
|
|
Regression since moving to looptri.
|
|
Same case as with space char really, one should not use those special chars in
filenames, but they are globally supported by all current FS/OS, so no real reason
to enforce that behvior on users here.
To be backported to 'a' release.
|
|
Should be backported to 'a' release.
|
|
files.
All optional image format are not #define'd in submodules like DDS read/write code.
This means values of `eImbTypes` would not always be the same in all contexts, yuck!
This is a regression and should be backported to 'a' release.
|
|
added in sequence editor.
|
|
Even if the weights are normalized, the weighted sum of normalized vectors
usually does **not** give a normalized vector (unless all source vectors
are aligned).
This probably was not a big issue in most cases, since we usually interpolate
similar vectors here - but still!
|
|
The final stage of the process (copying/interpolating new dst cddata from src cddata)
was simply broken in normal case, where we need to convert from source to destination
object space.
This patch is a bit verbose, but I cannot see how to avoid it really.
To think this code is in master since over 6 months and it only gets reported now... :/
|
|
Also, cleanup, reduce declarations of tmp_co/_no...
|
|
|
