MediaWiki has been updated to version 1.35.1. Please report any problems here.

Changes

Jump to navigation Jump to search
m
pm2wiki
Line 11: Line 11:  
     |author=<nowiki>Hooray</nowiki>
 
     |author=<nowiki>Hooray</nowiki>
 
     |date=<nowiki>Wed Jun 25</nowiki>
 
     |date=<nowiki>Wed Jun 25</nowiki>
 +
  }}
 +
}}
 +
 +
{{FGCquote
 +
  |The whole "FGCanvas" effort thing is actually about something different, but it entails moving FDM, AP, RM etc into an "AircraftManager" class, which would be the main step required to allow AI aircraft to be also driven by FDM, AP and route manager (and possibly even an aircraft-specific Nasal instance)
 +
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213487#p213487
 +
    |title=<nowiki>Re: How advanced is FlightGear's AI?</nowiki>
 +
    |author=<nowiki>Hooray</nowiki>
 +
    |date=<nowiki>Thu Jun 26</nowiki>
 +
  }}
 +
}}
 +
 +
{{FGCquote
 +
  |I went ahead to see how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as  each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably.<br/>
 +
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|450px]]
 +
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214262#p214262
 +
    |title=<nowiki>Re: FGCanvas Experiments & Updates</nowiki>
 +
    |author=<nowiki>Hooray</nowiki>
 +
    |date=<nowiki>Mon Jul 07</nowiki>
 
   }}
 
   }}
 
}}
 
}}

Navigation menu