> For the complete documentation index, see [llms.txt](https://docs.procedural-anatomy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.procedural-anatomy.com/nodes/simulation-nodes-1.0/anatomy-rig-skin.md).

# Anatomy Rig Skin

This node manages caching and transformation of skin tet mesh to final render mesh for the skin.

Internally there are two possible cache states, the first is Tissue Simulation and intended to be spot checking the tissue simulation. The second, called Skin enables cashing of the resulting deformation back on to the original model used to create your character.

#### Parameters

Both of these present an Automatic, Force Off, Force On options. These represent loading the caches. Automatic will only load if the cash is present, forcing on or off will do just that and force the matching cache to load.

**Load Tissue Simulation** - Load the cache directly from the tissue simulation.

**Load Skin** - Load the cache for the skin.

A debugging technique you may need to use is cashing the tissue simulation and skin simulation for comparison.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.procedural-anatomy.com/nodes/simulation-nodes-1.0/anatomy-rig-skin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.