Guide

Flyby, slingshot or capture

Ask Asterion to design a flyby, a slingshot or a capture around a star system, and see what each one takes. Needs a free account.

You will work in the workspace at /app. Open it in another tab and follow along.

Every step was followed by hand in the workspace on 2026-10-21, version 1.0.0-beta.817.

  1. Stop 1 of 3

    Ask for a flyby

    Free account needed. A free account gets 25 questions a day.

    1. Start with a star system in the scene, such as the one from Have Asterion build a system.
    2. In the Asterion tab, type: Design a flyby of an interstellar comet through this system. Then choose Send.

    What you should see. An Interstellar Comet appears in the Scene list outside the system, and the reply ends in an Interstellar visitor card marked Added to scene. The reply describes the visitor's path past the star and offers to change how close it passes.

    The workspace after a flyby request. The Scene list shows Red Dwarf System with Planet 1 and Planet 2, and a separate Interstellar Comet entry. In the Asterion tab, the end of the reply asks whether to adjust the closest-approach distance, move the planets or save the experiment. Below it, an Interstellar visitor card reads Interstellar Comet, Comet, 20.5 kilometres per second, marked Added to scene.
  2. Stop 2 of 3

    Ask for a slingshot

    Free account needed

    1. With the same scene, type: Design a gravitational slingshot for the visitor around one of the planets. Then choose Send.
    2. Read the end of the reply, then stop before answering it.

    What you should see. A second visitor, called Slingshot Comet or Slingshot Visitor, joins the Scene list. Asterion explains that a slingshot needs a massive planet, says rocky planets give only a small effect, and offers to add a gas giant. Do not accept that offer in a scene that already holds the system. The workspace then asks whether to add a system whose name is already in use, and choosing Add Anyway adds a second copy of the whole system with the giant in the copy, leaving the first copy as it was. The next stop builds a gas giant into a clean scene instead.

    The workspace after a slingshot request. The Scene list shows Red Dwarf System with its two planets, then Interstellar Comet and Slingshot Comet as separate entries. In the Asterion tab, the end of the reply asks whether to add the gas giant and set up the full slingshot, or to run the many-body simulation first. Below it, an Interstellar visitor card reads Slingshot Comet, Comet, 20.3 kilometres per second, marked Added to scene.
  3. Stop 3 of 3

    Ask for a capture

    Free account needed

    1. Choose File, then New Scene. A capture builds its own star, gas giant and visitor, so it starts from an empty scene.
    2. In the Asterion tab, type: Design a capture of an interstellar visitor by a gas giant. Then choose Send.
    3. Asterion first asks three questions: how fast the visitor arrives, how close it passes the star, and how massive the gas giant is. Type: Use the defaults. Then choose Send.

    What you should see. The Scene list shows a Capture Experiment system with a gas giant, Capture Giant, inside it, and a separate Interstellar Visitor. Asterion's reply says what it placed and that a capture is not guaranteed. It tells you to run the scene under full gravity, as in Your first star system, because the encounter only works out that way. Whether the visitor ends up held by the giant is for you to judge from its path.

    The Scene list and 3D view after a capture request. The list shows a system named Capture Experiment, with a gas giant called Capture Giant under it, and a separate entry called Interstellar Visitor. A long orbit line sweeps across the top of the 3D view.

At the end you have

A visitor on a flyby, a second on a slingshot, and a gas giant set up to try to capture a visitor, and a clear idea of what the workspace can and cannot yet tell you about whether a capture happens.

What capture does today

Capture works in the integration: a moon or other body can pass from one object into orbit around another.

The workspace does not yet detect a capture for you dependably. On the roadmap, this is planned: Dependable detection of capture events, and verified behavior across several interacting systems in one scene.

More guides are being planned. The roadmap says what is here and what is on the way.