> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/commands-overview/annotations/align-hatching.md).

# Align hatching

## Command Description

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FW0h0yjYaVMG9RL2UPLjb%2Fimage.png?alt=media&amp;token=e429bc3d-e0b0-4fa9-bb92-d2210d7d5ee1" alt=""><figcaption></figcaption></figure>

This command can align the hatching of welded assemblies in the same direction. Users can select or enter the required hatching angle and scale.

Normally, welded assembly (subassembly inserted into the main assembly) hatches in the Inventor drawing section views are not aligned in the same direction as required by technical drawing standards. This tool helps designers to overcome that issue. Now it is not necessary to manually adjust the hatching of every part of the welded assembly to comply with standards.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FH1gQ2JhbVFgzcvk9xXnV%2F02_align_hatches.png?alt=media&amp;token=56a75582-1957-4678-b4d6-2cc5f47c8fd3" alt="" width="563"><figcaption><p>Default hatching (left) and aligned hatching (right) of the welded assembly</p></figcaption></figure>

### What weldment occurrences does the command use?

Weldment occurrence is the highest weldment assembly (if any) in the top assembly structure. The following image depicts the weldment occurrences that can be used by the command. Other weldment occurrences and "general" file types are ignored.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FM2PrAsm033C6BAQeHX5G%2F03_weldment_occurrences.png?alt=media&amp;token=21515188-cdce-4df4-9436-2bbf173f815e" alt=""><figcaption><p>Weldment occurrences used by the command</p></figcaption></figure>

## Command Location

* Drawing environment

## Command Settings

This command has no settings.

## Workflow Overview

1. Start the command.
2. Select the drawing view containing the weldment assembly.
3. In the dialog, for each weldment occurrence, set the hatching angle and scale.
4. Click OK to apply changes.

## Example of using the Align hatching command

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FbOsIihR2u710G9oEBWBi%2FAlign%20hatching.gif?alt=media&amp;token=6c51ed3c-3615-48eb-ac55-01be8d511d0d" alt=""><figcaption><p>Using the Align hatching command</p></figcaption></figure>


---

# 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.besmart.software/t4i/commands-overview/annotations/align-hatching.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.