First test on the Automoton update! This rover and its beacon let the drone know where to mine (in front of its nose). Launch drone, it mines until full, drops it off at home, and returns to the rover.
Common pitfalls:
– Collision avoidance. Collision avoidance makes the drone wriggle weirdly and can lose sight of its objective happily floating off into the beyond never to be seen again, or disable whatever pathing block is controlling AI flight. I think it thinks “I can’t meet requirements” (avoidance or altitude) and simply gives up. It’s buggy.
– Precision mode. The main thing precision mode is good for is making sure actions aren’t triggering while following recorder waypoint paths. You’re better off without, as AI flight at a slow enough speed limit is precise enough.
– Buggy recorder pathing regardless of settings and easily disables itself for no reason. Check, double check, triple check… Check far too often, Reset far too often, until eventually you get lucky. Recorder paths are buggy but unfortunately necessary for relative waypoint pathing. Avoid using these if at all possible and redesign using basic task with GPS instead.
Required Workarounds:
– Sub Zero Altitudes. AI flight doesn’t support flying below sub zero altitudes and will get stuck above or below the zero barrier, unable to cross. An event controller checking grid speed is greater than or equals 3 and enabling/disabling thrusters is the way to go for a slow descend, and paired with thrust override for a slow ascend.
– Make sure power utilisation doesn’t hit 100% or things will start to turn off.
– Make sure thrust never hits a point where it struggles to lift the drone or pathing AI gets confused and disables itself.
source
