GeoNavigator.png

What it is. GeoNavigator builds camera flights across the map. You collect a list of places — a row per destination — and it generates the animation between them on a director. A three-stop tour becomes three rows plus a button press, rather than a hand-keyframed camera move that has to be redone every time the running order changes.

Its own description puts it as "geo camera navigator with payload row editing, optional camera row apply, and director keyframe animation generation." In practice the workflow is: fly the camera somewhere you like, capture it as a row, repeat, then generate the animation.

There is a companion ControlGeoNavigator that exposes the flight to Trio or Pilot, so an operator can pick destinations without opening the scene.

See chapter Working with Maps for detailed information

Flight settings

Setting

What it is for

Default Motion

The shape of the movement between two places. Linear moves at a constant rate. Sine eases in and out, which reads better on air for short hops. Van Wijk is the one to reach for on long flights — it automatically pulls back and pushes in again so the journey stays legible instead of skimming the ground at high speed. Great Circle follows the true shortest path over the globe, which is what you want when the flight itself is the story, like a route between two cities.

Default Duration

How long a flight takes, in the units of your director. Used when timing is authored rather than computed.

Timing Mode

Authored uses the duration you set, so every hop takes the same time whether it crosses a city or an ocean. Auto derives the duration from the distance, so long flights get proportionally longer. Auto usually feels more natural; Authored is what you want when the flight has to fit a fixed slot.

Default Zoom Lift

How far the camera pulls back at the midpoint of a flight before descending again. A little lift makes a hop feel like travel rather than a slide; too much makes short hops feel melodramatic.

Default Flight Direction

Which way round the globe. Shortest picks the shorter of the two, and is right nearly always. East and West force the direction — the reason they exist is flights near the date line, where the shortest path may not be the one that tells the story.

Director

Which director the generated animation is written to.

Hop Name Prefix

The naming used for the generated hops, so what lands in the director is identifiable later rather than a row of anonymous keys.

Progress

Where you are along the flight, from start to end. This is the value the director animates — and the one to scrub when checking what the middle of a flight actually looks like.

Prefetch Step (frames)

How often along the flight to fetch map tiles ahead of the camera. This is what stops a flight arriving somewhere the map hasn't loaded yet. Denser stepping costs more memory and bandwidth.

Target Row

Which row in the list the actions below apply to.

Search Location

A place to look up and fly to, rather than entering coordinates by hand.

Payload

The list of destinations itself — the flight plan. Normally built with the buttons below rather than edited directly.

Status

Feedback from the plugin. Worth a glance when a flight isn't behaving.

Actions

Button

What it does

Add Row from Camera

Captures where the camera is now as a new destination. The main way a flight gets built: fly, capture, repeat.

Replace Row from Camera

Overwrites the target row with the current camera. How you adjust one stop without rebuilding the flight.

Activate Row

Jumps the camera to a row, to check a stop looks right.

Clear Rows

Empties the flight plan.

Apply Search Location

Takes the place from Search Location and applies it.

Update Animation

Generates the director keyframes from the current rows and settings. This is the one to remember — changing rows or settings does not rewrite the animation on its own.

Auto Jump

Moves the camera to a row automatically as you work.

Prefetch Hops / Prefetch Animation

Pre-loads map tiles along the destinations or along the generated flight, so the first playback is not also the first tile fetch. Worth running before anything goes to air.

In practice

Build the flight first — capture your stops with the camera and check each with Activate Row — then set motion, timing and lift, then press Update Animation. That last step is the one people forget: the rows and the animation are separate things, and the director keeps whatever was generated last until you regenerate it.

Prefetch before air. A flight that looks perfect on the second run and ragged on the first is almost always tiles arriving late, not the animation.