swift can be run distributed. That means the core (see swift core) and the GUI (swift front end) are split up. A normal scenario would be to run the core on the same machine where the flight simulator (e.g. XPlane) is started, and the UI runs on a second (remote) computer. However, you can also run core and (distributed) UI on the same machine.
As you can see in the launcher you have 3 options:
Standalone
: This means swiftguistd is running standalone and includes
swift core. No other application needs to be started. Don't start
swiftcore as extra process in that case.
GUI and Core - Audio on GUI side
: Use this configuration, if you want
to run gui and core in separate applications (possibly also on two
different machines in the network). All Audio (inkluding VATSIM voice)
will stay within the GUI process.
GUI and Core - Audio on Core side
: Use this configuration, if you want
to run gui and core in separate applications (possibly also on two
different machines in the network). All Audio (inkluding VATSIM voice)
will stay within the core process.
As an alternative, one can use linkcommand line arguments to setup shortcuts to launch GUI and core more quickly. swift launcher does the same (calling GUI and core process with specific arguments).
As an alternative to running core on the simulator machine, one can also setup a connection to a simulator in local network.
In order to create the model set in those scenarios you need remote access (shared drive etc.) to the model directory.
swift using a remote SimConnect configuration: See here. This allows to connect a remote FSX/P3D from a standalone swift GUI.
So there are two ways to setup a distributed scenario
SimConnect
connection.SimConnect
to computer 2. No core!You can also use WideFS
for remote connection, and run swift as
standalone GUI. Same as with SimConnect
. Also the
DirectPlay
connection needs to be setup for remote access.