Re: [Flightgear-devel] Crash when KMYF not KSFO
Tony Peden writes: OK, I've figured out what the problem is. At intialization both the altitude and runway altitude are set: Start common FDM init ...initializing position... FGJSBsim::set_Longitude: -2.0444 FGJSBsim::set_Latitude: 0.572695 cur alt (ft) = 0 FGJSBsim::set_Altitude: 382.535 lat (deg) = 32.813 ...initializing ground elevation to 382.535ft... common_init(): set ground elevation 382.535 FGJSBsim::set_Runway_altitude: 382.535 ...initializing sea-level radius... lat = 32.813 alt = 382.535 FGJSBsim::set_Sea_level_radius: 2.09052e+07 ...initializing velocities... FGJSBsim::set_V_calibrated_kts: 0 ...initializing Euler angles... FGJSBsim::set_Euler_Angles: 0, 0.0074002, 5.14977 End common FDM init However, when the altitude is changed (for whatever reason) the ground elevation is not reset: fgFDMForceAltitude: 126.073 FGJSBsim::set_Altitude: 413.625 ^^^ lat (deg) = 32.813 FGJSBsim::set_Sea_level_radius: 2.09256e+07 (*) Current Altitude = 116.60 123.07 forcing to 126.07 Ground Trim So as far as JSBSim is concerned, the ground is still at 382.53 ft and the trimming routine does exactly the right thing with that piece of information: it lowers the aircraft until the gear are holding it up. Tony, This seems to gell with what I saw (as far as I got yesterday.) Question: Who's responsibility is it (or should it be) to set the runway elevation inside of FGInterface? Traditionally we have expected anything inside FGInterface to be set by the flight dynamics model code. In fact, FGInterface is a base class for JSBSim, YASim, etc. so it doesn't really even exist on it's own in the context of flightgear. FlightGear does maintain and update the following variable: scenery.get_cur_elev() It is the variables inside of FGInterface and JSBSim/YASim/etc. that aren't getting set properly. So, when you are looking at it from the perspective of the FDM, it might seem like runway elevation should be set by FlightGear, but when you are looking at it from the perspective of the FlightGear side, FlightGear treats the FGInterface and everything below as read only. In the future, the way things are going, you could think of the FGInterface class only as being there as a convenience for JSBSim and YASim and LaRCsim, etc. FlightGear will not care or know of it's existance and the interface between FlightGear and the FDM models will be handled completely through the property manager. At that point, it will be the responsibility of the FDM to read the important FlightGear properties (i.e. control positions, weather, ground elevation, etc.) and then do what ever needs to be done internally to keep track of these and use them as inputs to the flight and gear models. Does that make sense? We have started down that direction somewhat, but after 0.7.9 I'd like to finish up reworking the interface along these lines. We should also investigate why FlightGear is reporting one elevation initially and then amending it to something else later ... there's something not quite right there either. That investigation isn't going to happen though before 0.7.9. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Question: Who's responsibility is it (or should it be) to set the runway elevation inside of FGInterface? JSBSIm does fine on its own by using a runway elevation (or scenery elevation, or whatever) of zero - assuming sea level operations only, for now. JSBSim defaults to sea level in standalone mode. We have to default somewhere. If FlightGear wants us to follow them to somewhere and fly from there, how else can we get the runway/scenery elevation except from FlightGear?? It's a two-way street; FlightGear has to tell us about the world it is simulating (the scene it is showing and where in the world it is). We can do the rest. Maybe I am unclear on what you are saying that FlightGear does and doesn't do. Am I missing the point (I haven't had my morning coffee, yet, so maybe I am)? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
[EMAIL PROTECTED] writes: Question: Who's responsibility is it (or should it be) to set the runway elevation inside of FGInterface? JSBSIm does fine on its own by using a runway elevation (or scenery elevation, or whatever) of zero - assuming sea level operations only, for now. JSBSim defaults to sea level in standalone mode. We have to default somewhere. If FlightGear wants us to follow them to somewhere and fly from there, how else can we get the runway/scenery elevation except from FlightGear?? It's a two-way street; FlightGear has to tell us about the world it is simulating (the scene it is showing and where in the world it is). We can do the rest. Maybe I am unclear on what you are saying that FlightGear does and doesn't do. Am I missing the point (I haven't had my morning coffee, yet, so maybe I am)? Jon, I didn't mean to evoke a defensive response. FlightGear does provide the ground elevation (continuously updating) via: scenery.get_cur_elev() The question is, who should be updating the values inside of FGInterface (which are really inside the JSBSim class since JSBSim inherits from FGInterface.) This is what JSBSim is using for runway elevation and is what is not getting updated when starting at KMYF. The answer probably looks different depending on which side of the fence you are sitting. I'm on the FlightGear side of the fence, not the FDM side, so bear that in mind. :-) The point I was trying to make is that there is some confusion here that we are trying to investigate and sort out. JSBSim properly handles updating the runway/ground elevation most of the time, but here is at least one situation where it doesn't. YASim doesn't handle this at all (but Andy's the new kid so we can cut him some slack.) :-) Once we make FlightGear interface with the FDM's completely via the property manager, then this confusion will go away entirely. FlightGear will provide the local ground elevation (or elevations of several wheel points, or a plane and a normal, or whatever) via the property manager. It will be up to the individual FDM's to make use of that information however they see fit. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Crash when KMYF not KSFO
I didn't mean to evoke a defensive response. [That's just how I write, sometimes. I wasn't being defensive - though it came across that way - just argumentative. :-)] The question is, who should be updating the values inside of FGInterface (which are really inside the JSBSim class since JSBSim inherits from FGInterface.) This is what JSBSim is using for runway elevation and is what is not getting updated when starting at KMYF. OK. Well, that sort of sounds like something we should be doing inside of JSBSim.cxx (FGJSBSim), since we declared ourselves keepers of that code sometime ago. I guess I should've looked at JSBSim.cxx first, or waited for Tony and/or David to make a comment since they have been spending more time recently in that code than I have. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
We should also investigate why FlightGear is reporting one elevation initially and then amending it to something else later ... there's something not quite right there either. That investigation isn't going to happen though before 0.7.9. This, it seems to me, is the root cause of the problem. However, it looks like the fgFDMForceAltitude function does not update the runway altitude. If it did, it would likely make the immediate problem go away but also have the effect of covering up what's really wrong. As for whose responsible for what, I can only say that I wasn't trying to push anything off on anyone this morning. I was out of time and needed to get to work, so I just posted the info I had, figuring that if you or David had the time and/or inclination to fix it you could. If not, I'd just wait and see what I could do about it myself. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel __ Do You Yahoo!? Got something to say? Say it better with Yahoo! Video Mail http://mail.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Curtis L. Olson writes: The question is, who should be updating the values inside of FGInterface (which are really inside the JSBSim class since JSBSim inherits from FGInterface.) This is what JSBSim is using for runway elevation and is what is not getting updated when starting at KMYF. JSBSim.cxx is the glue between JSBSim and FlightGear -- it should grab any values JSBSim might need. All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Curtis L. Olson wrote: JSBSim properly handles updating the runway/ground elevation most of the time, but here is at least one situation where it doesn't. YASim doesn't handle this at all (but Andy's the new kid so we can cut him some slack.) :-) Uh, stupid question: where do I stick the number? I can't imagine this is difficult to fix. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Andy Ross writes: Curtis L. Olson wrote: JSBSim properly handles updating the runway/ground elevation most of the time, but here is at least one situation where it doesn't. YASim doesn't handle this at all (but Andy's the new kid so we can cut him some slack.) :-) Uh, stupid question: where do I stick the number? I can't imagine this is difficult to fix. Should be a breeze. Essentially you are assuming that the runway elevation field in the FGInterface structure is getting updated externally by FlightGear, but FlightGear treats everything from FGInterface on down as 'read only'. So whatever this value starts out as on initialization is what it stays at if YASim doesn't change it. FlightGear provides 'scenery-get_cur_elev()' which you could grab every time your 'update()' is called and stuff into the runway elevation field in FGInterface ... Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Curtis L. Olson wrote: Andy Ross wrote: Uh, stupid question: where do I stick the number? I can't imagine this is difficult to fix. Should be a breeze. Essentially you are assuming that the runway elevation field in the FGInterface structure is getting updated externally by FlightGear, but FlightGear treats everything from FGInterface on down as 'read only'. Roger that; I think I get it now. I don't have hardware at work to test against, but if someone is in a rush and wants to guinea-pig for a bit, the following patch to YASim.cxx should fix it. Comments in JSBSim indicate that the scenery object is returning meters from MSL, but I didn't investigate far enough to be sure I got the units right. Andy RCS file: /var/cvs/FlightGear-0.7/FlightGear/src/FDM/YASim/YASim.cxx,v retrieving revision 1.8 diff -u -r1.8 YASim.cxx --- YASim.cxx 24 Dec 2001 12:54:04 - 1.8 +++ YASim.cxx 15 Feb 2002 17:39:14 - @@ -225,7 +225,11 @@ wind[0] = get_V_north_airmass() * FT2M; wind[1] = get_V_east_airmass() * FT2M; wind[2] = get_V_down_airmass() * FT2M; -double ground = get_Runway_altitude() * FT2M; + +// The ground elevation doesn't come from FGInterface; query it +// from the scenery and set it for others to find. +double ground = scenery.get_cur_elev(); +set_Runway_altitude(ground * FT2M); -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
I think that does the trick, thank! Curt. Andy Ross writes: Curtis L. Olson wrote: Andy Ross wrote: Uh, stupid question: where do I stick the number? I can't imagine this is difficult to fix. Should be a breeze. Essentially you are assuming that the runway elevation field in the FGInterface structure is getting updated externally by FlightGear, but FlightGear treats everything from FGInterface on down as 'read only'. Roger that; I think I get it now. I don't have hardware at work to test against, but if someone is in a rush and wants to guinea-pig for a bit, the following patch to YASim.cxx should fix it. Comments in JSBSim indicate that the scenery object is returning meters from MSL, but I didn't investigate far enough to be sure I got the units right. Andy RCS file: /var/cvs/FlightGear-0.7/FlightGear/src/FDM/YASim/YASim.cxx,v retrieving revision 1.8 diff -u -r1.8 YASim.cxx --- YASim.cxx 24 Dec 2001 12:54:04 - 1.8 +++ YASim.cxx 15 Feb 2002 17:39:14 - @@ -225,7 +225,11 @@ wind[0] = get_V_north_airmass() * FT2M; wind[1] = get_V_east_airmass() * FT2M; wind[2] = get_V_down_airmass() * FT2M; -double ground = get_Runway_altitude() * FT2M; + +// The ground elevation doesn't come from FGInterface; query it +// from the scenery and set it for others to find. +double ground = scenery.get_cur_elev(); +set_Runway_altitude(ground * FT2M); -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
On Thu, 2002-02-14 at 09:09, Alex Perry wrote: The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO. Immediate crash. It's a long way to commute, could we fix that sometime? I've sent a fix off to Curt for this. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Crash when KMYF not KSFO
The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO. Immediate crash. It's a long way to commute, could we fix that sometime? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Alex Perry writes: The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO. Immediate crash. It's a long way to commute, could we fix that sometime? Hmmm, I can verify this same problem here too. With fgfs --airport-id=KMYF : - Flightgear starts up. - The JSBSim constructer is called, and the aircraft config file is loaded. (But JSBSim is not init'ed until after the scenery loads so we can pass in a proper ground elevation to the trimming routine.) - FlightGear continues to load/init various systems. - FlightGear finally gets around to loading the local scenery tile and a valid ground elevation appears on the bus. - FlightGear determines that it is now ok to run the JSBSim init() routine. This triggers a ground trim and JSBSim prints touch down reports and a bunch of other output and finally returns with: Trim successful JSBSim State Trim complete - This is immediately followed by a long sequence of: 0: GEAR_CONTACT 1 1: GEAR_CONTACT 1 2: GEAR_CONTACT 1 3: GEAR_CONTACT 1 4: GEAR_CONTACT 0 5: GEAR_CONTACT 0 6: GEAR_CONTACT 0 7: GEAR_CONTACT 0 8: GEAR_CONTACT 1 etc. . . . 56: GEAR_CONTACT 1 - It appears that JSBSim has trimmed the aircraft to below ground so FlightGear notices this and attempts to force JSBSim to use a higher elevation. This triggers another ground trim, again which ends up several meters underground, again causing FGFS to try to force JSBSim back up above the ground. - There seems to be a long exchange of angry words with subsequent JSBSim trims failing. - This is followed by JSBSim spewing out 985 successive GEAR_CONTACT bool messages. - Again FGFS tries to force/coax JSBSim up to ground level. - More of the same with JSBSim triming under ground, the gear code goes berzerk, spews 100's more GEAR_CONTACT messages. - Eventually JSBSim flags a CRASH. - JSBSim is hosed at this point and copies a completely bogus lat/lon onto the bus. - The flightgear tile pager sees that we have moved to a completely impossible location, flags a non-recoverable error and exits the sim. Wow, that was really ugly. It happens very quickly, and most of those messages scroll right on by before you can see them if you don't run the output through less or more or something similar. So it appears that at least for KMYF, JSBSim and FlightGear are having a very strong disagreement over the elevation of the ground, and neither is willing to budge. Sounds like two typical flightgear developers. :-) I haven't been able to reproduce this at any other airport I've tried, only KMYF. Ok, after all that, I tried the same thing with the YASim c172 at KMYF and something is wierd at KMYF. YASim started just fine and took off fine, but the entire time, FGFS was spewing message about being below ground. I wonder if it is a problem with the scenery models right there? Hmmm, this appears at the moment to be some sort of flightgear problem??? Ok, looking further, it appears that nothing, no place, no where is setting the runway elevation any more ... it get's initialized at startup, but then never is updated as the aircraft moves. That is really odd ... what got sliced out of the code? It's been a while so I don't remember where this was supposed to happen. The view code has a bit of a hack to force the view height above the ground so it's hard to notice. This is really weird. In theory, you'd see very strange effects if you started at a lower elevation airport and flew to a different elevation aiport and tried to land. Ok, there is something really strange here, probably because things were changed without a proper understanding of how everything worked together. My mind is fryed at the moment looking at this stuff. JSBSim seems to be doing the right thing *except* for at KMYF. YASim assumes that the runway altitude will get set for it externally, that makes a lot of sense, but apparently isn't the case. This sucks. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
So it appears that at least for KMYF, JSBSim and FlightGear are having a very strong disagreement over the elevation of the ground, and neither is willing to budge. Sounds like two typical flightgear developers. :-) Yep :-) This is _very_ similar to what I've been experiencing with 0.7.8 on KEDW - and _only_ on this one, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Ok, there is something really strange here, probably because things were changed without a proper understanding of how everything worked together. My mind is fryed at the moment looking at this stuff. JSBSim seems to be doing the right thing *except* for at KMYF. Whatever it was I said to whomever, I'm sorry and I apologize. Can I have my airport back please ? 8-) Actually, one odd thing. Everything looks fine if you airstart and land. It's also fine if you specify --altitude=400 on the command line. The default airports file shows the correct altitude of 423ft, but the HUD and ALT report noticably less, about 412ft, on startup. YASim assumes that the runway altitude will get set for it externally, that makes a lot of sense, but apparently isn't the case. I haven't tried that yet. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
Curtis L. Olson wrote: Ok, looking further, it appears that nothing, no place, no where is setting the runway elevation any more ... it get's initialized at startup, but then never is updated as the aircraft moves. Ah, which explains why I've never seen this. I only ever bother testing in the default scenery (I mean, I live here, right?), where all the useful airports are essentially at sea level. I'll try to remember to move around more. Ok, after all that, I tried the same thing with the YASim c172 at KMYF and something is wierd at KMYF. YASim started just fine and took off fine, but the entire time, FGFS was spewing message about being below ground. I wonder if it is a problem with the scenery models right there? Oh, and a tangent: what is the purpose behind the code in main.cxx that detects aircraft below ground and resets the elevation accordingly? One immediate bug is that it's not strictly correct -- the aircraft's position is by convention its nose. It can easily be in a crashed state with the nose sticking up in the air. There is a hard-coded 3m guard band in the code that presumably is intended to correct for this, but that can break for big aircraft (747) where 3m is juse noise. I actually have it commented out in my source at home, because it interacts badly with the crash detection. It's entierly possible for the aircraft to slip below ground to fgfs but not to YASim (YASim only checks the gear positions right now), resulting in a non-crash. The aircraft lawn-darts at 600 kts and then drifts slowly over the ground, still reporting a huge airspeed. So far as I can tell, there are no bad reactions to removing the check entirely. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
David Megginson writes: Hmmm, If I start at KSAN and taxi to KMYF, JSBSim seems happy with the ground elevation and everything jives with where FGFS thinks the ground is. The problem seems to be somehow at startup/init time. Very strange and confusing ... I don't see any evidence of a scenery model problem around KMYF. I have a guess about where the problem might be -- I recently modified JSBSim.cxx to copy start-up settings over from the FlightGear before initializing so that we'd get the initial engine values (RPM, etc.) into JSBSim. That might explain the tug-of-war; I'll look at it now. Nope -- that wasn't it (so I'm off the hook for now). Note that there is no problem with It's the JSBSim trimming routine. This works: fgfs --airport-id=KMYF --prop:/sim/startup/trim=false This doesn't work: fgfs --airport-id=KMYF --prop:/sim/startup/trim=true Note that the opposite applies everywhere else; i.e. fgfs --airport-id=KSFO --prop:/sim/startup/trim=false *doesn't* work (the plane flips over). I'll mention again that I'm using scenery I built myself, so this isn't just a glitch in Curt's official scenery build. All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Crash when KMYF not KSFO
On Thu, 2002-02-14 at 09:09, Alex Perry wrote: The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO. Immediate crash. It's a long way to commute, could we fix that sometime? It looks to me like there are at least a couple of problems. 1) the altitude is initially set to 382.53 feet, then later reset to the correct 413 ft. 2) when it is reset, JSBSim still thinks its 382 and trims to that. I'll see what I can do about #2. Finally initializing fdm Starting and initializing JSBsim Start common FDM init ...initializing position... FGJSBsim::set_Longitude: -2.0444 FGJSBsim::set_Latitude: 0.572695 cur alt (ft) = 0 FGJSBsim::set_Altitude: 382.535 lat (deg) = 32.813 ...initializing ground elevation to 382.535ft... common_init(): set ground elevation 382.535 FGJSBsim::set_Runway_altitude: 382.535 ...initializing sea-level radius... lat = 32.813 alt = 382.535 FGJSBsim::set_Sea_level_radius: 2.09052e+07 ...initializing velocities... FGJSBsim::set_V_calibrated_kts: 0 ...initializing Euler angles... FGJSBsim::set_Euler_Angles: 0, 0.0074002, 5.14977 End common FDM init [...] Finished initializing JSBSim FGControls::get_gear_down()= 1 FGJSBsim::set_Euler_Angles: 0, 0.0074002, 5.14977 FGJSBsim::set_Euler_Angles: 6.26822e-20, 0.0074002, 5.14977 FGJSBsim::set_Euler_Angles: 6.26822e-20, 0.0074002, 5.14977 fgFDMForceAltitude: 126.073 FGJSBsim::set_Altitude: 413.625 lat (deg) = 32.813 FGJSBsim::set_Sea_level_radius: 2.09256e+07 (*) Current Altitude = 116.60 123.07 forcing to 126.07 Ground Trim Initial Theta: 0.9126 Trim successful JSBSim State Trim complete [...] Weight:1964 lbs. CG: 43.0, 0.0, 39.6 inches Flaps: Up Gear: Down Speed:0 KCAS Mach: 0.00 Altitude: 387 ft. AGL Altitude: 5 ft. ^^^ Angle of Attack: 0.00 deg Pitch Angle: 0.89 deg Flight Path Angle: 0.00 deg Climb Rate:-0 ft/min Normal Load Factor: 1.00 g's Pitch Rate: 0.00 deg/s Heading: 295 deg true Sideslip: 0.00 deg Bank Angle: -0.00 deg Elevator: 0.00 deg Left Aileron: 0.00 deg Rudder: -0.00 deg Throttle: 0.00% Wind Components: 0.00 kts head wind, 0.00 kts cross wind Ground Speed:0 knots , Ground Track: 0 deg true ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
