Changeset View
Changeset View
Standalone View
Standalone View
manual/physics/baking.rst
| Show All 31 Lines | .. figure:: /images/physics_baking_multi-cache-interface.png | ||||
| :align: right | :align: right | ||||
| Two different caches stored simultaneously. | Two different caches stored simultaneously. | ||||
| Caches List | Caches List | ||||
| Blender allows for storing and managing multiple caches at once for the same physics object. | Blender allows for storing and managing multiple caches at once for the same physics object. | ||||
| You can manage the caches with this :ref:`list view <ui-list-view>`. | You can manage the caches with this :ref:`list view <ui-list-view>`. | ||||
| Double-click the cache entry to give it a name. | |||||
| Options | Options | ||||
| ======= | ======= | ||||
| Cache Name | |||||
| Each Cache can have a name. If this name is given, any disk cache will be | |||||
| stored in files starting with that name. For example, a cache named 'MyCache' | |||||
| will be stored in ``MyCache_xxxxxx_yy.bphys``. | |||||
| If the cache does not have a name (which is the default), the filename of the | |||||
Blendify: `If this field is empty` | |||||
Done Inline ActionsThe thing is, it's not really an input field, just a list entry you can double-click. Maybe "If the cache does not have a name"? sybren: The thing is, it's not really an input field, just a list entry you can double-click. Maybe "If… | |||||
| cache will depend on the object it is attached to, although this is not | |||||
| immediately obvious. For example, a cache on an object ``Cube`` will be | |||||
| stored in ``43756265_xxxxxx_yy.bphys``, where ``43756265`` is determined by | |||||
| the object name. | |||||
| .. warning:: | |||||
| When there are multiple caches on one object, **always specify a Cache Name**. | |||||
Not Done Inline ActionsWhen there are multiple caches for one object, **always specify a Cache Name**. sounds better Blendify: `When there are multiple caches for one object, **always specify a Cache Name**`. sounds better | |||||
Done Inline ActionsI wouldn't use "caches for" here; I see the cache as 'for' the particle system. It's connected to the object, though, which is why I used 'on' here. "always specify a Cache Name" is good. sybren: I wouldn't use "caches for" here; I see the cache as 'for' the particle system. It's connected… | |||||
| As described above, the filename of an unnamed cache is determined by the | |||||
| name of the object it is attached to. As a result, an object with multiple | |||||
| physics systems that all have an unnamed cache will cause conflict and | |||||
| **can result in losing cache files**. | |||||
Not Done Inline ActionsDon't bold again it is overly aggressive once is enough. Blendify: Don't bold again it is overly aggressive once is enough. | |||||
Done Inline ActionsIt's not my intention to be aggressive, but to produce something that is scannable, rather than requiring people to read every word carefully (because they don't). I'm basing this on https://www.nngroup.com/articles/how-users-read-on-the-web/. sybren: It's not my intention to be aggressive, but to produce something that is scannable, rather than… | |||||
| Disk Cache | Disk Cache | ||||
| The cache of a baked simulation will be stored inside the blend-file when you save it. | The cache of a baked simulation will be stored inside the blend-file when you save it. | ||||
| When *Disk Cache* is checked, Blender will save the Cache separately to the drive | When *Disk Cache* is checked, Blender will save the Cache separately to the drive | ||||
| in a folder named ``blendcache_[filename]`` alongside the blend-file. | in a folder named ``blendcache_[filename]`` alongside the blend-file. | ||||
| (The blend-file must be saved first.) | (The blend-file must be saved first.) | ||||
| Use Library Path | Use Library Path | ||||
| Share the disk cache when the physics object is | Share the disk cache when the physics object is | ||||
| ▲ Show 20 Lines • Show All 98 Lines • Show Last 20 Lines | |||||
If this field is empty