> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark/stage-model-viewer/making-models/making-a-hoist.md).

# Modeling A Hoist

By adjusting the size and rotation of the winch we can also make it look like a hoist.

As you saw with a lift, the winch-style model can be used to represent various machines other than ordinary deck winches. A hoist is set up similar to a lift, but it often has smaller dimensions, and resides above the deck, instead of below.

### Parameters To Set

* **Axis Type:** Hoist
* **Width:** 1.5ft
* **Length:** 5ft
* **Height:** 1.5ft
* **Rotation X:** 90 Degrees
* **Rotation Y:** 90 Degrees
* **Distance from Center:** 0ft
* **Distance from Plaster:** 1.5ft

### Instructions

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-b25d43135b859d1028cf502ef42f62b9b62efa7b%2FSM_CYSW_Hoist.gif?alt=media)

1. Select the motor you wish to adjust.
2. Select **winch** in the **Scenery Type** window.
3. Select **Hoist** in the **Axis Type** dropdown menu.
4. Adjust **Width, Length, and Height**.
   1. The **Width and Height** in this case are the plan dimensions of the unit.
   2. The **LENGTH** is the **DEPTH** of the unit.
5. Adjust **Rotation X** and **Rotation Y** so that the unit travels vertically.
6. Adjust **Distance** and **Elevation** to reflect actual location on the stage.
   1. In this example, we have the unit coming all the way to the ground. If you have a minimum height **above** **the deck**, use that height for **Elevation from Stage.**
7. Set [**Max Forward Position Soft Limit**](/docs/spikemark/position-scale/limits/setting-soft-limits.md) for actual travel distance.


---

# 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.creativeconners.com/docs/spikemark/stage-model-viewer/making-models/making-a-hoist.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.