Blender Git Loki

Merge branch 'usd-importer-T81257-merge' of https://gitlab-master.nvidia.com/omniverse/blender into omniverse

USD Import format fixes.

Add a little todo list

USD Import: not importing subdiv by default.

Changed the Import Subdive Scheme option default to false,
because this option can make large scenes considerably heavier
and because it needs to be further debugged.

Move component implementations to separate files

Merging latest USD Import changes.

USD Import: made USDPrimReader destructor virtual.

Geometry Nodes: Expose vertex normals as an attribute

This attribute exposes mesh vertex normals as a `vertex_normal`
attribute for use with nodes. Since the normal vector stored in
vertices is only a cache of data computable from the surrounding faces,
the attribute is read-only. A proper error message for attempting to
write this attribute is part of T85749. A write-only normal attribute
will likely come later, most likely called `corner_normal`.

The normals are recomputed before reading if they are marked dirty.
This involves const write-access to the mesh, protected by the mutex
stored in `Mesh_Runtime`. This is essential for correct behavior after
nodes like "Edge Split" or nodes that adjust the position attribute.

Ref T84297, T85880, T86206

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

USD Import: USD Preview conversion.

Added experimental Import USD Preview option to convert
UsdPreviewSurface shaders to Principled BSD shader networks,
for an approximate preview. Added new USDMaterialReader
class, which implements this feature. Also added a
Set Material Blend option to automatically set the material
blend method based on the UsdPreviewSurface shader's opacity
and opacityThreshold inputs. Finally, updated the logic so that
no materials will be imported if the Materials option is
not checked.

Merge branch 'master' into temp-gpencil-bezier-v2

Geometry Nodes: Sort attribute search items when menu opens

Because the search didn't run when the menu first opens, the attributes
appeared in a different order than after you typed anything into the
search field. This commit instead runs the search when the menu
is first opened, but it only sorts items without filtering.

Merge branch 'master' into temp-lineart-contained

Merge branch 'master' into temp-gpencil-io

Merge branch 'master' into greasepencil-object

Cleanup: Remove redundant special handling after previous commit

Not needed anymore since 3a907e742507.

Outliner: Barebones to port IDs to new Outliner tree-element code design

Continuation of work in 2e221de4ceee and 249e4df110e0 .
This prepares things so we can start porting the individual ID types to
the new code design. I already added some code for library IDs, because
they need some special handling during construction, which I didn't want
to break.

The `AbstractTreeElement::isExpandValid()` check can be removed once
types were ported and can be assumed to have a proper `expand()`
implemenation.

Also makes `TreeElementGPencilLayer` `final` which I forgot in
e0442a955bad.

Fix various CUDA issues fater recent change

- Strict compiler warnings in the CUDADeviceQueue
- Missing install file for the megakernel

fix missing updates when only the transformations are animated

Fix incorrect assert in Outliner ID deletion

Mistake in aa3a4973a30f. The expanded `ELEM()` check would include
`0 && te->idcode != 0`, which always evaluates to `false`/`0`. That
wouldn't cause the asset to fail, but the `te->idcode` part would never
be checked.

Fixed the error and cleaned up the check against "0" with a check
against `TSE_SOME_ID`, see b9e54566e3b1a.

Cleanup: Add & use enum value for ID Outliner element type

Code to check if the Outliner tree-element type was the general ID one
would always check against "0" (explicity or even implicitly). For
somebody unfamiliar with the code this is very confusing. Instead the
value should be given a name, e.g. through an enum.

Adds `TSE_SOME_ID` as the "default" ID tree-element type. Other types
may still represent IDs, as I explained in a comment at the definition.

There may also still be cases where the type is checked against "0". I
noted in the comment that such cases should be cleaned up if found.