2,561
edits
Decoupling the AI traffic system: Difference between revisions
Jump to navigation
Jump to search
m
→Goals
mNo edit summary |
m (→Goals) |
||
| Line 2: | Line 2: | ||
= Goals = | = Goals = | ||
Decouple the AI traffic system from FlightGear so that it may eventually become a standalone component, which would not only help improve runtime performance but also provide a possibility to handle AI state synchronization across multiple FlightGear multiplayer clients by feeding in all AI traffic via the FlightGear multiplayer server, so that all connected clients would get to see identical AI traffic, that is properly synchronized. | Decouple the AI traffic system from FlightGear so that it may eventually become a standalone component, which would not only help improve runtime performance (for FlightGear, as well as the AI system) but also provide a possibility to handle AI state synchronization across multiple FlightGear multiplayer clients by feeding in all AI traffic via the FlightGear multiplayer server, so that all connected clients would get to see identical AI traffic, that is properly synchronized. | ||
= Background Information = | = Background Information = | ||
== 2002 == | == 2002 == | ||