20,741
edits
FGAIS: Difference between revisions
Jump to navigation
Jump to search
→Design
(→Design) |
(→Design) |
||
| Line 58: | Line 58: | ||
* fgais should be able to send aircraft position only in area of the user (need to receive position of the client and calculate the "out of range" limit. This should be easy to use fgms implementation) | * fgais should be able to send aircraft position only in area of the user (need to receive position of the client and calculate the "out of range" limit. This should be easy to use fgms implementation) | ||
* fgais should be able to send aircraft position as AI traffic instead of MP traffic (need to create a new "Magic Header" like it's already done in fgms for relay/tracker and add a filter in flightgear in order to make the difference between AI traffic and MP traffic. | * fgais should be able to send aircraft position as AI traffic instead of MP traffic (need to create a new "Magic Header" like it's already done in fgms for relay/tracker and add a filter in flightgear in order to make the difference between AI traffic and MP traffic. | ||
I agree that the fgais <-> fgms <-> FG achitecture makes sense. | |||
I had a look at the fgais and fgms code last night. Combining them into an fgais server that's MP aware and only sends data for aircraft in the area of MP aircraft looks pretty straightforward. | |||
== Related == | == Related == | ||