Blender Git Loki

Fix T76132: Can't export Alembic with changing UVs

In the Alembic exporter, UVs were only exported on the first frame. This
is an issue, as when exporting an animated mesh the topology can change,
and then the UV coordinates of the first frame are no longer valid.

T76132 concerns both exporting and importing changing UVs. This fixes
the exporting.

Fix T76669: Crash when doing right click on channel

Reviewers: lichtwerk, sybren

Differential Revision: https://developer.blender.org/D7702

Merge branch 'blender-v2.83-release'

Merge branch 'blender-v2.83-release'

Merge branch 'blender-v2.83-release'

Merge branch 'blender-v2.83-release'

Fix T76507: Reading clipboard blocks keyboard input on X11

Cleanup: tag unused function

Fix T76514: Invalid geometry in Alembic crashes Blender

Even though {T76514} is caused by invalid geometry, and thus technically
constitutes a bug in the software that created the Alembic file, I would
like Blender not to crash on importing such a file.

The error in the Alembic file consists of invalid mesh loops, where
consecutive loops refer to the same vertex. The `BKE_mesh_validate()`
can actually correct these errors, so this commit focuses on two things:

- Letting Blender survive the situation until the mesh is loaded, and
- Detecting the error so that `BKE_mesh_validate()` can be called only
when necessary. This ensures there is only a minimal impact on
performance when loading actually valid data.

Differential Revision: https://developer.blender.org/D7703

Reviewed By: JacquesLucke

Fix T74818: improve tooltip for initial fluid velocity

Fix Frame Dropping not dropping the correct amount of frames

Previously the playback mode "Frame Dropping" would not drop the correct
number of frames which would lead to slow playback.

For example, the playback target is 60fps. However we can only muster
around 32 fps.

The delta frames from the last step is in this case ~1.98 or so.

With the previous code, we would floor this. That would lead us to step
forward one frame each time, effectively playing back the animation at
half the speed as we will try to render every frame.

To fix this we simply save the remaining fraction from the previous
frame and use it to compute the current frame step.

Reviewed By: Sybren

Differential Revision: https://developer.blender.org/D7694

UI: invoke operators in search menu instead of execute

Reviewers: campbellbarton

Differential Revision: https://developer.blender.org/D7639

Merge branch 'blender-v2.83-release'

Fix T75492: Only positive shrink factor values can be animated

A better fix would probably be to check if the value is animated,
but I'm not sure how to do that.

Reviewers: zeddb

Differential Revision: https://developer.blender.org/D7692

Merge branch 'blender-v2.83-release'

Fix T75889: Cannot bake mantaflow via Python API

The issue was the usage of the global `__main__` Python module.
When running scripts in the text editor, Blender would overwrite
the `__main__` module.

Reviewers: sebbas

Differential Revision: https://developer.blender.org/D7690

Fluid: remove special treatment for running Python code on windows

We discussed this in D7690 and could not find a reason for this
code anymore. It might just be leftover from some even older code.

Cleanup: Remove print statement

Preferences: Customize default empty size for collection instances

The old value (1.0) was often too large in practice. When many collection
instances are created, the large empties create a mess in the viewport.

This adds a new preference setting in `Editing -> Objects -> New Objects`
called `Instance Empty Size`.

The value will be used as display size for new empties containing a
collection instance.

Reviewers: Severin

Differential Revision: https://developer.blender.org/D7650

Merge branch 'blender-v2.83-release'