Blender Git Commits

Blender Git commits from all branches.

Page: 182 / 2888

August 5, 2021, 12:24 (GMT)
Merge branch 'master' into temp-geometry-nodes-expandable-geometry-socket-prototype
August 5, 2021, 11:12 (GMT)
Merge branch 'master' into soc-2021-uv-editor-improvements-edge-selection
August 5, 2021, 10:34 (GMT)
Cycles X: Bring back per-object GI approximation AO distance

Measure no performance impact beyond noise deviation on RTX6000:
```
cycles-x new
barbershop_interior 14.4251s 14.2849s
bmw27 9.5182s 9.1225s
classroom 17.1786s 17.1967s
junkshop 18.3849s 18.8356s
monster 9.9017s 9.5428s
pabellon 8.0902s 8.1711s
```

Differential Revision: https://developer.blender.org/D12138
August 5, 2021, 10:25 (GMT)
Bug Fix with close loop on poly splines
August 5, 2021, 10:02 (GMT)
Bug fix: loop closes when same endpoint selected
August 5, 2021, 09:55 (GMT)
Removed vertex select when altering segment
August 5, 2021, 09:53 (GMT)
Added comments
August 5, 2021, 09:43 (GMT)
Suppressed several build warnings
August 5, 2021, 09:39 (GMT)
Removed unused include headers
August 5, 2021, 09:39 (GMT)
adaptive_cloth: AdaptiveMesh: splittable edges indices set changes

Earlier, an edge wouldn't be tested for if one of it's verts was
already selected (for another edge). This would seems almost correct
but leads to non symmetrical remeshing. So it makes sense to get all
the splittable edges, sort them based on their size and then split the
edge only if it still exists in the mesh.

So changes added:
Give the entire set of splittable edges instead of maximally
independent.
Sort the set based on the edge size.
August 5, 2021, 08:48 (GMT)
Merge branch 'master' into asset-greasepencil
August 5, 2021, 08:35 (GMT)
adaptive_cloth: fix: AdaptiveMesh: anisotropic flip check

Based on the next paper by the same authors, "Folding and Crumpling
Adaptive Sheets". The edge flip criterion is different. So using this
now.
August 5, 2021, 08:06 (GMT)
Fix compiler warnings: unused variables
August 5, 2021, 05:44 (GMT)
adaptive_cloth: fix: mesh: flip edge: edge might already exist

It is possible that there might already be an edge between ov1 and ov2
so it is best to not create a new edge between those because edges
between verts should always be unique for all the algorithms to work
correctly.

It is a case that shouldn't show up too often but when it does, it
will be interesting to see what happens in the static remeshing
part. The number of faces remains the same but number of edges can
change (reduce only).
August 5, 2021, 03:40 (GMT)
Fixed error in python UI code, and error in caching acceleration.
August 5, 2021, 02:40 (GMT)
Merge branch 'master' into soc-2021-curves
August 5, 2021, 02:37 (GMT)
Select adjacent vertices when moving a segment
August 5, 2021, 01:46 (GMT)
Enable OmniPanel addon on startup

Added C calls to enable the OmniPanel addon
on startup.
August 5, 2021, 01:31 (GMT)
Pull latest addons_contrib umm_add_on branch

This update includes the OmniPanel addon.
August 4, 2021, 23:13 (GMT)
Merge branch 'master' into temp-geometry-nodes-fields-prototype
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021