diff options
| author | Rémi Verschelde <remi@verschelde.fr> | 2022-04-30 13:25:04 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-30 13:25:04 +0200 |
| commit | f131ec336bd364b5b8b98b9084bdb3d082698420 (patch) | |
| tree | 819006f8057745ddbae69a323bef65b8a5f9096d /doc/classes/@GlobalScope.xml | |
| parent | e619e0e4d458c347e4130821fc823afc6e21ade2 (diff) | |
| parent | 492903a0b221ac50c5db0426d22db2457f946b58 (diff) | |
Merge pull request #60614 from timothyqiu/lerp-angle-doc
Diffstat (limited to 'doc/classes/@GlobalScope.xml')
| -rw-r--r-- | doc/classes/@GlobalScope.xml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/classes/@GlobalScope.xml b/doc/classes/@GlobalScope.xml index 0021b2f857..a40b851efc 100644 --- a/doc/classes/@GlobalScope.xml +++ b/doc/classes/@GlobalScope.xml @@ -457,6 +457,7 @@ rotation = lerp_angle(min_angle, max_angle, elapsed) elapsed += delta [/codeblock] + [b]Note:[/b] This method lerps through the shortest path between [code]from[/code] and [code]to[/code]. However, when these two angles are approximately [code]PI + k * TAU[/code] apart for any integer [code]k[/code], it's not obvious which way they lerp due to floating-point precision errors. For example, [code]lerp_angle(0, PI, weight)[/code] lerps counter-clockwise, while [code]lerp_angle(0, PI + 5 * TAU, weight)[/code] lerps clockwise. </description> </method> <method name="linear2db"> |