March 26, 2015, 13:13 (GMT) |
Fix for cache item filtering: items can be part of the cache library but disabled, in that case hide them as well. |
March 26, 2015, 13:13 (GMT) |
Tessface customdata for derived mesh caching. |
March 26, 2015, 13:13 (GMT) |
Support CD_ORIGSPACE layer caching. This is needed by particles for distributions on meshes with changed topology (which is of course broken). |
March 26, 2015, 13:13 (GMT) |
Support for CustomData in Alembic caches. This is a skeleton feature that provides a general way of storing CustomData types. Currently only ORIGINDEX layers are implemented, the code is designed to make extension easy. Storing CustomData layers in Alembic is a bit involved because the complex structs often used as customdata need to be de-interleaved for Alembic into a set of POD (plain-old-datatype) array properties. In addition the property names should be unique, so that mapping abc properties back to customdata layers is safe. This works by using 2 levels of compound properties: the first level stored per CD type properties, with a number of properties for each layer of this type, using either a name or index (for unnamed layers). The internal properties can then in turn be compounds, if structs need to be serialized into PODs. Abc property readers/writers are created dynamically for the CustomData compounds. This is necessary because we don't know in advance what kind of data layers a DerivedMesh or other CD user will have, and this can change each frame in theory. Alembic is easier with state data schemes, but using it this way is possible (if somewhat cumbersome). |
March 26, 2015, 13:13 (GMT) |
Fixed test for "render" eval mode for hair dynamics. This is totally weird and convoluted, no idea if correct. Conflicts: source/blender/blenkernel/intern/particle_system.c Conflicts: source/blender/blenkernel/intern/particle_system.c |
March 26, 2015, 13:12 (GMT) |
Removed the DM writer/reader from hair dynamics again, this is part of the particle stuff and does not work. |
Revision 15e3298 by Sergey Sharybin / Lukas Toenne (alembic, gooseberry, gooseberry_farm, temp_motionpaths) March 26, 2015, 13:12 (GMT) |
Alembic: Fixes for linux buildbot and scons |
March 26, 2015, 13:12 (GMT) |
Use a combined class for hair dynamics for cloth and mesh data. Particles store a copy of the DM internally as the emitter. |
March 26, 2015, 13:12 (GMT) |
Minor fix for UI code showing cache items. |
March 26, 2015, 13:12 (GMT) |
Left a comment in DerivedMesh.c explaining why the caching system has to use the cumbersome cachedm pointer instead of virtual modifiers. |
March 26, 2015, 13:12 (GMT) |
Use a dedicated input_dm pointer in the cache modifier to provide a mesh result read from the cache. Mixing this with the output_dm used for writing leads to undefined situations where the DM was released but should actually be passed on. |
March 26, 2015, 13:12 (GMT) |
Use correct flag enums for checking render/viewport eval mode when writing derived mesh caches. |
March 26, 2015, 13:12 (GMT) |
Convenience feature: When linking a cache library, always default it to 'read' mode locally. Linking a cache library is meant to be used for getting existing cache data into a file. |
March 26, 2015, 13:12 (GMT) |
Fix for meaningless build error (no return value, can never happen). |
March 26, 2015, 13:12 (GMT) |
Depsgraph tagging function for cached objects. This is necessary to trigger object data updates for indirectly linked objects, which would otherwise not be evaluated. |
March 26, 2015, 13:12 (GMT) |
Archive Info operator for Cache Library archives. This creates a string with information about all the objects and properties contained within a (Alembic) archive, used by a cache library. The operator has 3 modes of presenting the info string: - stdout, ie. printing to the terminal - popup window (not very useful usually due to size limits and lack of scrolling) - clipboard copy |
March 26, 2015, 13:12 (GMT) |
Render/Viewport evaluation mode for cache libraries. This designates a cache library to be used either for the viewport or for renders. A "Render" cache library will evaluate modifiers with render settings and a "Viewport" cache library will use viewport (realtime) settings. When reading the cache, the library will only be used for the assigned purpose, i.e. a Render cache does not work for viewport caching and vice-versa (although a cache can be baked for one setting and then switched afterward). Note that render results will never be visible in the realtime viewport due to the way object evaluation is handled in Blender at this point (render settings are only evaluated explicitly during renderer sync). Conflicts: source/blender/blenkernel/intern/particle_system.c Conflicts: source/blender/blenkernel/intern/particle_system.c |
March 26, 2015, 13:12 (GMT) |
Ported archive filename constructor from pointcache library to BKE. The pointcache library is now pretty much independent from ID blocks and should not be responsible for handling file paths. The path construction is also fairly straightforward now compared to the old point cache system, with only basic conversion of relative to absolute paths for loading archive files. |
March 26, 2015, 13:12 (GMT) |
Removed now-unused util_path files from the pointcache lib. Paths are constructed outside this module now. A valid absolute path should always be provided through the API calls. |
March 26, 2015, 13:12 (GMT) |
Cache read result enum in DNA mirroring the internal pointcache results. This can be stored in cache library items as an indicator of cache reading state. |
|