How do I set up and join multiplayer flights in FSX?

Yes. Microsoft Flight Simulator X (FSX) and FSX: Steam Edition still support multiplayer, but the connection method depends on the edition. Use Steam sessions for Steam Edition, LAN for computers on the same network, or direct IP for boxed FSX over the internet. The boxed edition’s original GameSpy browser no longer works.

Can you still play FSX online multiplayer?

Yes, FSX multiplayer still works when everyone uses a compatible edition and the correct connection method. GameSpy’s closure removed the boxed edition’s public session browser; it did not remove LAN or direct-IP multiplayer from FSX.

Our explanation of which FSX multiplayer modes work online, over a LAN or without public internet covers these differences in more detail. If the group means organised online flying rather than a private lobby, use the separate FSX setup for VATSIM, vPilot and live ATC.

Do you need to be online to play FSX multiplayer?

No, the public internet is not required for an FSX LAN session between computers on the same local network. An internet connection is required for Steam internet sessions and remote direct-IP connections, while ordinary single-player FSX does not depend on multiplayer at all.

LAN is sometimes described as “offline multiplayer”, but the computers are still networked. FSX has no split-screen mode: every pilot needs a separate computer and a running installation of the simulator. Steam Edition must also be able to launch through the Steam client, even when its local-network mode is used.

What should I set up before joining an FSX flight?

Matching the host’s edition, build and session details prevents most failed connections and missing-aircraft problems.

1. Confirm the FSX edition and connection type. Ask whether the host is using FSX: Steam Edition, boxed FSX over LAN or boxed FSX through direct IP. Obtain the session name, password and public IP address where applicable.
2. Match the expected update level. Boxed participants should use the Service Pack or Acceleration configuration requested by the host. Steam users should allow Steam to finish updating FSX before joining.
3. Set a recognisable multiplayer identity. Enter the callsign or player name agreed by the group. Test the correct microphone and push-to-talk assignment before launching the session if built-in voice will be used.
4. Allow the simulator through Windows Firewall. Permit fsx.exe and, for Steam Edition, the Steam client on the appropriate trusted network profile. Do not disable the firewall permanently.
5. Agree on aircraft, airport and parking positions. Give every pilot a different gate, stand or ramp position. Loading several aircraft onto one runway threshold can cause immediate collisions or overlapping models.
6. Prepare the route locally. FSX does not automatically send a host’s flight plan to every pilot. Each participant should load the same .PLN file or create the agreed route independently.

If you are creating the flight rather than joining it, follow our host-side FSX session, firewall and NAT setup. Router configuration is primarily the host’s responsibility; an ordinary joining pilot should not start forwarding ports without a specific reason.

How do I join multiplayer in FSX: Steam Edition?

Join an FSX: Steam Edition internet flight through the Steam session browser built into the simulator.

1. Put Steam in online mode and launch FSX: Steam Edition from the Steam client.
2. Open Multiplayer from the FSX opening screen and choose the Internet or Steam connection option.
3. Refresh the session list. Remove restrictive filters if they are hiding private, password-protected or full sessions.
4. Select the host’s session and enter its password when requested. A private session may require an invitation from the host.
5. Choose your role and aircraft. Pilot is the normal selection. Use an air traffic controller or shared-aircraft role only when the host has configured the session for it.
6. Select the agreed starting point. Use your assigned parking stand rather than the active runway, then join and allow the scenery and other aircraft to finish loading.

The host can restrict aircraft changes and impose weather, time or realism settings. A greyed-out option inside the lobby may therefore be an intentional session rule rather than an installation fault.

How do I join a boxed FSX multiplayer flight?

Use LAN discovery for a nearby boxed-FSX host or Connect Directly for a remote host, because the old GameSpy login and public lobby are defunct.

1. Open Multiplayer from the FSX opening screen and enter your player name.
2. Choose Local Network or LAN when the host is connected to the same router, then search for available sessions.
3. Choose Connect Directly for a remote boxed-FSX host and enter the public IP address supplied by that host.
4. Select the session, provide its password and choose the agreed aircraft, role and starting position.
5. Enter the flight and remain at your assigned stand until the other participants have loaded.

A mistake we see constantly is trying to repair a GameSpy username or password. No account change will restore that retired service. For remote boxed-FSX sessions, the host must instead have a reachable public address and suitable router and firewall configuration.

Can Steam Edition join boxed FSX sessions?

Steam Edition cannot use its Steam internet browser to discover or join a boxed FSX GameSpy lobby. Steam matchmaking and the former GameSpy system are separate, and the latter no longer operates.

Mixed-edition connections may work through LAN or direct connection when the installed builds and session configuration are compatible, but they are less dependable than a group using one edition and update level. Do not plan a flight around mixed editions until the host has verified that exact setup.

Do all players need the same aircraft and scenery?

No, identical add-ons are not always required to connect, but FSX does not transfer aircraft, liveries, scenery or flight plans between participants.

• Aircraft: A pilot who lacks another player’s add-on model may see a stock substitute, the wrong livery or no useful representation of that aircraft. Stock FSX aircraft are the safest choice for an initial connection test.
• Scenery: Every computer renders its own airport. Different scenery packages can place pilots on mismatched taxiways, inside buildings or beside a runway that has moved.
• Flight plans: Routes remain local to each installation. Sharing a session does not load the host’s route into everybody’s GPS or Flight Planner.
• Weather and time: The host can impose these conditions, depending on the session settings, but participants should still confirm the planned departure time and weather.
• ATC and AI traffic: Native multiplayer does not turn several installations into one completely synchronised simulation. Locally generated AI aircraft and built-in ATC can differ between computers.

Two people who want to crew one aeroplane need an aircraft-sharing session rather than two ordinary pilot slots. Our shared-cockpit setup and joining procedure explains host permission, control handover and aircraft compatibility.

Why can’t I find or join the FSX multiplayer session?

Most missing FSX sessions are caused by the wrong edition or connection method, an offline Steam client, filtering, firewall rules, LAN isolation or an unreachable direct-IP host.

• No Steam sessions appear: Confirm that both host and joiner are using FSX: Steam Edition, Steam is online and the host has actually started the session. Refresh the browser, clear filters and check whether the lobby is private or full.
• The GameSpy login fails: Stop troubleshooting the credentials. Boxed FSX must use LAN or direct IP because GameSpy is no longer available.
• A LAN session is invisible: Put both computers on the same local network and trusted Windows network profile. Guest Wi-Fi, wireless client isolation, VPN adapters and firewall rules can block discovery even though both machines have internet access.
• Direct connection times out: Recheck the host’s public IP address; a private address beginning with ranges such as 192.168. cannot be used by a remote player. The host may need router changes, and carrier-grade NAT can make inbound hosting impossible without a different arrangement.
• You join but cannot see the group: Verify the airport, runway or parking stand and session name. Missing add-on aircraft may also be displayed as substitute models.
• FSX disconnects during loading: Test with a stock aircraft and a default airport. Complex add-ons, incompatible builds and long scenery-loading pauses are easier to identify after a basic session works.
• Voice is silent: Select the intended Windows recording device before launching FSX, verify the push-to-talk control and confirm that voice is enabled by the session host.

The quickest isolation test is a two-player session using the same FSX edition, stock aircraft and a default airport. If that works, restore add-on aircraft, scenery, voice and other session options one at a time until the conflicting element becomes clear.