2,561
edits
Proposals:AI Traffic related: Difference between revisions
Jump to navigation
Jump to search
m
adding pointer to related discussion about refactoring the AI traffic code in order to make it become a client that is connect to fgms instead of directly running inside the fgfs main loop
m (adding pointer to AI traffic performance discussion found on the forums) |
m (adding pointer to related discussion about refactoring the AI traffic code in order to make it become a client that is connect to fgms instead of directly running inside the fgfs main loop) |
||
| Line 4: | Line 4: | ||
* improve AI traffic performance, it still seems to affect overall FlightGear performance according to various discussions [http://flightgear.org/forums/viewtopic.php?f=2&t=6212] | * improve AI traffic performance, it still seems to affect overall FlightGear performance according to various discussions [http://flightgear.org/forums/viewtopic.php?f=2&t=6212] | ||
* allow nasal scripts in AI object XM files, so that nasal code can move AI objects along predefined routes | * allow nasal scripts in AI object XM files, so that nasal code can move AI objects along predefined routes | ||
* 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]). Also see [http://sourceforge.net/tracker/index.php?func=detail&aid=1849308&group_id=161928&atid=821811 this] discussion on the fgms tracker at sourceforge. | ||
* 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 | * 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 | ||