6,566
edits
FGTraffic: Difference between revisions
Jump to navigation
Jump to search
m
Switch to the {{forum url}} template for all forum links.
m (Switch to the {{forum url}} template for all forum links.) |
|||
| Line 34: | Line 34: | ||
Durk is inclined to break away from the approach he took for the current [[AI traffic]] system. The code has become too clunky too be maintainable, he will try to spend a limited portion of his development time for bug fixing the current code, but please don't expect any major changes any more. The new approach he has in mind should surpass everything we currently have, but it's going to take some time until it's all implemented. <ref>{{cite web | Durk is inclined to break away from the approach he took for the current [[AI traffic]] system. The code has become too clunky too be maintainable, he will try to spend a limited portion of his development time for bug fixing the current code, but please don't expect any major changes any more. The new approach he has in mind should surpass everything we currently have, but it's going to take some time until it's all implemented. <ref>{{cite web | ||
|url = | |url = {{forum url|p=298593}} | ||
|title = <nowiki> FGTraffic 2020: Road map for a new AI traffic system design </nowiki> | |title = <nowiki> FGTraffic 2020: Road map for a new AI traffic system design </nowiki> | ||
|author = <nowiki> durk </nowiki> | |author = <nowiki> durk </nowiki> | ||
| Line 55: | Line 55: | ||
It's Durk's explicit intention to make the new system 100% compatible with the current content (traffic database, AI Aircraft, liveries, etc). Finally, although Durk wants to keep the technical side of the discussion focused on the mailing list, as per project policy, he's open to suggestions for improvement from content developers. <ref>{{cite web | It's Durk's explicit intention to make the new system 100% compatible with the current content (traffic database, AI Aircraft, liveries, etc). Finally, although Durk wants to keep the technical side of the discussion focused on the mailing list, as per project policy, he's open to suggestions for improvement from content developers. <ref>{{cite web | ||
|url = | |url = {{forum url|p=298593}} | ||
|title = <nowiki> FGTraffic 2020: Road map for a new AI traffic system design </nowiki> | |title = <nowiki> FGTraffic 2020: Road map for a new AI traffic system design </nowiki> | ||
|author = <nowiki> durk </nowiki> | |author = <nowiki> durk </nowiki> | ||
| Line 157: | Line 157: | ||
More specifically, there are the following fundamental limitations in the current code base: | More specifically, there are the following fundamental limitations in the current code base: | ||
* AI traffic runs in the FlightGear main loop | * AI traffic runs in the FlightGear main loop | ||
* AI traffic cannot currently make use of existing FlightGear subsystems (FDMShell, Autopilot, Route Manager), i.e. there is code duplication <ref> | * AI traffic cannot currently make use of existing FlightGear subsystems (FDMShell, Autopilot, Route Manager), i.e. there is code duplication <ref>{{forum url|p=134970}}</ref> | ||
* AI Traffic is not synchronized across multiple instances of FlightGear | * AI Traffic is not synchronized across multiple instances of FlightGear | ||
* Unclear distribution of labor between the AIModels, ATC, and Traffic Manager subsystems | * Unclear distribution of labor between the AIModels, ATC, and Traffic Manager subsystems | ||