From: Mike M. <li...@li...> - 2010-12-11 20:18:06
|
Sent from my Samsung Epic™ 4G Erik Hofman <er...@eh...> wrote: >On Wed, 2010-12-08 at 17:13 -0800, Hal V. Engel wrote: >> I used 120Hz (this is the same as the freq. of the FDM) and it almost works. >> But the problem is that on each run there is enough variation in the behavior >> of the model that the control inputs eventually get out of sync with the state >> of the flight test and it ends up crashing. In fact it appears that things >> like what view is being used affect how the aircraft behaves. >> >> I am doing spins during the flight and the exit state of the spin (direction, >> roll angle, speed and so on) appears to vary in each run and that is where I >> run into the issue since the control inputs don't match the state of the >> aircraft at that point. > >Hm, you probably should make sure that you use the same weather settings >for every run. At the moment the GIT version of FlightGear always >enables METAR fetching for example. > >Thinking about it there can also be some influence from attached >joysticks and perhaps the mouse.. > >Erik > > >------------------------------------------------------------------------------ >This SF Dev2Dev email is sponsored by: > >WikiLeaks The End of the Free Internet >http://p.sf.net/sfu/therealnews-com >_______________________________________________ >Flightgear-devel mailing list >Fli...@li... >https://lists.sourceforge.net/lists/listinfo/flightgear-devel |