From eda04c6b6cbf02ac28bdc18c0d9c3540723b3874 Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Tue, 1 Dec 2020 16:23:09 +0100 Subject: [PATCH] Fix incorrect `Curve3D.interpolate_baked()` description The offset is in 3D units, not pixels. This closes https://github.com/godotengine/godot-docs/issues/4339. (cherry picked from commit 5a9600cd24881c3b5357e484fb06b36f4a1e244d) --- doc/classes/Curve3D.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/classes/Curve3D.xml b/doc/classes/Curve3D.xml index 1211de3edd9..e1fa066eb58 100644 --- a/doc/classes/Curve3D.xml +++ b/doc/classes/Curve3D.xml @@ -145,7 +145,7 @@ - Returns a point within the curve at position [code]offset[/code], where [code]offset[/code] is measured as a pixel distance along the curve. + Returns a point within the curve at position [code]offset[/code], where [code]offset[/code] is measured as a distance in 3D units along the curve. To do that, it finds the two cached points where the [code]offset[/code] lies between, then interpolates the values. This interpolation is cubic if [code]cubic[/code] is set to [code]true[/code], or linear if set to [code]false[/code]. Cubic interpolation tends to follow the curves better, but linear is faster (and often, precise enough).