Can't see other aircraft on VATSIM in FSX? Fix vPilot SimConnect, model-matching and AI model errors with this focused checklist.
If you cannot see other VATSIM aircraft in FSX, vPilot is usually connected to the network but cannot inject or model-match the traffic. Confirm vPilot has a SimConnect connection, install compatible AI models and matching rules, then check its messages for model errors. FSX's normal AI traffic slider does not supply VATSIM traffic.
What should I check first?
Start by confirming that both sides of the connection are working: vPilot must be connected to VATSIM and communicating with the running simulator.
- Load an FSX flight completely. Wait until your aircraft is sitting in the simulator before connecting vPilot.
- Check the simulator connection. If vPilot reports that it cannot connect to FSX or SimConnect, repair that problem before changing any aircraft models. Our FSX and vPilot setup instructions cover the required connection and model-matching components.
- Confirm that another pilot is genuinely nearby. Controllers, observers and pilots hundreds of miles away do not produce visible aircraft around you. Network maps may also update less often than the live client.
- Read the vPilot messages. Warnings about no matching model, an unavailable model or FSX failing to create an aircraft point directly to model matching.
- Restart after installing models. FSX and vPilot may need to rescan the available simulator aircraft before newly installed models can be used.
If vPilot cannot communicate with FSX at all, check its SimConnect installation and any firewall rules. In a remote setup where vPilot runs on another computer, the networked SimConnect configuration must also be correct. Avoid downloading miscellaneous replacement DLL files; use the components supplied with the simulator or client installation.
What does the symptom tell you?
| Symptom | Most likely cause |
|---|---|
| No VATSIM aircraft appear anywhere | vPilot is not connected to FSX, no pilots are within range, or traffic injection is being blocked |
| Callsigns are detected but no models appear | Missing AI models, invalid matching rules or FSX failing to create the selected model |
| Only certain aircraft are missing | The rule for that aircraft type or airline points to a model that is absent or incompatible |
| Aircraft appear with the wrong type or livery | Model matching is working, but only a generic fallback model is available |
| Aircraft appear underground or inside buildings | The two pilots are using different airport scenery, parking positions or ground elevations |
Why does vPilot connect but show no aircraft models?
A successful VATSIM login does not prove that FSX can render the other pilots. vPilot receives their callsigns, aircraft types and positions, then uses model-matching rules to select locally installed AI models.
The model package must contain the actual aircraft models. A matching rule by itself does not include an aeroplane. Those models normally sit under SimObjects\Airplanes, or in another SimObjects directory registered with FSX; the boxed and Steam editions use different installation roots. See our guide to locating FSX aircraft folders before moving or reinstalling anything.
A mistake we see constantly is assuming the folder name controls model matching. Rules normally refer to the model's title= value in the relevant [fltsim.x] entry of aircraft.cfg. If that title is missing, duplicated or different from the rule, vPilot cannot call the intended model.
Use models designed for AI traffic and compatible with FSX. Arbitrary flyable add-ons may have complex systems, unsuitable animations or configurations that fail when created as traffic. Older models made for another simulator can also display incorrectly, particularly when FSX's DirectX 10 Preview is enabled.
Do FSX traffic sliders affect VATSIM aircraft?
The airline and general aviation traffic sliders control FSX's offline AI, not the pilots supplied by vPilot. They can be set to zero while using VATSIM, which prevents computer-generated traffic from occupying gates or being mistaken for network pilots.
FSX's built-in multiplayer is separate as well. Do not join an FSX multiplayer session at the same time; vPilot injects network aircraft through SimConnect. Our explanation of FSX multiplayer versus external online networks clarifies the difference.
Settings inside vPilot can still limit the number of displayed aircraft or their drawing range. If only distant traffic is absent, check those client limits before reinstalling models. Aircraft labels merely control the text shown above an aeroplane; enabling labels cannot fix a missing model.
Why are only some VATSIM aircraft missing?
When most pilots are visible, SimConnect and traffic injection are already working. Concentrate on the aircraft type named in the vPilot warning and the matching rule that selected it.
- Confirm that the referenced model is installed in an active FSX SimObjects path.
- Check that its
aircraft.cfgentry has a valid, uniquetitle=value. - Replace or correct rules that refer to models you do not own.
- Use a generic fallback for aircraft types or liveries absent from your package.
- If the problem began after adding one model set, remove or disable that set and test again.
If ordinary computer-controlled aircraft are also missing, treat that as a separate FSX problem and use our FSX AI traffic troubleshooting checks. When offline AI works but VATSIM pilots do not, the fault remains with vPilot's connection, model library or matching configuration.