> 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/interface/toc175916526/toc175916652/generate-loads2/toc161394382.md).

# Moving Loads

How to generate moving point loads applied along specified members with automatic load cases and combinations.

Create > Generate Loads > Moving Loads prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-b342a460f44534fabf37141c5b5956fc011705a4%2FFASTFR~1_img133.png?alt=media)

It allows you to generate moving loads applied to specified members in the model. You must select a load case that contains moving loads. Only point loads on the specified members in the load case will be moved. These moving loads are assigned to their own load cases. The program automatically generates additional load cases and load combinations based on the moving step size.

If the Bi-Directional option is deselected, generation steps will take place in the positive global axis direction.

If the Bi-Directional option is selected, generation steps will take place in the positive AND negative global axis direction.

It should be pointed out that one moving load case cannot be used in more than one load combination prior to moving load generation.


---

# 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/interface/toc175916526/toc175916652/generate-loads2/toc161394382.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.
