Can't see other aircraft on VATSIM in FSX? Check vPilot, SimConnect, nearby traffic, model matching and missing AI models in the right order.
If other VATSIM aircraft are invisible in FSX or FSX: Steam Edition, vPilot is usually not connected to the simulator, no pilot is within display range, or model matching has selected an unavailable aircraft. Verify SimConnect, nearby traffic, installed AI models and vPilot's messages; FSX's AI sliders do not create VATSIM traffic.
How do I make other VATSIM aircraft appear in FSX?
Work through the connection, range and model checks in that order; changing aircraft models cannot fix a failed SimConnect connection.
- Load a normal FSX flight. Wait until your aircraft is fully loaded at a stand before connecting vPilot. Use a standard free-flight session rather than FSX's native multiplayer mode.
- Confirm both connections. vPilot must be connected to VATSIM and communicating with the running simulator through SimConnect. These are separate connections: a successful network login does not prove that vPilot can inject traffic into FSX. If either one fails, follow our complete FSX and vPilot connection setup.
- Verify that a pilot is genuinely nearby. A controller, observer or pilot hundreds of miles away will not create an aircraft around your airport. Network maps can also cover a much larger area than the client draws.
- Read the vPilot messages. Messages naming an unavailable model, no suitable match or failed aircraft creation point to model matching or a broken FSX aircraft installation. A simulator-disconnection message points back to SimConnect.
- Check vPilot's display limits. A low drawing range removes distant aircraft, while a low maximum-aircraft setting shows only the closest pilots. Increase these enough for testing, but do not assume that maximum values are best for FSX performance.
- Confirm that models and rules are both installed. A rule set only tells vPilot which local aircraft to use; it does not contain the models themselves. The selected models must be compatible with FSX and available in one of its registered SimObjects paths.
- Restart after changing models. Close FSX and vPilot, relaunch the simulator, load the flight and reconnect. This forces FSX and the client to read newly installed or corrected aircraft configurations.
If vPilot runs on a second computer, its networked SimConnect configuration and the relevant firewall permissions must also be correct. Do not attempt to repair this by placing miscellaneous replacement DLL files into FSX; use the SimConnect components supplied with the simulator or client installation.
What does each visibility symptom mean?
The point at which traffic disappears usually identifies whether the fault is network range, SimConnect or model matching.
| Symptom | Likely cause | Next check |
|---|---|---|
| No nearby traffic is reported or displayed | No pilot is within range, vPilot is offline, or a client display limit is too restrictive | Confirm the network connection, location and drawing range |
| vPilot receives nearby aircraft but FSX shows none | SimConnect injection failure or no usable models | Check the simulator connection and vPilot messages |
| Only particular types or airlines are missing | A rule points to an absent or broken model | Check the model title named by vPilot |
| Aircraft appear with the wrong type or livery | vPilot has selected a generic fallback | Install or enable a suitable local match |
| A label appears without a visible aeroplane | FSX created the object but cannot render its model correctly | Inspect that aircraft's model and configuration files |
| Aircraft are underground, floating or displaced | The pilots use different airport scenery, elevations or parking layouts | Compare scenery rather than reinstalling model-matching rules |
Why can vPilot connect but show no aircraft?
A VATSIM connection only confirms that vPilot can exchange network data; FSX still needs a working SimConnect link and a usable local model for every displayed aeroplane.
VATSIM supplies details such as the callsign, aircraft type and position. vPilot applies its matching rules and asks FSX to draw an installed substitute. The other pilot does not transmit an aircraft model or livery file to you.
Models are normally under SimObjects\Airplanes or another SimObjects folder registered with FSX. Boxed FSX and FSX: Steam Edition use different installation roots. If both are installed, make sure the models were added to the edition that vPilot is connected to.
A mistake we see constantly is treating the aircraft folder name as the matching name. A vPilot rule normally refers to the title= value inside a valid [fltsim.x] section of aircraft.cfg. FSX then follows the section's model= entry to a model folder and its model.cfg file. Our explanation of how FSX reads fltsim entries and title values covers those relationships.
Use aircraft designed for AI traffic and compatible with FSX. A complex flyable add-on is not automatically suitable as an injected traffic model, and models built only for another simulator may fail to render. If older models disappear only when DirectX 10 Preview is enabled, temporarily disable Preview and restart FSX to test for a model-format problem.
Why are only some VATSIM aircraft missing or wrong?
If most nearby pilots are visible, the network and SimConnect links are working; the missing aircraft has a matching or rendering problem.
- Find the aircraft or model title named in vPilot's messages.
- Confirm that the rule refers to a model actually installed in an active FSX SimObjects path.
- Check that the corresponding
[fltsim.x]block has a valid and uniquetitle=value. - Verify that
model=leads to the expected model folder and that its configuration points to an existing model file. - Correct rules copied from another installation if they reference models you do not own.
- Keep a generic fallback for aircraft types or liveries absent from your model library.
A wrong livery is not the same failure as an invisible aircraft. It usually means vPilot found a renderable fallback but did not have an exact airline and type combination. If FSX selects the model but draws it invisibly or with major parts missing, use our checks for diagnosing aircraft that FSX loads invisibly or incompletely.
Do FSX traffic sliders affect VATSIM aircraft?
No. FSX's airline and general aviation traffic sliders control offline computer-generated AI, not the live pilots injected by vPilot.
Many VATSIM users set both offline traffic sliders to zero so computer-controlled aircraft do not occupy gates or become confused with network traffic. vPilot's own drawing range and maximum-aircraft settings still apply, so check those if nearby traffic appears but more distant aircraft do not.
FSX's built-in multiplayer is also separate from VATSIM. Joining a native FSX multiplayer session will not supply VATSIM traffic; vPilot injects it into a normal loaded flight through SimConnect. Aircraft labels only control identifying text and cannot repair a missing model.
Can I see ATC and every online pilot as aircraft?
No. Only nearby connected pilots within the client's display limits become aircraft in FSX; controllers and observers are not rendered as aeroplanes.
An online controller may appear in vPilot's controller information and be available by radio without producing a visible object at the airport. Pilots using another supported simulator can still appear because VATSIM is cross-platform, but FSX renders them with one of your locally installed models. See our explanation of how nearby pilots, visibility limits and online ATC differ if the network map and the traffic around you do not agree.
Why do visible aircraft sit underground or in the wrong place?
Aircraft that render but float, sink or occupy the wrong stand usually indicate mismatched scenery rather than failed model matching. Different airport versions can use different elevations, taxiway layouts and parking coordinates, so two pilots may occupy the same network position but see different ground geometry in FSX.