# Line

The Line is used to construct line in a Path System. The [MUs](/components-and-scripts/mu-movable-unit.md) are moved along the Line with the [Path Mover](/extensions/page-4/path-system/pathmover.md)

<figure><img src="/files/mtukGSFUf8MEd7dEmrrd" alt=""><figcaption></figcaption></figure>

### Path finding strategy <a href="#path-finding-strategy" id="path-finding-strategy"></a>

Please check page [Path Finding](/extensions/page-4/path-system/path-finding.md) for more information about path strategies and implementing your own strategies.

### Line properties

**Drive**\
For moving [MUs](/components-and-scripts/mu-movable-unit.md) always a [Drive](/components-and-scripts/motion/drive.md) is needed. The Drive can be on the [MU](/components-and-scripts/mu-movable-unit.md) itself (e.g. for modelling AGVs) or the [Drive](/components-and-scripts/motion/drive.md) can be on the Curve or Line itself (e.g. for Power\&Freee systems). If this field is kept empty, a [Drive](/components-and-scripts/motion/drive.md) on the [MU](/components-and-scripts/mu-movable-unit.md) is needed.

**Path Strategy**\
You can assign a component of type *PathStrategy* to the line. Each time a [PathMover](/extensions/page-4/path-system/pathmover.md) is leaving the Path the strategy can select a successor. Please check page [Path Finding](/extensions/page-4/path-system/path-finding.md) for more information about using custom strategies. If the PathStrategy is empty, automatically the first successor is selected.

**Length**\
The lengh of the Path in meters.

**Show Path On Simulation**\
Must be set to true if path should be visible during simulation.

**Thickness**\
The thickness of the path line.

**Materialpath**\
The material of the path.

**Direction Arrow**\
If true, the Direction arrow will be displayed.

**Size Direction Arrow**\
The size of the direction arrow.

<figure><img src="/files/A5pC3aue4yv61UDLSsAe" alt=""><figcaption></figcaption></figure>

#### Path events <a href="#path-events" id="path-events"></a>

A certain behavoir at the entrance or the exit of an path element can be defined within the section path events. Scripts which are connected there will be called during run time. An expample for such a strategies is within the demo scene *DemoPathsystem\_UsedCases/DemoAGVSystemWithStations*.

<figure><img src="/files/epx80AvDYaLKDfMz4hBX" alt=""><figcaption></figcaption></figure>

© 2025 realvirtual GmbH [https://realvirtual.io](https://realvirtual.io/) - All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including printing, saving, photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.realvirtual.io/extensions/page-4/path-system/line.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.