> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2022.1/toolbox/incari/object/set-rotation.md).

# Set Rotation

## Overview

![The Set Rotation Node.](/files/XsShLaBtQ88sNLLKZ3uT)

**Set Rotation** sets the value of a given **Object's** `Rotation` **Attribute**.

[**Scope**](/incari-studio/2022.1/toolbox/overview.md#scopes): **Scene**, **Function**, **Prefab**.

## Attributes

![The Set Rotation Node Attributes.](/files/9ryuS8AdQYH8cK5ImykN)

| Attribute  | Type         | Description                                                                                                       |
| ---------- | ------------ | ----------------------------------------------------------------------------------------------------------------- |
| `Object`   | **ObjectID** | The ID of the **Object**, whose `Rotation` you wish to set, if one is not provided in the `Object ID` **Socket**. |
| `Rotation` | **Vector3**  | The desired `Rotation` value of the **Object**, if one is not provided in the `Rotation` **Socket**.              |

## Inputs

| Input             | Type         | Description                                                                                                                                  |
| ----------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**    | A standard **Input Pulse**, to trigger the execution of the **Node**.                                                                        |
| `Object ID`       | **ObjectID** | The ID of the target **Object** whose `Rotation` value you wish to set.                                                                      |
| `Rotation`        | **Vector3**  | A 3-dimensional vector that contains the `Rotation` components measured in Euler angles along the X, Y, and Z axes of the target **Object**. |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [**Get Scale**](/incari-studio/2022.1/toolbox/incari/object/get-scale.md)
* [**Get Position**](/incari-studio/2022.1/toolbox/incari/object/get-position.md)
* [**Get Rotation**](/incari-studio/2022.1/toolbox/incari/object/get-position.md)

## External Links

* [*Rotation*](https://en.wikipedia.org/wiki/Euler_angles) on Wikipedia.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.incari.com/incari-studio/2022.1/toolbox/incari/object/set-rotation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.