The flightplan works great with regard to waypoints, but I have to manually insert an altitude in gui ap. This works great and stable too... It just leads me to believe that the property tree is messed up somewhere. Is coding the only correction here or can something be done via xml file or even a nasal bind (new to nasal, but it seems like it has something useful to my plight)
Thanks for your efforts... Craig E. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee Elliott Sent: Thursday, November 10, 2005 7:53 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] waypoints, waypoint loops, route manger On Wednesday 09 Nov 2005 22:02, Craig E. Staples wrote: > Hello all, > > I'm trying certain senarios via waypoints and varying altitudes > by using flightplan/.fgfsrc file. I plan on implementing a data input > change for route manger code to read a file with my data, but in the > mean time I was wondering if there's a reason why [EMAIL PROTECTED] has issues > maintaining the wanted altitude. I have alts at 15k, but the craft > drifts to > 20 k, etc... I also want to maintain a senario for a certain > amount of time, so go to waypoint 1 and 2 looping for 10 mins, etc... > then hit waypoints 3, 4 and 5... If anyone has a better way to > approach this please give me ur ideas. Thanks a lot.. > > Regards, > Craig E. I don't know the straight answer to this problem but there are a couple of factors that need to be considered in using flightplan data, like the [EMAIL PROTECTED] info in a flightplan file, or supplied on the console/termninal at start-up. The first is that if you want any altitude hold there will have to be a controller, or more likely a cascade of controllers set up in the autopilot to do it. The reference or target altitude that the autopilot altitude controller tries to achieve needs to be available in the property tree, so that it can read it. If the altitudes supplied in the flightplan aren't transferred to the right place in the property tree then the a/p controllers can't use them. The second factor is that just setting a target altitude will not mean that an a/c will fly properly to that altitude. Climbing to a new, higher altitude that's a lot different to the current altitude isn't a simple matter and must be done at the correct speed and may need to be done in steps. The fuel state and payload will also have a great influence on how the climb is achieved. I guess a simple list of [EMAIL PROTECTED] waypoints is inadequate because it lacks the climb info/requirements. LeeE _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
