Blender Git Loki

Blenderin Git "master"-kehityshaaran kommitit.

Page: 254 / 5574

Revision 711ddea by Hans Goudey
June 2, 2021, 03:50 (GMT)
Fix assert with geometry node output

The previous commit (my own) returned early without providing a value
for the node's output geometry set, which is required.
Revision 6b5bbd2 by Hans Goudey
June 1, 2021, 21:51 (GMT)
Cleanup: Avoid duplicating node input retrieval

Pass the selection name and the invert argument to each component
instead of retrieving them every time.
June 1, 2021, 21:32 (GMT)
Geometry Nodes: Add Delete Geometry Node

This node is similar to the mask modifier, but it deletes the elements
of the geometry corresponding to the selection, which is retrieved as
a boolean attribute. The node currently supports both mesh and point
cloud data. For meshes, which elements are deleted depends on the
domain of the input selection attribute, just like how behavior depends
on the selection mode in mesh edit mode.

In the future this node will support curve data, and ideally volume
data in some way.

Differential Revision: https://developer.blender.org/D10748
June 1, 2021, 21:06 (GMT)
VSE: Use own category for metadata panel

Metadata panel was visible in each category. In other editors, this
panel is usually placed in category with other source media properties.
In sequencer, metadata is transfered over while compositing and relation
to particular strip is lost, therefore separate category for metadata
seems to be best option. Since Metadata panel is alone in this category,
it will be open by default.
Revision 17b09b5 by Hans Goudey
June 1, 2021, 16:03 (GMT)
Geometry Nodes: Skip calculating normals in transform node

This commit skips the eager recalculation of mesh normals in the
transform node. Often another deformation or topology-altering
operation will happen after the transform node, which means the
recalculation was redundant anyway.

In one of my test cases this made the node more than 14x faster.
Though depending on the situation the cost of updating the normals
may just be shifted elsewhere.
June 1, 2021, 15:54 (GMT)
Fix T88715: particle size influence texture not working for 'keyed' or 'none' physics types

This was reported for the special case of mapping with "Strand /
Particle" coords, but was not working with other coordinates either.

Dont see a reason for not supporting Size influence textures for these
kinds of particles (and since these types of particles have an "age"
like all others as well, even the "Strand / Particle" coords are
supported here as well)

Maniphest Tasks: T88715

Differential Revision: https://developer.blender.org/D11449
June 1, 2021, 15:37 (GMT)
LibOverride: Fix again infinite loop in resync in some complex/degenerated cases.

Broken in recent refactor of (recursive)resync, reported by studio,
thanks.
June 1, 2021, 13:25 (GMT)
Geometry Nodes: add empty material slot to new meshes

This fixes T88455 by adding an empty material slot to newly
generated meshes. This allows the object to overwrite the
"default" material without any extra nodes. Technically,
all polygons reference the material index 0 already, so it
makes sense to add a material slot for this material index.

Differential Revision: https://developer.blender.org/D11439
June 1, 2021, 13:18 (GMT)
BuildBot: Cleanup

Removing scripts that were placed in the source tree that would drive
the old buildbot. With the new buildbot in place these scripts aren't
being used anymore.

The buildbit is currently driven by
`build_files/config/pipeline_config.json`. In the near future make
update would also use this config.

Overview of the new buildbot: https://wiki.blender.org/wiki/Infrastructure/BuildBot

Work done by James Monteath.
June 1, 2021, 11:38 (GMT)
Fix T88658: Force Fields of curve shape can crash if curve has only one point

`bvhtree_from_mesh_edges_create_tree` can actually leave the BVHTree
NULL (e.g. if no edges are present).

Now dont allocate `BVHTreeFromMesh` on the `SurfaceModifierData` at all
in case the tree would be NULL anyways.
Places like `get_effector_data` check for `SurfaceModifierData`-
>`BVHTreeFromMesh` and dont try to stuff like getting a closest point on
surface, which would crash as soon as BVHNodes would need to be accessed
(from the NULL BVHTree).

Maniphest Tasks: T88658

Differential Revision: https://developer.blender.org/D11443
June 1, 2021, 11:18 (GMT)
DrawManager: Use CPP for Mesh Extraction Scheduling.

More cleanups will come to make this more CPP-like.
June 1, 2021, 11:18 (GMT)
Cleanup: API for MeshExtractRunTimeData.
June 1, 2021, 11:18 (GMT)
Cleanup: NULL->nullptr.
June 1, 2021, 11:18 (GMT)
Cleanup: remove unused parameter.
June 1, 2021, 11:18 (GMT)
Cleanup: remove unused parameter.
June 1, 2021, 10:29 (GMT)
Cleanup: LibOverride: rename 'local' group tagging functions to 'overrides'.

Since we use them on linked data now as well, 'local' does not fit them
anymore.
June 1, 2021, 10:01 (GMT)
ID Management: Allow unique name check for linked IDs too.

This is mandatory for liboverride resync, since this feature may imply
we have to create linked overrides in libraries, and there may be
several copies of those.

This is also a first step to a more general support of IDmanagement-editing
library data.

Note that this commit should have absolutely no effect on current code,
as the only function allowed to check unique names for linked IDs
currently is `BKE_libblock_management_main_add`, which is unused.

This commit also adds some basic testing for `BKE_id_new_name_validate`.
June 1, 2021, 10:01 (GMT)
Fix `BLI_libblock_ensure_unique_name` not ignoring linked IDs.

This function would considere that there was a name conflict even in
case existing ID would be a linked one.

This is only a (symbolic) perforance improvement and logical fix, since
`BKE_id_new_name_validate` would not do that mistake anyway.
June 1, 2021, 10:01 (GMT)
IDManagement: `BKE_libblock_rename`: assert we get local ID.

For now at least, linked data should never be renamed that way.
June 1, 2021, 10:01 (GMT)
Fix libOverride resync issues in some corner-cases.

This commit fixes two different issues:
* In some cases, when an object was added to a sub-collection and used
into a different subcollection, and the root common collection would
not need to be resynced, it would end up creating multiple overrides
of the new object. This was affecting both normal and recursive
resync.
* In recurisve resync case, the barrier code to define what is part or
not of a override group/hierarchy was wrong.

Note that the current solution for the first issue is sub-optimal (it
goes back to the root of the override hierarchy and resync the whole
thing), a better solution is TODO for now.
Tehnyt: Miika HämäläinenViimeksi päivitetty: 07.11.2014 14:18MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021