Blender Git Commits

Simplified cache item path description, based on plain ID blocks with
subtype/index.

This omits possible instancing and recursion by dupli groups, but since
the data of instances is always the same in Blender at this point, there
is little need to take them into account for caching.

At some point in the future it may become desirable to store full dupli
hierarchies in the cache, but it doesn't make sense to try to design a
fully-fledged path descriptor for this hypothetical case now.

BKE functions for managing cache content based on a group.

This uses a complete hierarchy of group instances, based on a path
hierarchy (object names).

Putting

Simple cache manager panel UI in the scene buttons.

This is mostly a simple and unintrusive placeholder to have some way of
making caches accessible, but needs some more thought.

Group pointer property for cache libraries to associate them with an
object group.

This is somewhat experimental, eventually we may want to link to Objects
instead, or allow multiple cache targets for the same cache, etc.

Missing include.

Removed meaningless comment.

`New` operator for adding cache libraries.

Conflicts:
release/scripts/startup/bl_ui/properties_physics_common.py
source/blender/blenkernel/BKE_pointcache.h
source/blender/blenkernel/intern/pointcache.c
source/blender/editors/physics/physics_ops.c
source/blender/editors/physics/physics_pointcache.c

New ID datablock 'CacheLibrary', for managing physical cache archives
and files.

At it's core this is just a file path, but many different cache users
may refer to this, so having a dedicated ID block helps. It can be
compared to Image datablocks, which also primarily are used for data
on storage, but can be packed with the blend file, and carry some
additional information that would be cumbersome to keep sync'ed
otherwise.

The name 'CacheLibrary' deliberately resembles the 'Library' datablock:
just as a Library stores ID blocks in a physical file, a CacheLibrary
stores cached data (in Alembic HDF5/Ogawa or other formats).

Conflicts:
source/blender/blenkernel/BKE_pointcache.h
source/blender/blenkernel/intern/pointcache.c
source/blender/makesdna/DNA_pointcache_types.h

Fix for remaining PointCache references in the alembic code.

Now, for the time being, uses a simple relative "//blendcache/" folder
path again. This will be adressed later.

Big revert of all things pointcache, old code is impossible to work with.

The Alembic caching must be integrated with Blender as a new, entirely
independent feature. The old pointcache code can not be surgically
removed without major damage to vital features. Instead of wasting more
time trying to deal with an outdated complicated system, a better choice
is implementing a new caching system next to it and if possible phase
out the old one at some point ...

Merge branch 'master' into alembic_pointcache

Removed unused DNA field.

Use the cache library to construct cache file paths instead of the
relative point cache paths.

Use `cache` as a relative folder path for storing caches by default.

Display UI for cache library inside the point cache UI.

`New` operator for adding cache libraries.

Use a cache library pointer in point caches to replace the per-object
path construction.

Fix for cache panel display: the `is_baked` flag has been removed and
should not be used to disable cache UI any longer.

New ID datablock 'CacheLibrary', for managing physical cache archives
and files.

At it's core this is just a file path, but many different cache users
may refer to this, so having a dedicated ID block helps. It can be
compared to Image datablocks, which also primarily are used for data
on storage, but can be packed with the blend file, and carry some
additional information that would be cumbersome to keep sync'ed
otherwise.

The name 'CacheLibrary' deliberately resembles the 'Library' datablock:
just as a Library stores ID blocks in a physical file, a CacheLibrary
stores cached data (in Alembic HDF5/Ogawa or other formats).

Removed unused (and broken) functions for getting the number of written
cache samples.

This can be done more reliably using Alembic schemas.