Fly to a Local Position

14 September 2015

Release 9.11 - added.

The flyto command makes Corrade fly towards a position in a given time duration getting as close to the vicinity of the position as possible with a specified affinity and finally turning flight mode on or off depending on whether fly is set to True, respectively False.

Command Required Parameters Required Corrade Permissions Example

flyto

group, password, position

movement

llInstantMessage(CORRADE,
    wasKeyValueEncode(
        [
            "command", "flyto",
            "group", wasURLEscape(GROUP),
            "password", wasURLEscape(PASSWORD),
            // fly to 1m above this object
            "position", llGetPos() + <0,0,1>,
            // accept a precision of 2 meters from the target
            "vicinity", 2,
            // upon reaching the object, turn flight off
            "fly", "False",
            // give Corrade 10 seconds to arrive at this object
            "duration", 10000,
            "callback", wasURLEscape(URL)
        ]
    )
);

Optional Parameter	Possible Value	Description
`duration`	Time in milliseconds.	Allow `duration` for Corrade to reach `position` - otherwise, send an error to the callback indicating that Corrade has not properly reached its destination.
`vicinity`	A range in meters (default `2`).	If Corrade arrives in the `vicinity` of the `position`, consider that Corrade has arrived at the destination.
`affinity`	An integer representing the affinity of the movement (default `2`).	How precise should the movements be?
`fly`	`True` (default)	When Corrade has reached the destination, keep flight mode on.
`fly`	`False`	When Corrade has reached the destination, turn flight mode off (useful, for climbing platforms).

Notes

Note that, compared to autopilot flyto, is a blocking command that will return a success status via the callback when and if Corrade has reached the destination. The distinction is that compared to autopilot you should always install a callback and wait for confirmation before sending another flyto command. If you do not wait for the callback, then Corrade will still be moving, such that sending a follow-up flyto command will queue the command until the antecedent flyto has completed and may lead to your workers being exceeded.
For a mathematical explanation for the duration, affinity and vicinity parameter please see the walkto page.