-
Notifications
You must be signed in to change notification settings - Fork 3
FSD Protocol Introduction
FSD(Flight Simulation Daemon)是一个用于连接管制和机组的一个后端处理软件
FSD主流的协议有三种:FSD V3.000 draft 9(后续简称为FSD9)、Vatsim协议、Vatsim(token)协议、VATSIM2022协议。
-
FSD9协议:
由于目前编者没有找到FSD9的官方定义文件,仅在kuroneko/FSD中找到下文
This repository is derived from the last known public copy of Marty Bochane's FSD 2 source code.
It originated from a zip file 'fsd1110.zip', which bears indications it may have been "FSFDT Windows FSD Beta from FSD V3.000 draft 9". It is almost identical to contents of the fsd-ubuntu-120413.tar.bz2 distribution still available from the Apollo3 flight simulator site.
这个仓库源自 Marty Bochane 的 FSD 2 源代码的最后已知公开副本。
它起源于一个名为 'fsd1110.zip' 的压缩文件,显示它可能是 "FSFDT Windows FSD Beta from FSD V3.000 draft 9"。它几乎与 Apollo3 飞行模拟器网站上仍然可用的 fsd-ubuntu-120413.tar.bz2 发行版内容相同。
- Vatsim协议、Vatsim(token)协议与VATSIM2022协议:
顾名思义是一种Vatsim自研的协议, Vatsim(token)协议顾名思义就是在Vatsim协议的基础上添加了Token, 这里的Token指的是JWT, 主要用于身份验证
目前主流的Vatsim协议一般都是指Vatsim(token)协议, 总不可能让管制用着旧版的EuroScope连接你的服务器,就因为没做token
VATSIM2022协议则是在Vatsim(token)的基础上添加了challenge/response认证
由于编者没有找到官方FSD协议标准文件, 故后续所述的协议均为通过阅读Swift源码与使用EuroScope连接实际FSD服务器进行抓包后推测得出,故而结果可能会不准确,若与实际情况有所偏差,一切以实际为准
FSD(Flight Simulation Daemon) is a back-end processing software to connect controls and pilots together
There are three mainstream protocols for FSD: FSD V3.000 draft 9(hereinafter referred to as FSD9), Vatsim protocol, Vatsim(token) protocol and Vatsim2022 protocol.
-
FSD9 Protocol
Due to found no FSD9 official protocol definition file, only in the kuroneko/FSD found text below
This repository is derived from the last known public copy of Marty Bochane's FSD 2 source code.
It originated from a zip file 'fsd1110.zip', which bears indications it may have been "FSFDT Windows FSD Beta from FSD V3.000 draft 9". It is almost identical to contents of the fsd-ubuntu-120413.tar.bz2 distribution still available from the Apollo3 flight simulator site.
- Vatsim Protocol, Vatsim(token) Protocol and Vatsim2022 protocol:
As the name suggests, it is a self-developed protocol of Vatsim. The Vatsim(token) protocol, as the name suggests, adds a Token on the basis of the Vatsim protocol. Here, the Token refers to JWT, which is mainly used for identity verification
Currently, the mainstream Vatsim protocol generally refers to the Vatsim(token) protocol. It's impossible for a controller to connect to your server using an old version of EuroScope just because no token has been created
The VATSIM2022 protocol adds challenge/response authentication on top of Vatsim(token)
As the editor did not find the official FSD protocol standard document, all the protocols described later were inferred by reading the Swift source code and using EuroScope to connect to the actual FSD server for packet capture. Therefore, the results may not be accurate. If there is any deviation from the actual situation, the actual situation shall prevail
Copyright © 2025 Half_nothing. All rights reserved.