Godot Engine – Multi-platform 2D and 3D game engine https://godotengine.org https://git.neuromancer.sk/godot.git/atom/core/math/matrix3.h?h=3.0-stable 2018-01-02T18:02:19Z 2018-01-02T18:02:19Z Juan Linietsky 2018-01-02T18:02:19Z urn:sha1:14772d22136ac87e2bbf2b94639f79242330ae0a Restore the behavior of Spatial rotations recently changed in c1153f5. 2018-01-01T13:40:47Z Rémi Verschelde 2018-01-01T13:40:08Z urn:sha1:b50a9114b105dafafdda8248a38653bca314a6f3 Happy new year to the wonderful Godot community! 2017-12-27T21:40:49Z tagcup 2017-12-27T00:15:20Z urn:sha1:e9896b17a9804ba6392dab0bd6c484f4d2e294c1 That change was borne out of a confusion regarding the meaning of "local" in #14569. Affine transformations in Spatial simply correspond to affine operations of its Transform. Such operations take place in a coordinate system that is defined by the parent Spatial. When there is no parent, they correspond to operations in the global coordinate system. This coordinate system, which is relative to the parent, has been referred to as the local coordinate system in the docs so far, but this sloppy language has apparently confused some users, making them think that the local coordinate system refers to the one whose axes are "painted" on the Spatial node itself. To avoid such conceptual conflations and misunderstandings in the future, the parent-relative local system is now referred to as "parent-local", and the object-relative local system is called "object-local" in the docs. This commit adds the functionality "requested" in #14569, not by changing how rotate/scale/translate works, but by adding new rotate_object_local, scale_object_local and translate_object_local functions. Also, for completeness, there is now global_scale. This commit also updates another part of the docs regarding the rotation property of Spatial, which also leads to confusion among some users. 2017-12-26T15:45:56Z Juan Linietsky 2017-12-26T15:44:58Z urn:sha1:c1153f5041f896536957b851329b5adaa1de6dc4 2017-10-11T20:56:47Z Ferenc Arn 2017-10-10T00:51:45Z urn:sha1:8861cc40fa79acd131875a556a8cf528384858ee 2017-09-04T10:49:42Z Juan Linietsky 2017-09-04T10:48:14Z urn:sha1:6d233c651b21ecaef78fbb20d0365a22919b72b1 -Fixed get_scale functions (and added set_scale) to make it more coherent when decomposing and composing (fixes bugs in transform interpolation) 2017-08-30T13:37:18Z Ferenc Arn 2017-08-25T19:45:21Z urn:sha1:5ad8d310f2a62a78a7d68bc169089b0f450dfe89 This new decomposition splits the basis into a rotation-reflection matrix and a positive scaling matrix, which is required for physics calculations. 2017-08-30T01:47:59Z Ferenc Arn 2017-08-30T01:47:59Z urn:sha1:a0bbf5c9afd0822d5f392c91fff37ecd4315647a Those functions were added in #8277 but they did more harm than good. They're subtle, don't do what people think and requires users to understand the non-uniqueness of polar decomposition. They ended up confusing people. Until we store additional information enough to make a unique polar decomposition, these functions shouldn't be a part of Basis. 2017-08-27T12:16:55Z Rémi Verschelde 2017-08-27T12:16:55Z urn:sha1:bd282ff43f23fe845f29a3e25c8efc01bd65ffb0 2017-08-09T13:05:37Z Ferenc Arn 2017-08-09T02:55:52Z urn:sha1:53c23b02226968d27e6caadcb801343697ac4fe9 As discussed in issues #1479 and #9782, choosing the up axis (which is Y in Godot) as the axis of the last (or first) rotation is helpful in practical use cases. This also aligns Godot's convention with Unity, helping with a smoother transition for people who are used to working with Unity (issue #9905). Internally, both XYZ and YXZ functions are kept, for potential future applications.