Blender Git Commits

USD: fixed copyright year in license blocks

USD: enable USD in Release configuration

USD: Replaced `#include "../usd.h"` with `#include "usd.h"`

USD: Also `include pxrTargets-release.cmake` when harvesting dependencies

USD: Added & corrected GPL license blocks

USD: Build improvements

- Removed the `USD_PATH` variable, expose `USD_ROOT_DIR` from `FindUSD.cmake`
instead.
- Properly call `find_package_wrapper(USD)` from `platform_unix.cmake`.
- Added USD files to `harvest.cmake`.
- Removed `external_python` from USD dependencies, as we don't use USD's
Python interface.
- Removed Fink and DarwinPorts support.
- Enable USD in `blender_full.cmake`

USD: build & install USD with 'make deps'

Automated test for USD's AbstractHierarchyIterator

USD: Introducing USD support

This commit introduces an exporter to Pixar's Universal Scene
Description (USD) format.

- The USD libraries are expected to be in /opt/usd/, not yet built by
install_deps.sh. I'll work on that while this patch is under review.
- Only experimental support for instancing; by default all duplicated
objects are made real in the USD file. This is fine for exporting a
linked-in posed character, not so much for thousands of pebbles etc.
- This patch contains LazyDodo's fixes for building on Windows in D5359.

== Meshes ==

USD seems to support neither per-material nor per-face-group
double-sidedness, so we just use the flag from the first non-empty
material slot. If there is no material we default to double-sidedness.

Each UV map is stored on the mesh in a separate primvar. Materials can
refer to these UV maps, but this is not yet exported by Blender. The
primvar name is the same as the UV Map name. This is to allow the
standard name "st" for texture coordinates by naming the UV Map as such,
without having to guess which UV Map is the "standard" one.

Face-varying mesh normals are written to USD. When the mesh has custom
loop normals those are written. Otherwise the poly flag `ME_SMOOTH` is
inspected to determine the normals.

The UV maps and mesh normals take up a significant amount of space, so
exporting them is optional. They're still enabled by default, though.
For comparison: a shot of Spring (03_035_A) is 1.2 GiB when exported
with UVs and normals, and 262 MiB without. We probably have room for
optimisation of written UVs and normals.

The mesh subdivision scheme isn't using the default value 'Catmull
Clark', but uses 'None', indicating we're exporting a polygonal mesh.
This is necessary for USD to understand our normals; otherwise the mesh
is always rendered smooth. In the future we may want to expose this
choice of subdivision scheme to the user, or auto-detect it when we
actually support exporting pre-subdivision meshes.

A possible optimisation could be to inspect whether all polygons are
smooth or flat, and mark the USD mesh as such. This can be added when
needed.

== Animation ==

Mesh and transform animation are now written when passing
`animation=True` to the export operator. There is no inspection of
whether an object is actually animated or not; USD can handle
deduplication of static values for us.

The administration of which timecode to use for the export is left to
the file-format-specific concrete subclasses of
`AbstractHierarchyIterator`; the abstract iterator itself doesn't know
anything about the passage of time. This will allow subclasses for the
frame-based USD format and time-based Alembic format.

== support for simple preview materials ==

Very simple versions of the materials are now exported, using only the
viewport diffuse RGB, metallic, and roughness.

When there are multiple materials, the mesh faces are stored as geometry
subset and each material is assigned to the appropriate subset. If there
is only one material this is skipped.

The first material if any) is always applied to the mesh itself
(regardless of the existence of geometry subsets), because the Hydra
viewport doesn't support materials on subsets. See
https://github.com/PixarAnimationStudios/USD/issues/542 for more info.

Note that the geometry subsets are not yet time-sampled, so it may break
when an animated mesh changes topology.

== Hair ==

Only the parent strands are exported, and only with a constant colour.
No UV coordinates, no information about the normals.

== Camera ==

Only perspective cameras are supported for now.

== Particles ==

Particles are only written when they are alive, which means that they
are always visible (there is currently no code that deals with marking
them as invisible outside their lifespan).

Particle-system-instanced objects are exported by suffixing the object
name with the particle's persistent ID, giving each particle XForm a
unique name.

== Instancing/referencing ==

This exporter has experimental support for instancing/referencing.

Dupli-object meshes are now written to USD as references to the original
mesh. This is still very limited in correctness, as there are issues
referencing to materials from a referenced mesh.

I am still committing this, as it gives us a place to start when
continuing the quest for proper instancing in USD.

== Lights ==

USD does not directly support spot lights, so those aren't exported yet.
It's possible to add this in the future via the UsdLuxShapingAPI. The
units used for the light intensity are also still a bit of a mystery.

== Fluid vertex velocities ==

Currently only fluid simulations (not meshes in general) have explicit
vertex velocities. This is the most important case for exporting
velocities, though, as the baked mesh changes topology all the time, and
thus computing the velocities at import time in a post-processing step
is hard.

Merge remote-tracking branch 'origin/master' into wip-ctest-blenloader

Merge remote-tracking branch 'origin/master' into wip-ctest-blenloader

Fixed memory leak

Deinitialisation of Blender

Blendfile-loading test class

To test some functionality of the USD exporter, I want to be able to load a blend file and run parts of the exporter. Up to now this wasn't possible from a GTest test. Of course a Python test could run the USD exporter, but testing the result would require writing a parser for USD files, which I want to avoid.

This new test class minimally sets up Blender so that it can load blend files and construct a depsgraph without crashing. Note that I haven't tested this on very complex blend files, so it may still crash when the loaded blend file references/requires uninitialised data structures.

The test will certainly crash with Blend files created with Blender 2.80, as the versioning code requires space types to be registered. This is normally done by initialising the window manager, which is not done in this test. The WM requires Python to run, which in turn requires that Blender finds the release directory in the same directory that contains the running executable, which is not the case for GTest tests (they are written to `bin/tests/executablename`.

This patch requires the functionality from {D6236}.

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

FIXUP for EXTRA_CLI

CMake/GTest: allow defining CLI arguments for GTEST tests

For USD tests I need to load a blend file from a GTest test, and in order to do that properly it needs to get the location of the lib/tests directory. The easiest way to do this is to pass it on the CLI.

To make it possible to extend the `BLENDER_SRC_GTEST_EX()` without adding yet more macros, it now accepts keyword arguments.

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

Header guard #define

More feedback from Sergey

Updated for review comments

- Removed link to CMake docs
- EXTRA_CLI ? COMMAND_ARGS
- BlendfileLoadingAbstractTest ? BlendfileLoadingBaseTest
- Moved BlendfileLoadingBaseTest into tests/gtests/blenloader
- Added failure message
- Check C++ string with a C++ string function
- Full stop.

Updated license blocks