blender-v4.2-release backports #130215

Philipp Oeser · 2024-11-13T11:31:03+01:00

Philipp Oeser commented

2024-11-13 11:31:03 +01:00

No response

_No response_

Philipp Oeser added 12 commits 2024-11-13 11:31:13 +01:00

Fix #128916 : Tag Light ID when applying scale 68db3949a9

When applying scale on a light in the viewport, ensure we tag the light
itself for updating. Otherwise, the viewport get confused over which
size to use.

Pull Request: #129030

Fix #129067 : Transforming an edit-mesh crashes with cage editing b8fa9c7520

Regression in [0] although prior to this the `deformed_only` was not
being set, caused by a separate regression.

[0]: 80fa49f24a

Fix #128805 : Missing Depsgraph Update when removing FCurve modifiers a4af50593d

The problem was that when removing FCurve modifiers via the python API
the Depsgraph wasn't notified.
Fixed by tagging the owner ID of the fcurve modifier for an update.

Pull Request: #128984

Fix #125451 : Duplicating bone doesn't copy pose bone colors e7330998b0

When duplicating a bone (has to be done in edit mode)
the pose bone colors were not copied.
This adds the code to do just that

This also fixes it for symmetrising because that uses the
same code path

Pull Request: #129007

Fix #129095 : Crash on wayland on startup without a "seat" bdfca55ff0

Running in a headless weston session was asserting, then crashing,
causing WITH_UI_TESTS to fail.

Resolve by accounting for a wayland sessions without a seat.

Cleanup: remove deprecated typing built-ins for extension logic 81546f30aa

Deprecated since Python 3.9 but still used in many docs/examples.

Fix #123963 : Unable to select through unselectable bones 8d0a2d3b1e

When trying to select bones that are inside other bones which are not selectable,
the selection would fail. This is inconsistent with object mode, where unselectable
things are just ignored.
This patch fixes it for pose mode and edit mode.
Note that there are two areas for edit mode that were modified.
The one in `ed_armature_pick_bone_from_selectbuffer/202` is never actually reached,
but I added the code there for completeness.

The code in `get_nearest_editbonepoint` had to be modified some more to
implement a similar logic as `armature_select.cc/220`

Pull Request: #129120

Fix #128997 : wrong evaluation of outputs in the Index of Nearest node f107c419b3

Pull Request: #128998

Fix #129205 : Crash when Cryptomatte picking while rendering 2501735fd7

Blender crashes when picking Cryptomatte while rendering. This is
because pass data are not yet allocated. To fix this, we just fail the
picking until data becomes available.

Fix #129167 : Operator search can hang for some operator names ca4f30d710

RNA label & description truncation could cause invalid UTF8
which caused BLI_string_search to hang.

Resolve by ensuring truncation of RNA descriptions & labels never
truncates a multi-byte sequences.

The issue with BLI_string_search would still be good to resolve but can
be handled separately.

Fix #129302 : GIL not released if poll_message_set was passed a string 0fae5283d8

Regression in [0].

Co-authored-by: Jorn Visser <git@jornvisser.com>

[0]: ebe04bd3ca

Fix #127097 : Extension preferences crashes after "import multiprocesing"

buildbot/vexp-code-patch-lint Build done.

Details

buildbot/vexp-code-patch-linux-x86_64 Build done.

Details

buildbot/vexp-code-patch-darwin-x86_64 Build done.

Details

buildbot/vexp-code-patch-darwin-arm64 Build done.

Details

buildbot/vexp-code-patch-windows-amd64 Build done.

Details

buildbot/vexp-code-patch-coordinator Build done.

Details

a51ca8ef17

Remove a workaround for #23871 which manipulated the module
to prevent classes defined in the text editor from having their
name-space cleared.

This caused the "multiprocessing" module to store the "__main__" module
as "__mp_main__" for later use.

Accessing attributes from this module would then attempt to read from
with a null "mp_dict" which crashed. This happened when showing the
extensions preferences but would have occurred if "__mp_main__" was
accessed from elsewhere too.

Resolve by removing the workaround since it has not been needed
since Python 3.2.

Philipp Oeser commented

2024-11-13 11:31:51 +01:00

@blender-bot build

Philipp Oeser added 6 commits 2024-11-13 12:10:57 +01:00

Fix #129323 : Slowdown adding/removing objects from Python 49734abcd4

Python scripts could perform actions that created notifiers
which would not be handled until the script was complete.

In the case of adding & removing objects a notifier would be created
for adding the object, then cleared when the ID was removed.

This lead to the notifier queue filling up with cleared notifiers
which were included in the search whenever an ID was removed.

The result of this was that adding and removing objects from a script
would become increasingly slower & use more memory.

Resolve by storing the current notifier being handed which isn't freed
(only cleared). The notifier handling loop detects cleared notifiers
and frees them after use.

Fix #125958 : Disable/uninstall an add-on can keep its dependencies 55eecb0dcf

Python wheels from extensions were not being removed after
install/uninstall in some cases - although installing an extension
afterwards that used wheels would recalculate deps & remove them.

- Installing an extension didn't include the extension in the
  compatibility-cache, causing uninstalling not to remove deps.
- Uninstalling an extension wasn't re-calculating the deps,
  leaving them as-is.

Always write the compatibility-cache after installing and uninstalling
so changes are detected & handled.

Fix memory leak pasting images in Wayland 1d5f3a5674

Fix #129401 : BMesh.clear() causes crash on garbage collection e82134cdcf

Fix missing lock in GHOST_SystemWayland::hasClipboardImage b6cb3ebb14

Fix #129420 : precision issue in light tree distant light angle

buildbot/vexp-code-patch-lint Build done.

Details

buildbot/vexp-code-patch-darwin-x86_64 Build done.

Details

buildbot/vexp-code-patch-linux-x86_64 Build done.

Details

buildbot/vexp-code-patch-windows-amd64 Build done.

Details

buildbot/vexp-code-patch-darwin-arm64 Build done.

Details

buildbot/vexp-code-patch-coordinator Build done.

Details

9773a228bc

In volume segment, the minimal angle formed by the emitter bounding cone
axis and the vector pointing from the cluster centroid to any point on
the ray is computed via `dot(bcone.axis, point_to_centroid)`, see Fig.8.
in paper.
For distant light this angle is 0, but due to numerical issues this is
not always true. Therefore explicitly assign `-bcone.axis` to
`point_to_centroid` in this case.

Pull Request: #129489

Philipp Oeser commented

2024-11-13 12:12:25 +01:00

@blender-bot build

Philipp Oeser merged commit 0046bf6b10 into blender-v4.2-release

2024-11-13 13:29:16 +01:00

Philipp Oeser referenced this issue from a commit

2024-11-13 13:29:18 +01:00

Fix #129420: precision issue in light tree distant light angle

Philipp Oeser deleted branch blender-v4.2-release

2024-11-13 13:29:21 +01:00

Sign in to join this conversation.

No reviewers