> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-construction/depence-scene-graph-and-grouping.md).

# Scene Graph & Grouping

All 3D objects within the project are stored in a hierarchic tree structure called Scene Graph. That means that each object inherits the position, rotation, and scale values from its parent object. All child objects will be always relative to their parent. Therefore, Dynamic objects like Motors also can manipulate their child's relative positions.

## **Terminology**

### *Object-Space*

A position or rotation in object space means that it might be relative to their parents.

### *World-Space*

This is the absolute position or rotation in world coordinates.\
![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/uIRbwSuzTHUhJfSqUWJA/37519403.jpg)

## **3D Hierarchy**

### Object hierarchy position

The hierarchy position of an object can be changed by dragging an object within the 3D Hierarchy window.

By default, the object's World-Space position won’t be changed, because it will calculate a new relative position depending on the new parent Object.

{% hint style="info" %}
By holding the **ALT-Key** while dropping the object, it will keep the original relative position *(Object-Space position)*
{% endhint %}

More information about the position is explained within the [Transformation editor tools](/depence-construction/depence-editor-tools/transformation.md).


---

# 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.depence.com/depence-construction/depence-scene-graph-and-grouping.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.