- Tue Jul 18, 2017 8:44 pm
Most common reasons include:
1. You don't have AI that support the aircraft type that you are trying to see. For example, BAW doesn't fly the C172, but if someone logs in as a BAW C172, regardless of what they filed in their flight plan
, and you don't have a BAW C172 AI (I'm guessing it doesn't exist!), you are likely to see a generic representation.
2. Similar to above, a user, regardless of what they filed in their flight plan
, logs on using an incorrect aircraft type for which you don't have AI. For example, instead of logging in as a B772, a member accidentally logs on as a B775. That aircraft doesn't exist, so there is likely no AI for it, so you are likely to see a generic representation.
One way to try to troubleshoot is, when you see a generic representation (e.g. white A321), type .aircraft into vPilot. A window will open that shows you all aircraft within range of yours, including the callsign and aircraft type code. For any generic aircraft (e.g. white A321s), look at their callsign and aircraft type. Determine if they logged in with an invalid aircraft type. If so, your issue was caused by them. If not, determine if you have AI to support the callsign prefix and aircraft type. If not, either they are using a wonky combination, which is their fault, or you don't have enough suitable AI, which would be your problem to fix (assuming you want a better simulation experience).