Blender Git Commits

Implement scaling imported/exported objects.

Merge branch 'master' into alembic_basic_io

Fix for missing updates when opening a file.

Add option to setup scene's frame range based on that of the imported
archive.

Slight refactor of the mesh exporting code.

Move most functions to gather data out of the AbcMeshWriter class into
static utility functions.

Use a hash map to store object reader / object path pair to be able to
reconstruct the object hierarchy more easily.

The previous approach was brute forcing by iterating over all the
objects in the scene for each object creating to find the object
(parent) that has the same name as its parent in the abc archive.

This was both inefficient and prone to errors since multiple objects in
the abc archive can have the same name, as long as their path are
different, but Blender only allows for unique object name, so the wrong
object could have been choosen as the parent of a given object.

Now all of the tests file import correctly.

Merge branch 'master' into alembic_basic_io

Cleanup: includes.

Fix for missing modifier update when enabling the new depsgraph.

Cleanup: extra qualifier.

Fix crash dereferencing null BoundBox pointer.

Add new transform cache constraint in the new depsgraph.

Exporter: remove AbcShapeWriter class.

It was only used to compute the bbox of the object, and added some
unecessary code complexity.

Various cleanups:

- move AbcEmptyReader to abc_transform.cc/h
- use pragmas for includes
- add separators in the code to help keeping things separated.

Merge branch 'master' into alembic_basic_io

Fix typo in some previous commit.

Add Alembic version to the system info module.

Cleanupo: de-duplicate some code.

Merge branch 'master' into alembic_basic_io

Improve (fix a few bugs in) the transform hierarchy creation.

Now an empty is created for every transform node except for the cases
when the transform node only has a single child that is not a transform
itself.

There are still a few issues in complex hierarchies where multiple
objects have the same name (which is legal in Alembic since it is the
whole path to the object that counts, not just the name).