| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
operator and move it next to the detail slider
|
|
Located on topology panel.
To use just click on button and click on mesh.
Operator will just use the dimensions of the triangles below to set the
constant detail setting.
Also changed pair of scale/detail size with nice separate float
percentage value.
|
|
Nothing spectacular here, fill tools are easy. Just take the dyntopo
code and repeat until nothing more to do.
The tool can be located in the dyntopo panel when the dyntopo constant
detail is on.
Also added scale factor for constant detail. This may change when detail
sampling gets in, I am not very happy with having two numbers here,
still it will give some more control for now.
|
|
This commit introduces support for a number of new interpolation types
which are useful for motion-graphics work. These define a number of
"easing equations" (basically, equations which define some preset
ways that one keyframe transitions to another) which reduce the amount
of manual work (inserting and tweaking keyframes) to achieve certain
common effects. For example, snappy movements, and fake-physics such
as bouncing/springing effects.
The additional interpolation types introduced in this commit can be found
in many packages and toolkits (notably Qt and all modern web browsers).
For more info and a few live demos, see [1] and [2].
Credits:
* Dan Eicher (dna) - Original patch
* Thomas Beck (plasmasolutions) - Porting/updating patch to 2.70 codebase
* Joshua Leung (aligorith) - Code review and a few polishing tweaks
Additional Resources:
[1] http://easings.net
[2] http://www.robertpenner.com/easing/
|
|
is needless
|
|
|
|
|
|
previous fixes only tweaked epsilon, but logic for skipping zero area
boxes was still wrong.
|
|
|
|
To reduce user confusion, we were already presenting users with an error message
when they tried to edit constraints for bones from the Object Constraints tab.
This commit just makes things more convenient by adding a button which takes
users to the right tab when clicked.
|
|
Core issue exists since ages - the thing you get from bpy.types.YOUR_OT_operator is fuzzy, and may change,
due to the fact that both Operator and OperatorProperties share the same name...
Would be cool to get rid of this issue one day, but for now it's safer to use rna acessor...
This commit is to be backported to 2.70.
|
|
|
|
The color picker uses.
|
|
|
|
Expose all four quadviews in a collection in RNA API.
Note the region returned by old region_quadview property is now region_quadviews[2].
|
|
transformation.
This was suggested by Christopher Barrett (terrachild). Corner pin is a common feature in compositing.
The corners for the plane warping can be defined by using vector node inputs to allow using perspective plane transformations without having to go via the MovieClip editor tracking data.
Uses the same math as the PlaneTrack node, but without the link to MovieClip and Object.
{F78199}
The code for PlaneTrack operations has been restructured a bit to share it with the CornerPin node.
* PlaneDistortCommonOperation.h/.cpp: Shared generic code for warping images based on 4 plane corners and a perspective matrix generated from these. Contains operation base classes for both the WarpImage and Mask operations.
* PlaneTrackOperation.h/.cpp: Current plane track node operations, based on the common code above. These add pointers to MovieClip and Object which define the track data from wich to read the corners.
* PlaneCornerPinOperation.h/.cpp: New corner pin variant, using explicit input sockets for the plane corners.
One downside of the current compositor design is that there is no concept of invariables (constants) that don't vary over the image space. This has already been an issue for Blur nodes (size input is usually constant except when "variable size" is enabled) and a few others. For the corner pin node it is necessary that the corner input sockets are also invariant. They have to be evaluated for each tile now, otherwise the data is not available. This in turn makes it necessary to make the operation "complex" and request full input buffers, which adds unnecessary overhead.
|
|
NEVER use `git commit .` or stage submodules. Leave it to platform maintainers!
See [1] where you'll find few hooks which would help you preventing
accidental commit of submodules.
[1] http://wiki.blender.org/index.php/User:Nazg-gul/DevTools#Git_hooks
|
|
value was mixing operator result with an int/boolean.
|
|
Dyntopo detail in object space. This allows to set the detail in
percentage of blender units and sculpt in this detail constantly,
regardless of the distance to the mesh.
This commit just enables the functionality, which is really trivial.
There will be some more commits like detail flood fill and
detail sampling in the future.
|
|
|
|
- Addons and locales now points to v2.70-rc tag
- Also updated hashes for addons_contrib and scons
to make them up-to-date while i'm on updating this
hashes.
|
|
Splash concept art & paint-over: David Revoy. 3D artwork by Mathieu Auvray.
|
|
|
|
patch T37008 from Michael P.
|
|
tab, now only show in Tools.
Patch by Kévin Dietrich.
Reviewed by: dingto
Differential Revision: https://developer.blender.org/D378
|
|
also comment debug prints for raytracing
|
|
|
|
i18n option
Actually, was broken for any custom modifier name, since it was explicitly using 'Cloth' one. Changed to mimic other cloth pressets (wonder why this one was different!).
|
|
Also allow mirror for any object type
|
|
|
|
|
|
|
|
Also fixed wrong frame number used for reconstructed object
visualization in 3D viewport.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds bpy.utils.escape_identifier()
|
|
This is what we do with boolean and sub-settings. We usually hide it when the options depend on a menu-enum.
|
|
|
|
|
|
|
|
removed from the UI.
Also shorten info messages a bit.
|
|
Patch by Sebastian Koenig, thanks!
|
