Blender Git Commit Log

All Blender Git commits.

Page: 1453 / 8462

July 20, 2020, 13:36 (GMT)
Fix T78958: Library Override crash: undo make local.
July 20, 2020, 13:31 (GMT)
Particles: support removing particles during the simulation

This still cannot be controlled by the user. Currently, all particles are
killed after two seconds
July 20, 2020, 13:23 (GMT)
Fix T79107: Crash changing brush size in GPencil sculpt

Reviewed By: fclem

Maniphest Tasks: T79107

Differential Revision: https://developer.blender.org/D8353
July 20, 2020, 12:15 (GMT)
Merge branch 'master' into newboolean
July 20, 2020, 12:04 (GMT)
Fix signed/unsigned comparison
July 20, 2020, 12:02 (GMT)
GHOST: Vulkan: Add logical device creation
July 20, 2020, 11:55 (GMT)
Fix T79075: Tool popup fails with experimental vertex colors enabled

Register key-maps from tools in functions.
July 20, 2020, 11:52 (GMT)
Fix T70455: Knife Tool failing to cut edges

Analyzing the cuts, the points shown in the viewport (indicating the
previous and current cuts) do not correspond to the final cuts.

Sometimes a point, even snapped to a vert, is a point that cuts an edge and
sometimes a point, even snapped to an edge, is a point that cuts only the face.

This is because the detection of snapping vertices from mouse is different
from the "snap" that detects vertices that are cut.

So small projection inaccuracies can result in detection failures.

The solution for this is simply to confirm the cuts whose vertices
indicate the `prev` ou and `cur` point.

The tolerance distance does not need to be calculated in these cases.
July 20, 2020, 11:35 (GMT)
Update integer type usage
July 20, 2020, 11:34 (GMT)
Merge branch 'master' into newboolean
July 20, 2020, 11:26 (GMT)
Move vertex (and UV vertex) list outside OBJRawObject

Since an OBJ file may contain data like [1], the vertex coordinates
list should be detached from any `OBJRawObject`. So every raw object
keeps track of its vertices by indexing into the global list of coordinates.

[1]
```
o plane
v 0 0 2
v 0 2 0
v 2 0 0
f 1 2 3
# note missing o <name>
v 1 1 0
v 1 0 0
v 0 1 0
v 0 0 0
g curve
cstype bspline
curv 0 1 -1 -2 -3 -4
...
```
July 20, 2020, 11:23 (GMT)
GHOST: Vulkan: Add physical device & queue family selection
July 20, 2020, 11:14 (GMT)
Animation: Fix MSVC warning about C incompatibility of `AnimationEvalContext`

Thanks @JacquesLucke for pointing this out.

No functional changes.
July 20, 2020, 11:02 (GMT)
BLI: add Vector/Array.fill methods
July 20, 2020, 10:16 (GMT)
Refactor: Update integer type usage

This updates the usage of integer types in code I wrote according to our new style guides.

Major changes:
* Use signed instead of unsigned integers in many places.
* C++ containers in blenlib use `int64_t` for size and indices now (instead of `uint`).
* Hash values for C++ containers are 64 bit wide now (instead of 32 bit).

I do hope that I broke no builds, but it is quite likely that some compiler reports
slightly different errors. Please let me know when there are any errors. If the fix
is small, feel free to commit it yourself.
I compiled successfully on linux with gcc and on windows.
July 20, 2020, 09:51 (GMT)
T77086 Animation: Passing Dependency Graph to Drivers

Custom driver functions need access to the dependency graph that is
triggering the evaluation of the driver. This patch passes the
dependency graph pointer through all the animation-related calls.

Instead of passing the evaluation time to functions, the code now passes
an `AnimationEvalContext` pointer:

```
typedef struct AnimationEvalContext {
struct Depsgraph *const depsgraph;
const float eval_time;
} AnimationEvalContext;
```

These structs are read-only, meaning that the code cannot change the
evaluation time. Note that the `depsgraph` pointer itself is const, but
it points to a non-const depsgraph.

FCurves and Drivers can be evaluated at a different time than the
current scene time, for example when evaluating NLA strips. This means
that, even though the current time is stored in the dependency graph, we
need an explicit evaluation time.

There are two functions that allow creation of `AnimationEvalContext`
objects:

- `BKE_animsys_eval_context_construct(Depsgraph *depsgraph, float
eval_time)`, which creates a new context object from scratch, and
- `BKE_animsys_eval_context_construct_at(AnimationEvalContext
*anim_eval_context, float eval_time)`, which can be used to create a
`AnimationEvalContext` with the same depsgraph, but at a different
time. This makes it possible to later add fields without changing any
of the code that just want to change the eval time.

This also provides a fix for T75553, although it does require a change
to the custom driver function. The driver should call
`custom_function(depsgraph)`, and the function should use that depsgraph
instead of information from `bpy.context`.

Reviewed By: brecht, sergey

Differential Revision: https://developer.blender.org/D8047
July 20, 2020, 09:28 (GMT)
Work in progress to treat nary boolean differently.

This will make it faster. There's one bug in it still,
but committing progress.
July 20, 2020, 09:12 (GMT)
Merge branch 'master' into lanpr-under-gp
July 20, 2020, 09:11 (GMT)
Merge branch 'master' into greasepencil-object
July 20, 2020, 09:11 (GMT)
Merge branch 'master' into greasepencil-edit-curve
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021