| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
LINEAR_LIGHT.
|
|
|
|
|
|
|
|
OPERATOR_CANCELLED.
|
|
also quiet warning without openmp.
|
|
(Patch by Philipp Oeser, submitted in [#37199], many thanks)
|
|
Maya keymap was activating wrong transform modes for translation/scaling - in
DopeSheet and NLA, these use the TIME_TRANSLATE/TIME_SCALE modes instead
|
|
|
|
|
|
Cycles shader inputs/outputs based on socket names are using a few modifications on the Blender socket names. But these only apply
to standard nodes where the Blender socket names can differ from associated Cycles names and may require additional indices to make them unique. Script node sockets are already unique and exact due to
being generated from the script function parameters.
|
|
|
|
lot more needed) so that they get properly updated in UI when the
property is edited through python or a custom key binding to context
toggle operator.
|
|
of lasso enclosing rectangle.
|
|
Thanks to Campbell for the advice!
|
|
|
|
for now.
Used to be ultra terrible but with threading (openmp) there is slightly
better performance
and is ready for testing. To use press shift-ctrl-lclick. Still no
ability to
remove mask. Coming soon.
Also make box selection threaded (openmp) and comment fix.
|
|
|
|
|
|
Added two options to a header of FCurve editor:
- Normalize which makes it so every individual
curve is fit into -1..1 space.
- Auto-normalize, which probably is to be called
"Lock" which "locks" curve normalization scale.
This is useful to prevent curves from jumping
around when tweaking it.
It's debatable whether it need to be a button to
normalize curves n purpose only, and it's fully
depends on animator's workflow.
Here during Project Pampa we've got Francesco
who get used to auto-renormalization and Hjalti
who prefers locked behavior.
Docs are to be ready soon by Francesco.
Thanks Brecht for the review!
|
|
Remove usages of ANIM_unit_mapping_apply_fcurve in favor of
runtime scale factor apply.
There're still calls to ANIM_nla_mapping_apply_fcurve are
hanging around, they're the next t be cleaned up!
|
|
shader node editor. The 'free' callback for node execution data was accessed from the node->typeinfo, but this pointer can
become invalid because the render database is not immediately freed after the job finishes. To avoid access to dangling node pointers, store the function callback in the exec data itself. The node
pointer must not be accessed in the free function (wasn't used before either), these functions are purely for the execution data.
|
|
hmrf arguments order was wrong ... but int/bool casting made it pass
through the compiler
|
|
Mapping from grid on ll 0 was not used and was incorrect
since bmesh merge anyway.
|
|
Uses trick with crating simple subdivided mesh with
level 1 and bakes against it.
From quick tests seems to be working correct, more
tests are welcome.
|
|
Not sure what's actual reason for this, increased it to MAXFRAMRF.
|
|
|
|
using a texture with "Particles/Strands" coordinates that in turn has a "Lifetime" influence on the particles, the texture eval
accesses the particle lifetime/dietime data before it is actually defined! This is a design flaw, but to avoid corrupted data for now just initialize the lifetime/dietime values for particles in advance
before evaluating the texture.
|
|
Panning)
|
|
Collada exporter
|
|
|
|
|
|
Quads: Beauty, Fixed, Fixed Alternate, Shortest Diagonal
Ngons: Beauty, Scanfill
* Shortest Diagonal is the default method in the modifier (popular
elsewhere), but beauty is the default in Ctrl+T).
* Remove the need for output slot and beauty operator to be called
after Clt+T
Patch with collaborations and reviewed by Campbell Barton
|
|
Before the refinement phase of tracking, a brute force SAD search
is run across the search area. This works well but is slow;
especially if the guess for the track's location is accurate.
This patch runs a refinement phase before running a brute force
search, hoping that the guessed position (in x2, y2) is close to
the best answer. If it is, then no brute search is done. If it is
not, then a normal brute force search followed by refinement is
done.
In some cases this may produce worse tracks than before; the
regressions will need investigation. The predictive motion model
(to be implemented) will reduce the probability of that happening.
|
|
from Henrik Aarnio (hjaarnio)
|
|
reroute nodes, cutting node links)
by Henrik Aarnio (hjaarnio)
|
|
from Lawrence D'Oliveiro (ldo)
|
|
from Lawrence D'Oliveiro (ldo)
|
|
points is at the tail point of points it's connecting.
from Henrik Aarnio (hjaarnio)
|
|
|
|
Added a property to track_marker operator to be
able to render clip which name was passed to the
operator instead of clip from current clip editor
context.
Very much useful for automatic tests.
|
|
|
|
|
|
Before this patch, if Ceres returned USER_SUCCESS indicating that
Ceres was only changing the tracked quad slightly between
iterations (indicating convergence), no final correlation check
was done. This leads to incorrectly returning that the tracking
was successful, when it actually failed.
|
|
|
|
|
|
Commited patch provided by Lawrence D'Oliveiro, thanks.
|
|
when using an image sequence offset
generally speaking, if multilayer image fails to load for current
frame doesn't mean anything bad. It might be used to make it so
image sequence is being alpha-overed somewhere in the middle of
scene time.
Made it so if the whole file fails to load, image node will
deliver black transparent color, the same what happens for
regular (non-multilayer images).
Also needed to tweak code in load_multilayer_sequwnce to make
sure no cached frames are pointing to a freed memory.
|
