Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/05/20 in all areas

  1. ... and using 2200 for "IFR, in non-controlled space" is really just a VATSIM-ism anyway. If you file IFR but squawk 1200, the FSD server apparently throws a command back to your pilot client to automatically kick your transponder to 2200 just so you won't appear as a VFR target on controller's scopes. FSINN definitely recognized and responded to this command. I'm not sure whether xPilot and vPilot do; I think not, but I don't know for certain. Swift developers encountered this issue shortly after the client's release because they didn't know about that command and early versions of Swift did not know how to handle that response from the server, crashing the client.
    1 point
×
×
  • Create New...