Blender Git Loki

Cleanup: Use array as a parameter for event x/y functions

This change simplifies the parameter list for these functions
and reduces the chance of typos mixing up array indices.

Missed in rB69102786047dccdcbaee0df6307a8c3364d28fe0.

VSE: Add 2D cursor overlay option

Since 2D cursor will be used rarely in VSE and it is adding visual
noise, it will be hidden by default.

Reviewed By: campbellbarton

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

Cleanup: Remove dead code

Cleanup: Use array as a parameter for event x/y functions

This change simplifies the parameter list for these functions
and reduces the chance of typos mixing up array indices.

Missed in rB69102786047dccdcbaee0df6307a8c3364d28fe0

Cleanup: use underscore separators for event struct members

Improve readability using underscores for separators, e.g.
prev_click_time instead of prevclicktime.

Cleanup: Use array as a parameter for event x/y functions

This change simplifies the parameter list for these functions
and reduces the chance of typos mixing up array indices.

Reviewed By: campbellbarton

Ref D12950

Cleanup: Set default snap cursor values during build time

Fix failing 'script_validate_keymap' after recent changes

Properties with `_funcs_runtime` are always saved when exporting keymaps.

This is an error since changing one changes all others.

For now, work around the problem by setting the `PROP_IDPROPERTY` flag.

Fix: Empty id attribute on curve control points

No virtual array should be returned instead of returning an empty span.

Fix: Builtin curve attributes unavailable

After the addition of the `id` attribute in rB40c3b8836b7a, the `exists`
function assumed that all attributes were stored in the custom data.

Fix T92369: Raycast node crash with no target attribute

The corrected hit mask should only be generated when there is
data to transfer. Also correct two of the warning messages.

Fix: Add cast to atof for CYCLES_CONCURRENT_STATES_FACTOR env variable parsing.

The conversion from double to float was causing a build failure.

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

Fix: Crash when retrieving output "id" attribute

The attribute provider needs to handle the case where the data is stored
with just a data type, and the case where it is stored with a name.

Fix missing null-terminator in BLI_string_join_arrayN

Although the documentation says so, the null-terminator was missing.
This could cause crashes when logging shader linking errors as shader
sources are empty in this case.

UI: Remove extra padding on Annotate tool settings

For some reason the Annotate tool has an extra padding when compared to
other tools. This makes the UI to flicker a bit (specially with D12939
applied).

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

Geometry Nodes: Add warnings for instances input in two nodes

Certain geometry nodes don't work properly on inputs that contain
instances, but don't display any warning that they aren't working.

The nodes now will display a warning that explains the situtation
iff the input contains any instances.

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

Cleanup: remove unused code

New test for USD import.

Added a basic test for importing a primitive hierarchy from a USDA
file into Blender. This was reviewed by Sybren in patch D12479.

Geometry Nodes: Make Random ID a builtin attribute, remove sockets

In order to address feedback that the "Stable ID" was not easy enough
to use, remove the "Stable ID" output from the distribution node and
the input from the instance on points node. Instead, the nodes write
or read a builtin named attribute called `id`. In the future we may
add more attributes like `edge_id` and `face_id`.

The downside is that more behavior is invisible, which is les
expected now that most attributes are passed around with node links.
This behavior will have to be explained in the manual.

The random value node's "ID" input that had an implicit index input
is converted to a special implicit input that uses the `id` attribute
if possible, but otherwise defaults to the index. There is no way to
tell in the UI which it uses, except by knowing that rule and checking
in the spreadsheet for the id attribute.

Because it isn't always possible to create stable randomness, this
attribute does not always exist, and it will be possible to remove it
when we have the attribute remove node back, to improve performance.

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

Cycles: reduce kernel reserved local memory when not using shader raytracing

Ref T87836