> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/wood-framing/common/wood-metal-framing/framing-configuration/brace.md).
# Brace
### Brace Type
**Use Main Types** – brace family and type will be taken from **Common Settings** tab.
**Type –** select the family and type that will be used for the brace. Default families are predefined. **Width (b)** – shows b size of selected type.
**Depth (h,d) –** shows h or d size of selected type.
**Define Depth (h,d) by Layer Thickness** – Wall+/Floor+/Roof+ will automatically create new type for selected family with new depth equal to selected wall/floor layer thickness.
### Rotate 90° and 180°
**Rotate 90°** – if ticked, then bracing rotates by 90 degrees.
**Rotate 180°** – if ticked, then bracing rotates by 180 degrees. Rotation depends on how the profile in the family is created.
*Example with wood wall frame:*
*Example with metal wall frame:*
### Extend Ends
**Extend Ends –** extends brace ends if it connects other plates/rim joists or studs/joists.
*Example: **Extend Ends** is switched ON for the left brace and switched OFF for the right brace:*
*Example: when **Extend Ends** is switched ON:*
*Example: when **Extend Ends** is switched OFF:*
### Minimum/Maximum Angle
**Minimum Angle** and **Maximum Angle** – define angle limits for adding bracing.
### Cut Studs/Joists and Cut Bridging/Nogging
**Cut Studs/Joists** – select bracing and stud/joist connection cutting type.
**Cut Bridging/Nogging** – select bracing and bridging or nogging connection cutting type.
*Example with wood wall frame:*
*Example with metal wall frame:*
*Example with wood floor: when **Cut Joists** is selected:*
*Example with wood floor: when **Cut Bridging/Nogging/Blocking** is selected:*
### Brace Connection Offset from Stud/Joist or Plate/Bridging/Nogging
**Brace Connection Offset from Stud/Joist** – enter a distance between bracing and stud/joist.
**Brace Connection Offset from Plate/Bridging/Nogging** – enter a distance between bracing and plate, bridging, or nogging.
*Example, **Brace Connection Offset from Stud/Joist** = 3":*
### Frame Side
**Frame Side** – select whether a brace should be applied in the center, external or internal side of the frame.
*Example: when **Frame Side** = **Center**:*
*Example: when **Frame Side** = **External**:*
### Build in Place
**Build in Place** – writes Yes/No information into the brace instance parameter if it is build-in-place or is prefabricated with the whole wall frame. Later this parameter can be used in schedules or view filters.
*Example with wood wall:*
*Example with wood floor:*
---
# 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.besmart.software/3d-modeling-and-design/wood-framing/common/wood-metal-framing/framing-configuration/brace.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.
