OK - “Zip Wire mode” may not be an official Litchi setting name … but it’s what I’ve seen it referred to, and now think of it myself, when only the route is defined.
Speed (zero), Tilt and Camera heading (both manual) are all controlled by you.
Ideal for this kind of scenario. You’d have to be clever to know exactly when the train would appear and how fast it would be moving to be able to start the mission and sit back and wait for everything to happen … when you’re 300m from the track, too.
I flew out to near the first waypoint, started the mission, flew “forwards” until just past the first waypoint and was “engaged” onto the path … then hovered and waited a few minutes for the (hourly) train.
This was my 2nd run of the mission I’d set up - and there was also an initial “dummy-run” … totally manual with the path displayed, so I could double check heights of trees, height of the track (I was located quite a bit lower than the track at take off), etc.
Whilst one can set height above the ground … not sure Google data
is accurate to the detail of “an embankment” to rely upon it without checking.
I think something (Litchi?) may have reset my reduced yaw and gimbal pitch sensitivity … I must check … but other than that I’m linking the great repeatability (albeit tweaked a little after the dummy-run.
The first run using the mission (running in reverse) was OK, but the track’s downhill in that direction and the train didn’t chuff enough! LOL!
Straight from the MP … just clipped start and end boring bits. (Yup - I left the LARGE boring bit in the middle! ) Not playing with editing on this … it’s purely Litchi (nerves) training.