Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

Export in CSV format

<div lang="en" dir="ltr" class="mw-content-ltr">
Every [[slot]] in a [[world]] has an associated set of position, rotation and scale values, even if there is no visual component associated with it. Since space is three dimensional in Resonite, position is encoded as a [[Type:float3|float3]] [[:Category:Type|type]], which is a [https://en.wikipedia.org/wiki/Euclidean_vector 3D vector] of coordinates along X, Y, and Z axes. Rotations can also be expressed as angular displacements about these three axes and this is how it is displayed in the slot [[Scene Inspector|inspector panel]]. However, rotations are internally managed as a [[Type:floatQ|floatQ]] type, or a [https://en.wikipedia.org/wiki/Quaternion quaternion]. Scale works similarly to position and is encoded as a float3.
</div>

== <span lang="en" dir="ltr" class="mw-content-ltr">Directions</span> ==

<div lang="en" dir="ltr" class="mw-content-ltr">
[[File:Resonite Inspector Axis Directions.png|thumb|498x498px|The [[scene inspector]] shows a reference of directions in Resonite.]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In Resonite, the positive X axis direction is defined as 'right', negative X direction is 'left'. The positive Y axis direction is defined as 'up', negative Y is 'down'. The the positive Z axis direction is defined as 'forward', negative Z direction is 'back. The positive X, Y and Z axes correspond to the red, green and blue arrows on the [[Gizmo|gizmo]] tool. Distances are scaled such that a unit of 1 in any axis direction corresponds to 1 meter. Angles are displayed in the slot inspector panel in units of degrees.
</div>

== <span lang="en" dir="ltr" class="mw-content-ltr">Coordinate spaces</span> ==

<span lang="en" dir="ltr" class="mw-content-ltr">In Resonite, a '''coordinate space''' refers to the orientation of the X, Y, and Z axes for a given transform. There are two different kinds of coordinate spaces that you work with in Resonite:</span>

* <span lang="en" dir="ltr" class="mw-content-ltr">The '''global''' coordinate space is the base coordinate space and is measured relative to the world [[Root|root]]. It can not be changed.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">A '''local''' coordinate space, which is measured relative to some slot in the slot hierarchy.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The <code>Position</code>, <code>Rotation</code>, and <code>Scale</code> fields on slots in the [[scene inspector]] are shown and managed in a local coordinate space to the slot's immediate parent.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The world's root slot is unique and always at the top of the world slot hierarchy. It has a fixed position at <code>[0; 0; 0]</code>, fixed identity rotation, and <code>[1; 1; 1]</code> scale. This means that, for a slot parented directly under the world root, global and local coordinate measures will be equivalent. This is also true if and only if all of a slot's parents have <code>[0; 0; 0]</code> position, <code>[0; 0; 0]</code> rotation, and <code>[1; 1; 1]</code> scale.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For example, if a slot, Slot_A, is parented under the world root and has global position <code>[1; 0; 0]</code> (i.e. 1 meter to the right of the world root) its local position, as shown in the inspector, will be <code>[1; 0; 0]</code>. If another slot, Slot_B, is parented under Slot_A and also has local position <code>[1; 0; 0]</code>, its global position is <code>[2; 0; 0]</code>. If Slot_A is now moved to <code>[1; 1; 0]</code> (i.e. translated 1 meter upwards), Slot_B will move with Slot_A and its local position remains <code>[1; 0; 0]</code>; its global position will now be <code>[2; 1; 0]</code>.
</div>

== <span lang="en" dir="ltr" class="mw-content-ltr">Transformations</span> ==

<div lang="en" dir="ltr" class="mw-content-ltr">
In principle one could calculate a slot's global position by summing its local position vector with those of all of its parents. However it is much easier to use the [[ProtoFlux:Global Transform|Global Transform]] ProtoFlux node for this purpose. The same goes for global rotation and scale, although those would require the element-wise product of parent local rotations or scales due to how those quantities are combined.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There are many ProtoFlux nodes which are particularly useful for moving, rotating and scaling slots in the [[:Category:ProtoFlux:Transform|Transform]] category of the ProtoFlux node browser. When applying a transformation (movement, rotation or scale) to a slot, such as via a Drive or a Tween, one usually wants the input value to be in the target slot's local coordinate space. Initially calculating transformations using global coordinates may be useful if the intended effect should not depend on the slot's current context. Conversely, typically one wants transformations to happen relative to the slot's current state which requires the use of local coordinates. There are a several nodes for converting positions, directions, rotations and scales between global and local coordinates. There are also ones for converting between the local coordinate spaces of two slots with different parents.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is possible to scale objects non-uniformly (i.e. having different X, Y and Z scale values), though this should be done with care as child slots inherit scaling from their parents. This can cause hard-to-debug issues where a visual component of a child slot displays strangely due to a non-uniformly scaled parent somewhere above in the hierarchy. The requirement for non-uniform scaling to achieve the desired look with primitive meshes (boxes, spheres, cones, quads etc.) can, and should, usually be avoided by instead changing the parameters of the respective mesh component.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In addition to ProtoFlux, slots can be made to move or transform in various ways using components under the [[:Category:Components:Transform|Transform]] component category (e.g. [[Component:Spinner|Spinner]], [[Component:Wiggler|Wiggler]], [[Component:Wobbler3D|Wobbler]] etc.).
</div>

== <span lang="en" dir="ltr" class="mw-content-ltr">Tools</span> ==

* <span lang="en" dir="ltr" class="mw-content-ltr">The [[Dev Tool]] is extremely useful since it gives access to the transform gizmos and slot inspector panels which enable setting coordinates precisely.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">The [[ProtoFlux Tool]] is required for interacting with coordinate values via ProtoFlux nodes.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">The [[Meter Tool]] can be useful for measuring distances in various ways.</span>

== <span lang="en" dir="ltr" class="mw-content-ltr">See also</span> ==

* [https://en.wikipedia.org/wiki/Three-dimensional_space <span lang="en" dir="ltr" class="mw-content-ltr">3D Space on Wikipedia</span>]
* [https://en.wikipedia.org/wiki/Euclidean_vector <span lang="en" dir="ltr" class="mw-content-ltr">3D Vectors on Wikipedia</span>]
* [https://en.wikipedia.org/wiki/Quaternion <span lang="en" dir="ltr" class="mw-content-ltr">Quaternions on Wikipedia</span>]