2,561
edits
Decoupling the AI traffic system: Difference between revisions
Jump to navigation
Jump to search
m
→Partitioning Rationale
m (→Goals) |
|||
| Line 5: | Line 5: | ||
= Partitioning Rationale = | = Partitioning Rationale = | ||
* "[...]I think a more flexible approach may be "self-contained" modules communicating by passing "properties" over TCP. The "remote" FDM is already a possibility and there is an example of a remote joystick but how easy would it be to break up the rest of flightgear?"[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg09046.html] | * "[...]I think a more flexible approach may be "self-contained" modules communicating by passing "properties" over TCP. The "remote" FDM is already a possibility and there is an example of a remote joystick but how easy would it be to break up the rest of flightgear?"[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg09046.html] | ||
| Line 14: | Line 10: | ||
* "I agree that the approach you suggest, of starting with a single subsystem/module is probably the best way to start tackling this issue."[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg09064.html] | * "I agree that the approach you suggest, of starting with a single subsystem/module is probably the best way to start tackling this issue."[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg09064.html] | ||
* "It'd be worth identifying which subsystems are the big time sinks (FDM? AItraffic?) to prioritise this." [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18063.html] | |||
* "I think the main targets for parallelization are the rendering pipeline and various "add-on" systems, like the traffic manager."[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16400.html] | |||
For additional details regarding partioning FlightGear into distinct modules that may be run as standalone processes doing IPC via the property tree, please also see [[Modularizing, parallelizing and distributing FlightGear]]. | For additional details regarding partioning FlightGear into distinct modules that may be run as standalone processes doing IPC via the property tree, please also see [[Modularizing, parallelizing and distributing FlightGear]]. | ||