> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-construction/depence-add-fixtures-and-objects/depence-fixture-hang-tool.md).
# Fixture Hang Tool
The Fixture Hang tool allows you to add multiple fixture types directly on truss pipes or splines within a single action.
*Note: Fixture Hang Tool only works with native Depence Trusses &* [*Splines*](/depence-construction/depence-splines.md)*.*
1. Select pipes or splines with your left mouse button (hold **CTRL** for multi-selection).
1. Drop your fixtures from the library into the Hang Tool.
## **Hang Tool Settings:**
| Count | Total Amount of fixtures (or per element). |
| -------------- | ------------------------------------------------------------------------ |
| Spline From/To | Limits the arrangement (if not per element). |
| Element Limit | Limits the arrangement per element (useful to keep fixtures on trusses). |
| Rotation | Rotation offset in addition to current spline rotation. |
To create and auto-patch the fixtures click on **Create**. If you hang fixtures on trusses, the fixtures will automatically be grouped with the truss group.
---
# 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://help.depence.com/depence-construction/depence-add-fixtures-and-objects/depence-fixture-hang-tool.md?ask=&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.
