| Age | Commit message (Collapse) | Author |
|---|
|
Resolves T40745, where faces from extruded edges had flipped normals.
|
|
|
|
|
|
|
|
|
|
Returning to object mode reactivates any generative modifiers
and this can lead to a polycount explosion.
For now just improve the warning when entering dyntopo with generative
modifiers. I would like to add the ability spawn options to apply or
remove the modifiers too, however separate undo stack system comes back
with a vengeance here, since it won't allow restoring the application/
also may invalidate all sculpt undo in the undo stack prior to the
application (needs investigation).
|
|
|
|
nice 32chars hexadecimal string.
That kind of stuff belongs to BLI, not specialized code like thumbs.c
|
|
|
|
- Was missing pixel scale
- Dither is now supported on GPU
|
|
Currently resolution divider is not exposed to the
interface yet, and i'm not even sure it needs to be
exposed because it's somewhat weird configuration.
Need to check how often artists are changing start
resolution in Cycles.
Pretty much straightforward implementation with the
only weak part: render result is getting re-allocated
and upscaled when current resolution is finished.
Not sure how to make it faster actually. Maybe it's
just a matter of making upscale fast enough.
Needed to fix some possible memory leak happening
in Freestyle when canceling rendering on a special
stage -- it was missing temp bmain free,
Reviewers: campbellbarton, dingto
CC: sebastian_k, fsiddi, venomgfx
Differential Revision: https://developer.blender.org/D609
|
|
Auto-generate this link from Blender version, as done for e.g.py API link.
This commit should be backported to 2.71 branch.
|
|
|
|
D590 by Matthew Reid
|
|
|
|
D529 by Gottfried Hofmann
|
|
Needed to make the blender link libraries a global property
now that tests are parallel to source directory.
Current sort order for blender link libraries doesn't work
for tests that start with few defined symbols. Doubling the
lib list works, but a TODO to find a better way (probably
using CMake's own mechanism for tracking dependencies).
|
|
** TO BE PORTED BACK TO 2.71 **
As pointed out by Thomas Beck (plasmasolutions), the current behaviour and/or
default values for their parameters didn't quite make sense:
1) Back Easing - The old default value of 0.0 results in some overshoot being applied,
while trying to tweak it up or down resulted in some odd jumps and discontinities.
I've ended up removing some code here which forcibly using a "back" value of 1.7
when users wanted 0.0 instead. There doesn't seem to be any good reason for this.
To ensure that there is still an effect initially, keyframes now get created
with back set to 1.7
2) Elastic Easing - The old default settings of <amplitude = 0, period = 0> resulted
in a curve without any elastic bounce, which wasn't very useful for motion graphics.
Now, default values of amplitude = 0.8 and period = 4.1 get set. These were hand picked
by Thomas to work well when the duration of the motion is 10 frames long (i.e. the
typical length of such effects when doing motion graphics).
|
|
|
|
initialised properly
|
|
D608 by Gaia Clary
|
|
|
|
|
|
|
|
|
|
|
|
|
|
also remove redundant check
|
|
WOEdge::GetVec().
|
|
|
|
Fix to be included in 2.71
|
|
Reported by Andy Davies (metalliandy) outside the tracker
Fix to include in 2.71
|
|
Error
Users can now bake from Mesh, Font, Curve, Surface and Metaballs.
Fix to include in 2.71
|
|
|
|
Sorry, forgot to check other uses of BKE_nurb_makeCurve, NURBS surfaces were affected as well.
|
|
Error in rB4b4bb410e04e, BKE_nurb_makeCurve() requires its coord_array to be zero'ed,
hence we need calloc here.
|
|
Do not do a step when there is no collision of the brush with the mesh.
|
|
|
|
|
|
|
|
|
|
Issue here is that if there's a texture in the tree, chances are it has
already been set as active texture so groups are never traversed.
Now changed logic so that if a group node is active, its own active
texture takes priority over the parent group active texture.
|
|
Currently covers only small set of functionality.
|
|
Cleanest way here is not do bounding box collision for editmeshes at
all. Decision is taken because:
* Usually we want to do the snapping to the edited mesh anyway (when we
don't the mesh is skipped completely, so we don't need to worry for
extra checks)
* Bounding box is calculated from derived mesh. This means that for
subsurfed meshes for instance, the bounding box may be significantly
smaller than the size of the edit mesh.
|
|
Looks like the cleanest way to handle this is to no do bounding box collision
for edit mode at all. But this is easy to enforce
This reverts commit 7b5fe4f316234022a0ab761b694cd459ce98db2d.
Conflicts:
source/blender/editors/transform/transform_snap.c
|
|
|
|
|
|
|
|
|
|
|
