> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/model-entities/toc161394027/toc161394031.md).

# Beams vs. Trusses

How members behave as beam or truss elements depending on the chosen 2D or 3D model type.

By default, a member or frame element is a beam. However, if you choose the model type to be either “2D Truss” or “3D Truss”, then the frame element becomes a truss element. The program assigns full moment releases automatically to the ends of all members and suppresses all three rotational DOFs Dox, Doy, Doz for each and every node. For the model type “2D Truss”, the program also suppresses translational DOF Dz. Generally speaking, if a model contains only 2D or 3D truss elements, you should choose the model type as “2D Truss” or “3D Truss”. If a model contains both trusses and beams, you should choose the model type“2D Frame” or “3D Frame & Shell”, and assign appropriate moment releases to individual beams. It may also be necessary to assign appropriate restraints to nodes to ensure stability of the model. You may choose the appropriate model type by running the command Analysis > Analysis Options.


---

# 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://enercalc.com/docs/e3d-user-manual/model-entities/toc161394027/toc161394031.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.
