Connection Settings controls how Flight Deck apps connects to X Plane over the network. Most of the time it just auto detects the simulator and you never have to touch anything. This page exists for the weird days.
Connection status
At the top you see the current status:
- X Plane Detected (green dot) means the app can see the simulator on the network.
- X Plane not detected (red dot) means nothing was found.
- Custom Connection means you enabled manual settings, so discovery info is not used for the connection details.
When X Plane is detected you may also see:
- Host: the computer name running X Plane
- IP and Port: the address and UDP port advertised by X Plane
- Local Port: the port your device is using to receive UDP data
Connect and Disconnect
- Connect starts the connection using either auto detection or your custom settings.
- Disconnect forces the link to stop.
Custom Connection
Enable
Turn Enable on only if you need to manually set the connection. When you switch it off, the app returns to auto detection and restarts the link.
X Plane UDP Address
The IP address of the computer running X Plane.
Use 0.0.0.0 only as a placeholder, a real connection needs the actual IP.
X Plane UDP Port
The UDP port X Plane is listening on.
For maximum compatibility, prefer the legacy port of X Plane.
Receiving Port
The UDP port on your device that receives packets from X Plane.
This matters more than most people expect. If the IP is correct but the Receiving Port is wrong, the app might still detect X Plane via its beacon, but commands may not work. A quick test is to try a simple command like pause or unpause from the app.
If another app is already using the same Receiving Port, change it to avoid conflicts.
Applying changes
When you edit the address or ports and submit, the app updates the interface settings and restarts the connection so the new values take effect.
Troubleshooting
If the app is not connected, a Still having issues? section appears with a link to the Troubleshooting guide.
That guide is the right place for the classic culprits: Wi Fi mismatch, firewall, VPN, router isolation, and multiple network adapters on the host Mac or PC.
