> 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/math/rotation-matrix.md).

# Rotation Matrix

## Overview

![The Rotation Matrix Node.](/files/lTH2v7oBaqpi7ZZ8MeiW)

The **Rotation Matrix** **Node** receives three angles as inputs and generates a **Matrix4x4** that represents a *rotation* along the X, Y, and Z axes in the received angles.

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

## Attributes

![The Rotation Matrix Node Attributes.](/files/kxB64gfBLdnR1vfSRG1b)

### Inputs

| Attribute         | Type      | Description                                                                                                                                       |
| ----------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Default Angle X` | **Float** | The angle, in degrees, along the X axis in which the *rotation* will be performed, if no value is provided in the `Angle X in degree` **Socket**. |
| `Default Angle Y` | **Float** | The angle, in degrees, along the Y axis in which the *rotation* will be performed, if no value is provided in the `Angle Y in degree` **Socket**. |
| `Default Angle Z` | **Float** | The angle, in degrees, along the Z axis in which the *rotation* will be performed, if no value is provided in the `Angle Z in degree` **Socket**. |

## Inputs

| Input               | Type      | Description                                                                        |
| ------------------- | --------- | ---------------------------------------------------------------------------------- |
| *Pulse Input* (►)   | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**.              |
| `Angle X in degree` | **Float** | The angle, in degrees, along the X axis in which the *rotation* will be performed. |
| `Angle Y in degree` | **Float** | The angle, in degrees, along the Y axis in which the *rotation* will be performed. |
| `Angle Z in degree` | **Float** | The angle, in degrees, along the Z axis in which the *rotation* will be performed. |

## 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. |
| `Rotation Matrix`  | **Matrix4x4** | A **Matrix4x4** representing *rotations* along the X, Y, and Z axes in the given angles.                                               |

## External Links

* [*Rotation matrix*](https://en.wikipedia.org/wiki/Rotation_matrix) 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/math/rotation-matrix.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.