> For the complete documentation index, see [llms.txt](https://gilmour.online/compsci/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gilmour.online/compsci/archives/vanek-archives/archives-art-i/lesson-10-layout-the-base-metaball-mesh..md).

# Lesson 11: Layout the base metaball mesh.

As we did for the animals, you will be laying out the **base mesh in Blender** using metaballs and primitive shapes (boxes, cylinders, etc). Make sure you are using a separate base mesh for EACH object, rather than a single base mesh for everything.

Please watch the videos below for some advanced use of metaballs before proceeding.

Take two classes to work on this. It is an important step and should not be rushed!

{% embed url="<https://youtu.be/otEyqhRmfyc>" %}

{% embed url="<https://youtu.be/N1O64bdHsLo>" %}


---

# 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://gilmour.online/compsci/archives/vanek-archives/archives-art-i/lesson-10-layout-the-base-metaball-mesh..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.