March 23, 2015, 11:21 (GMT) |
Removed unused line. |
March 23, 2015, 11:21 (GMT) |
Unlink and cleanup functions when objects or the cached group get unlinked or changed. |
March 23, 2015, 11:21 (GMT) |
Make sure cache item pointers are lib-linked correctly. |
March 23, 2015, 11:21 (GMT) |
Name string construction for cache items, to use as a unique identifier in the cache library. |
March 23, 2015, 11:21 (GMT) |
Draw some UI buttons for all the current cache item types. |
March 23, 2015, 11:21 (GMT) |
Updated hash table for lookup of enabled cache items and added basic UI support. |
March 23, 2015, 11:21 (GMT) |
Improved collections in RNA for looping over potential caching items in the object group. |
March 23, 2015, 11:21 (GMT) |
Define a collection of "object_caches" in the CacheLibrary RNA for iterating over all objects eligible for caching in the group. This allows for nested dupligroup instances as well. All objects that are instantiated at least once by any group can be included in the respective cache, but get represented only once because the cached data is the same anyway. |
March 23, 2015, 11:21 (GMT) |
Link main CacheLibrary pointers in readfile. |
March 23, 2015, 11:21 (GMT) |
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. |
March 23, 2015, 11:21 (GMT) |
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 |
March 23, 2015, 11:21 (GMT) |
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. |
March 23, 2015, 11:21 (GMT) |
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. |
March 23, 2015, 11:21 (GMT) |
Missing include. |
March 23, 2015, 11:21 (GMT) |
Removed meaningless comment. |
March 23, 2015, 11:21 (GMT) |
`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 |
March 23, 2015, 11:21 (GMT) |
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 Conflicts: source/blender/makesrna/intern/rna_main_api.c |
March 23, 2015, 11:20 (GMT) |
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. |
March 23, 2015, 11:17 (GMT) |
Merge branch 'master' into depsgraph_refactor Conflicts: source/blender/editors/object/object_constraint.c source/blender/render/intern/source/pipeline.c |
March 23, 2015, 11:12 (GMT) |
PointCache modifier to act as a terminator in modifier stacks. When writing DerivedMesh data, the modifier result at the point of the modifier will be used for writing to the cache. If this modifier is not used the derivedFinal mesh is used instead. |
|
|
|


Master Commits
MiikaHweb | 2003-2021