6,566
edits
Decoupling the AI traffic system: Difference between revisions
Switch to {{flightgear url}} to fix the broken Gitorious link.
(→Goals) |
(Switch to {{flightgear url}} to fix the broken Gitorious link.) |
||
| Line 6: | Line 6: | ||
= Status / News = | = Status / News = | ||
This article should be considered outdated, while the underlying issues still persist, this is currently being worked on via the [[HLA]] effort. In particular, there's a prototype named "fgai" that demonstrates how to use HLA in order to decouple an AI component from the FG main loop, please see: [http://www.mail-archive.com/search?q=fgai&l=flightgear-devel%40lists.sourceforge.net] [ | This article should be considered outdated, while the underlying issues still persist, this is currently being worked on via the [[HLA]] effort. In particular, there's a prototype named "fgai" that demonstrates how to use HLA in order to decouple an AI component from the FG main loop, please see: [http://www.mail-archive.com/search?q=fgai&l=flightgear-devel%40lists.sourceforge.net] [{{flightgear url|commit=d79b2385b4f4a64a2460c32e6123ea399bfa83d6}}]. | ||
The long term plan is to move the current AI system into its own HLA component, so that it can be run separately from the fgfs main thread and to ensure that AI traffic can be properly synchronized among multiple clients (multiplayer) or multiple fgfs instances that are configured in a master/slave fashion (think FSWeekend/LinuxTag). | The long term plan is to move the current AI system into its own HLA component, so that it can be run separately from the fgfs main thread and to ensure that AI traffic can be properly synchronized among multiple clients (multiplayer) or multiple fgfs instances that are configured in a master/slave fashion (think FSWeekend/LinuxTag). | ||