2,561
edits
Proposals:AI Traffic related: Difference between revisions
Jump to navigation
Jump to search
m
moving related items from FGFS Todo here
mNo edit summary |
m (moving related items from FGFS Todo here) |
||
| Line 5: | Line 5: | ||
* Factor out AI traffic code in order to make it work with the multiplayer client code: incorporate the AI traffic system with the multiplayer system so that the AI traffic system becomes a special multi-aircraft client and can thus sort of 'inject' AI aircraft/traffic instances into multiplayer servers. Next abstract out the current AI traffic system so that it can be run as a standalone executable, that way multiplayer servers could optionally also run their own dedicated AI traffic clients that can connect to a multiplayer server (authentication permitting) in order to inject AI traffic (multiple AI aircraft instances) into a multiplayer server. Eventually, this would address issues concerning the discrepancy between multiplayer clients running with enabled AI traffic scenarios that are currently not yet synchronized. Ultimately, this would add the possibility to have server-side (AI traffic) scenarios for all connected multiplayer clients. Export all AI/multiplayer traffic nodes to local property tree, using a configurable range ([http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13205.html related mailing list discussion from nov/2007]). | * Factor out AI traffic code in order to make it work with the multiplayer client code: incorporate the AI traffic system with the multiplayer system so that the AI traffic system becomes a special multi-aircraft client and can thus sort of 'inject' AI aircraft/traffic instances into multiplayer servers. Next abstract out the current AI traffic system so that it can be run as a standalone executable, that way multiplayer servers could optionally also run their own dedicated AI traffic clients that can connect to a multiplayer server (authentication permitting) in order to inject AI traffic (multiple AI aircraft instances) into a multiplayer server. Eventually, this would address issues concerning the discrepancy between multiplayer clients running with enabled AI traffic scenarios that are currently not yet synchronized. Ultimately, this would add the possibility to have server-side (AI traffic) scenarios for all connected multiplayer clients. Export all AI/multiplayer traffic nodes to local property tree, using a configurable range ([http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13205.html related mailing list discussion from nov/2007]). | ||
* merge AI and ATC code so that both work properly with each other | * merge AI and ATC code so that both work properly with each other | ||
* Add command line option to enable/disable individual AI scenarios, so that there is no manual editing of XML files involved for users, preferably this should also become a runtime configurable setting, though | |||
[[Category:Code Cleanup]] | [[Category:Code Cleanup]] | ||