Re: [Flightgear-devel] Re: Flightgear and lighting
Martin Spott wrote: On Wed, Feb 19, 2003 at 11:46:49PM +0100, Felix Kühling wrote: On Wed, 19 Feb 2003 23:06:33 +0100 Martin Spott [EMAIL PROTECTED] wrote: I just found out by accident how to get correct lightning in FlightGear with current DRI drivers _and_ HW-TCL: Just look straight out of the cockpit and bank the plane 120 degrees to the right (not to the left, this does not work). Quite 'usuable' lightning happens between 90 and 180 degrees. This effect is absolutely independent of the direction I look (fly) into. Actually I saw this effect before and reported it to dri-devel. IIRC I also found out that the direction in which you have to bank depends on the simulated time of day, or in other words, the direction of the light source. [...] I usually run FlightGear-tests at 11 am local time: --start-date-lat=2002:04:11:11:11:11 I believe this is a similar effect as Erik Hofman reported to have seen on his O2 - Erik ? Yes, but that was controllable because I did somethin wrong. BTW, could you try this patch? Erik --- /home/erik/src/CVS/fgfs/FlightGear/src/Objects/newmat.cxx Fri Nov 15 23:21:21 2002 +++ FlightGear/src/Objects/newmat.cxx Thu Feb 20 09:54:22 2003 @@ -397,7 +397,7 @@ texture_loaded = false; } textured-enable( GL_COLOR_MATERIAL ); -#if 0 +#if 1 textured-setColourMaterial( GL_AMBIENT_AND_DIFFUSE ); textured-setMaterial( GL_EMISSION, 0, 0, 0, 1 ); textured-setMaterial( GL_SPECULAR, 0, 0, 0, 1 );
[Flightgear-devel] FlightGear without Joystick
Hello, at least since 1.6.0 release (or earlier) PLIB appears not to build joystick support on Solaris (not on the two machines I use to compile miscallaneous stuff on). But FlightGear does not build with a PLIB without joystick support: /usr/local/src/FlightGear/src/Cockpit/built_in ~ g++ [...] -c -o FGMagRibbon.o [...] [...] In file included from ../panel.hxx:54, from FGMagRibbon.hxx:25, from FGMagRibbon.cxx:22: ../../../src/Input/input.hxx:31:21: plib/js.h: File not found In file included from ../panel.hxx:54, from FGMagRibbon.hxx:25, from FGMagRibbon.cxx:22: ../../../src/Input/input.hxx:262: `JS_MAX_AXES' was not declared in this scope ../../../src/Input/input.hxx:262: enumerator value for `MAX_JOYSTICK_AXES' not integer constant ../../../src/Input/input.hxx:308: syntax error before `*' token make[3]: *** [FGMagRibbon.o] Error 1 Do you tend to wait until PLIB has joystick support on Solaris or might it be of interest to let 'configure' test for joystick support and set the dependencies in FlightGear accordingly ? 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
[Flightgear-devel] CVS how-to
Title: Message Hi guys ... I've actually got some free time to contribute ... is there a tutorial on CVS anywhere I have basically no knowledge about it ..(*blush* been coding for years without CVS) Kind Regards Danie Heath Software Integrator RisC Com cc +27 12 654 5100 083 412 6904 [EMAIL PROTECTED] www.risccom.co.za
Re: [Flightgear-devel] FlightGear without Joystick
Martin Spott wrote: Hello, at least since 1.6.0 release (or earlier) PLIB appears not to build joystick support on Solaris (not on the two machines I use to compile miscallaneous stuff on). But FlightGear does not build with a PLIB without joystick support: Do you tend to wait until PLIB has joystick support on Solaris or might it be of interest to let 'configure' test for joystick support and set the dependencies in FlightGear accordingly ? This should be fixed in the CVS version of plib. I've added a jsNone.cxx file with empty functions for IRIX, Solaris and HP-UX. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS how-to
Danie Heath wrote: Hi guys ... I've actually got some free time to contribute ... is there a tutorial on CVS anywhere I have basically no knowledge about it ..(*blush* been coding for years without CVS) This might be a good start: https://sourceforge.net/docman/display_doc.php?docid=14033group_id=1 Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Flightgear and lighting
BTW, could you try this patch? You know I'll try _every_ patch you want me to do so ;-) Unfortunately this one does not do the trick, 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] Re: Flightgear and lighting
Martin Spott wrote: BTW, could you try this patch? You know I'll try _every_ patch you want me to do so ;-) Unfortunately this one does not do the trick, Okay, I'm pretty sure now it's OpenGL shininess related, but I can't think of a reason why. :-( Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear without Joystick
This should be fixed in the CVS version of plib. I've added a jsNone.cxx file with empty functions for IRIX, Solaris and HP-UX. I tried yesterday without success: /usr/local/src/plib/src/js ~ g++ [...] -c -o js.o js.cxx In file included from js.cxx:23: js.h:40:32: machine/joystick.h: No such file or directory In file included from js.cxx:23: js.h:131: 'joystick' is used as a type, but is not defined as a type. make[2]: *** [js.o] Error 1 and today PLIB CVS did not change, 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] FlightGear without Joystick
Martin Spott wrote: This should be fixed in the CVS version of plib. I've added a jsNone.cxx file with empty functions for IRIX, Solaris and HP-UX. I tried yesterday without success: /usr/local/src/plib/src/js ~ g++ [...] -c -o js.o js.cxx In file included from js.cxx:23: js.h:40:32: machine/joystick.h: No such file or directory In file included from js.cxx:23: js.h:131: 'joystick' is used as a type, but is not defined as a type. make[2]: *** [js.o] Error 1 and today PLIB CVS did not change, It looks like a platform detection problem. Somehow your compiler identifies itself as being a BSD platform. Instead it should support the SOLARIS definition. If you know this shouldn't be the case, add the correct string to plib/src/util/ul.h. After that everything should compiler again. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] airspeed and headwind
Curtis L. Olson writes: I guess I don't really know now that I think about it, but I always thought of windshear more as a singular event as you pass from one layer of wind to another rather than continuous high turbulence. If I'm wrong just ignore the rest of this. Wind shear is any vertical or horizontal change in wind that is fast enough to cause a change in airspeed. Passing through a front or into/out of an inversion are two possible causes. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear without Joystick
Somehow your compiler identifies itself as being a BSD platform. Instead it should support the SOLARIS definition. I think it's a different issue. Taken from current 'README': PORTABILITY and DEPENDANCIES: [...] JS -- Currently Linux/Windows/BSD only. plib-1.4.2 detects the presence of a joystick and decides not to build 'libplibjs': [ configure ] checking joystick.h usability... no checking joystick.h presence... no checking for joystick.h... no checking linux/joystick.h usability... no checking linux/joystick.h presence... no checking for linux/joystick.h... no [ make ] make[2]: Entering directory /usr/local/src/plib-1.4.2/src/js' make[2]: Nothing to be done for ll'. make[2]: Leaving directory /usr/local/src/plib-1.4.2/src/js' So would might be worthwhile to allow building FlightGear _without_ joystick support in PLIB !? 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] FlightGear without Joystick
Martin Spott wrote: Somehow your compiler identifies itself as being a BSD platform. Instead it should support the SOLARIS definition. I think it's a different issue. Taken from current 'README': PORTABILITY and DEPENDANCIES: [...] JS -- Currently Linux/Windows/BSD only. from the README in plib/src/js: ...and a bunch of OS-specific code: jsLinux.cxx jsLinuxOld.cxx jsWindows.cxx jsBSD.cxx jsMacOS.cxx ...for OS's (eg IRIX and SOLARIS) without standard joystick functionality, we add: jsNone.cxx ...which safely returns error status with no buttons or axes provided. believe me, it is the SOLARIS variable in plib/src/util/ul.h You might want to try this path: --- /home/erik/src/CVS/fgfs/plib/src/util/ul.h Sat Jan 4 11:01:57 2003 +++ plib/src/util/ul.h Thu Feb 20 13:35:45 2003 @@ -80,7 +80,7 @@ #define UL_IRIX 1 -#elif defined(SOLARIS) +#elif defined(SOLARIS) || defined (sun) #define UL_SOLARIS 1 Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re : More on CVS
Hi all, I have some more questions on CVS. If I have the version 0.9.0 base package, and I run : cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase it seems it downloads the whole base package through CVS. Is there a way I can update only the files that have changed or are new to the repository. Or will it by default download the whole base package the first time I update the base package via CVS Kind Regards Danie Heath Software Integrator RisC Com cc [EMAIL PROTECTED] http://www.risccom.co.za ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re : More on CVS
Hi all, I have some more questions on CVS. If I have the version 0.9.0 base package, and I run : cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase it seems it downloads the whole base package through CVS. Is there a way I can update only the files that have changed or are new to the repository. Or will it by default download the whole base package the first time I update the base package via CVS Kind Regards Danie Heath Software Integrator RisC Com cc [EMAIL PROTECTED] http://www.risccom.co.za ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] airspeed and headwind
Tony Peden writes: Huh!?! Except at high power settings and low speed in a twin, engine failure should not cause a big upset. Even then, if you're fairly quick to get on the rudder, it's generally very controllable (or should be, anyway...) A friend of mine has a Frasca sim (cockpit enclosure, full working panel, etc.) It has a twin mode and I tried repeatedly to survive an engine out on take off in one of their light twins (forget which one, maybe a baron?) and had no luck; I hit hard every time. I don't know about a real pilot in a real plane, but this sim took a lot more coaxing than I had in me to even maintain altitude with an engine out; if you let your airspeed drop below blue line[1] trying to hold altitude, it get's real ugly real fast. [1] Blue line is the speed below which the rudder cannot overcome the torque effects of a single engine and you can no longer have directional control. I would guess that *many* designs (especially commercial jets) would be much more survivable in those circumstances. And they'd have the added advantage of having a real pilot at the controls. :-) 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] Re : More on CVS
Danie Heath wrote: Hi all, I have some more questions on CVS. If I have the version 0.9.0 base package, and I run : cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase it seems it downloads the whole base package through CVS. Is there a way I can update only the files that have changed or are new to the repository. Or will it by default download the whole base package the first time I update the base package via CVS I always use: cvs -d:pserver:[EMAIL PROTECTED]:/home/cvsroot up -Pd fgfsbase after the first install. This explicitly tells cvs to _update_ the tree rather than copying. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear without Joystick
Martin, Our assumption has been that plib supports joysticks on every platform, or hides the fact that it doesn't from the calling application. Apparently neither is the case, at least for solaris. :-( Question, if you hack up the FG code to yank out all joystick support, can you then get to the end and get a working FG build? In the past there have been strange missing symbols that couldn't be resolved which looked a lot like a compiler bug somewhere. Regards, Curt. Martin Spott writes: Hello, at least since 1.6.0 release (or earlier) PLIB appears not to build joystick support on Solaris (not on the two machines I use to compile miscallaneous stuff on). But FlightGear does not build with a PLIB without joystick support: /usr/local/src/FlightGear/src/Cockpit/built_in ~ g++ [...] -c -o FGMagRibbon.o [...] [...] In file included from ../panel.hxx:54, from FGMagRibbon.hxx:25, from FGMagRibbon.cxx:22: ../../../src/Input/input.hxx:31:21: plib/js.h: File not found In file included from ../panel.hxx:54, from FGMagRibbon.hxx:25, from FGMagRibbon.cxx:22: ../../../src/Input/input.hxx:262: `JS_MAX_AXES' was not declared in this scope ../../../src/Input/input.hxx:262: enumerator value for `MAX_JOYSTICK_AXES' not integer constant ../../../src/Input/input.hxx:308: syntax error before `*' token make[3]: *** [FGMagRibbon.o] Error 1 Do you tend to wait until PLIB has joystick support on Solaris or might it be of interest to let 'configure' test for joystick support and set the dependencies in FlightGear accordingly ? 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 -- 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] Re : More on CVS
Danie, it seems it downloads the whole base package through CVS. Is there a way I can update only the files that have changed or are new to the repository. Or will it by default download the whole base package the This works the same way as described here for the code repository http://www.flightgear.org/cvsResources/anoncvs.html ? Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] 3D models
Hi, I was wondering, do any of you (using the latest plib CVS version) still see the A-10 aircraft model? At first I tought this was a problem with the 3ds loader, but as it happens, I can see the seahawk (which is also a 3ds model) model without any problem? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D models
Erik Hofman [EMAIL PROTECTED] wrote: I was wondering, do any of you (using the latest plib CVS version) still see the A-10 aircraft model? Yes, I do - but only on Linux. On IRIX I never saw any aircraft designed by Lee Elliot, neither TSR.2, A-10 not B-52 or Seahawk. At first I tought this was a problem with the 3ds loader, but as it happens, I can see the seahawk (which is also a 3ds model) model without any problem? The Seahawk does have textures, A-10 does not, 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] FlightGear without Joystick
Martin Spott writes: Curtis L. Olson [EMAIL PROTECTED] wrote: Question, if you hack up the FG code to yank out all joystick support, can you then get to the end and get a working FG build? I'll try my best as time permits. I spent quite a couple of hours compiling and testing FlightGear, DRI, FreeTDS and other OpenSource stuff these days. I assume I somehow should get back to working a bit more for my income really soon ;-) Now, now ... don't be distracted by those hunger pains, and those angry people banging on your door wanting to evict you for not paying rent. :-) 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] 3D models
Martin Spott wrote: Erik Hofman [EMAIL PROTECTED] wrote: The Seahawk does have textures, A-10 does not, I did see (a white) A-10 in the past ... Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Re : More on CVS
From: Danie Heath [mailto:[EMAIL PROTECTED]] Sent: 20 February 2003 2:26 pm To: [EMAIL PROTECTED] Subject: [Flightgear-devel] Re : More on CVS Hi all, I have some more questions on CVS. If I have the version 0.9.0 base package, and I run : cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase it seems it downloads the whole base package through CVS. Is there a way I can update only the files that have changed or are new to the repository. Or will it by default download the whole base package the first time I update the base package via CVS You cannot update a release copy of the base package using CVs (unfortunately) since it is missing all the CVS control files. You can however (I think) update a CVS snapshot if you have one. To start using CVS, you have to check out a new local copy (using the command in your email above), hoever, this does not have to complete in one operation. Once it has created the CVS directory in the root of the local copy, you can use the regular update command cvs -z3 up -dP to carry on getting more. I used this technique to get the base package in 10-20 minute chunks on a 56K modem over a couple of weeks. Richard ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] airspeed and headwind
Curtis L. Olson writes: If things turn u [1] Blue line is the speed below which the rudder cannot overcome the torque effects of a single engine and you can no longer have directional control. I think that blue line is a bit higher than Vmc -- it's a speed where a typical pilot (rather than a highly-skilled test pilot under ideal conditions) might actually be able to control the plane. It's not mainly torque effects but the yawing moment that you have to worry about. Unless the plane is a centreline thrust, the good engine will be off to one side pulling that side forward and starting a yaw-induced roll (and if the bad one is not feathered, it will be dragging the far side back even further). In fact, if things start to go bad, the last-ditch solution is to cut the good engine as well -- if you do that in time, you can at least try a forced landing. A Navajo pilot over Winnipeg did that a couple of years ago in an apparently unsurvivable situation (low-altitude engine failure over a dense urban area) and managed to land on a busy city street with no fatalities, though some passengers suffered serious injuries including leg amputations). The plane somehow avoided killing anyone on the ground as well. That's actually the time you'd rather be in a single, because even a light twin is heavier and has a higher stall speed -- that means that you might have many times as much energy to dissipate in a forced landing. I would guess that *many* designs (especially commercial jets) would be much more survivable in those circumstances. And they'd have the added advantage of having a real pilot at the controls. :-) ... who, to keep their jobs, have to demonstrate those skills in a full-motion simulator twice a year with a DFE watching every move. I've noticed that many private multiengine pilots do recurrent training every six months as well (FlightSafety Intl. seems the place of choice) -- it's a big change from flying a single, and you have to be very, very current if you want to stay alive. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: More on CVS
* Richard Bytheway -- Thursday 20 February 2003 16:13: Once it has created the CVS directory in the root of the local copy, you can use the regular update command cvs -z3 up -dP to carry on getting more. You do not really use cvs -z3 up -dP every time, do you? cvs has a configuration file ~/.cvsrc where you can put your favorite settings for each of the cvs commands. I'm using this as my ~/.cvsrc: cvs -z4 -q diff -up update -dP checkout -P rdiff -u In other words: every cvs command uses -z4 and -q, while the update command (up) =additionally= uses -dP. I can still override these settings for a specific repository, but it never turned out to be necessary. So, the regular update command should IMHO be cvs up. m. :-) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] airspeed and headwind
David Megginson [EMAIL PROTECTED] said: It's not mainly torque effects but the yawing moment that you have to worry about. Unless the plane is a centreline thrust, the good engine will be off to one side pulling that side forward and starting a yaw-induced roll (and if the bad one is not feathered, it will be dragging the far side back even further). In fact, if things start to go bad, the last-ditch solution is to cut the good engine as well -- if you do that in time, you can at least try a forced landing. Keep in mind I don't know how to fly, so get out your grains of salt :-) It seems to me I read somewhere that if you have any altitude at all (1000ft) the thing to do is move all the levers up to full throttle. Cut the throttle on the engine you think is out, because with most aircraft you don't want to risk feathering your good engine. Then if things are still yawing bad (meaning you cut the throttle on the engine that is really dead), feather immediately. Try to do the whole procedure in a few seconds, but don't skip the safeguard step. I'll have to ask my boss what he experienced last year when losing an engine on his Grumman Cougar. The thing I remember most about his story was the less than friendly phone call he got from the FAA because he decided to continue and fly it home on one engine (about 350 miles). Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] airspeed and headwind
Jim Wilson writes: Keep in mind I don't know how to fly, so get out your grains of salt :-) It seems to me I read somewhere that if you have any altitude at all (1000ft) the thing to do is move all the levers up to full throttle. Cut the throttle on the engine you think is out, because with most aircraft you don't want to risk feathering your good engine. Then if things are still yawing bad (meaning you cut the throttle on the engine that is really dead), feather immediately. Try to do the whole procedure in a few seconds, but don't skip the safeguard step. I'll have to ask my boss what he experienced last year when losing an engine on his Grumman Cougar. The thing I remember most about his story was the less than friendly phone call he got from the FAA because he decided to continue and fly it home on one engine (about 350 miles). I have a friend who flies King Air's ... he said one potential failure mode is in the governor that controls prop rpm. If this fails, it's possible to over torque that engine which will make it appear as if the other engine is the one with the failure. If you act too quickly, you can power off/feather your good engine and have a real problem. He spoke of this like it was one of those things that you really hope never happens to you, because it is the sort of thing that can get even the really good pilots in big trouble. 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
[Flightgear-devel] Navaids and fixes from DAFIF
I'm currently checking new files Navaids/default.nav.gz and Navaids/default.fix.gz into the base package. These are generated directly from DAFIF files (I've checked in my Perl scripts as well), so they will be easy to keep up to date. The navaids file is a moderate improvement, adding a couple of thousand additional navaids around the world; the fixes file is a major improvement, increasing the number of fixes from 16,000 to 71,000 -- that will be a good foundation for adding GPS support to FlightGear in the future. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Navaids and fixes from DAFIF
David, In the spirit of keeping code separate from data, would it make sense to put the scripts somewhere in the source tree? Maybe scripts/ or src/Navaids/? Curt. David Megginson writes: I'm currently checking new files Navaids/default.nav.gz and Navaids/default.fix.gz into the base package. These are generated directly from DAFIF files (I've checked in my Perl scripts as well), so they will be easy to keep up to date. The navaids file is a moderate improvement, adding a couple of thousand additional navaids around the world; the fixes file is a major improvement, increasing the number of fixes from 16,000 to 71,000 -- that will be a good foundation for adding GPS support to FlightGear in the future. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ 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] Navaids and fixes from DAFIF
Curtis L. Olson writes: David, In the spirit of keeping code separate from data, would it make sense to put the scripts somewhere in the source tree? Maybe scripts/ or src/Navaids/? I should also say this really cool to be able to incorporate this data directly. In terms of fixes though 72000 is an insane amount. For anyone wanting to actaully draw these on a map, there is going to have to be some sort of data reduction strategy. Does the DAFIFT file give any hints or ranking of which are the more important or more widely used fixes? There's about 15 fixes right on or very near the KSFO airport property. 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] airspeed and headwind
On Thu, 2003-02-20 at 06:34, Curtis L. Olson wrote: Tony Peden writes: Huh!?! Except at high power settings and low speed in a twin, engine failure should not cause a big upset. Even then, if you're fairly quick to get on the rudder, it's generally very controllable (or should be, anyway...) A friend of mine has a Frasca sim (cockpit enclosure, full working panel, etc.) It has a twin mode and I tried repeatedly to survive an engine out on take off in one of their light twins (forget which one, maybe a baron?) and had no luck; I hit hard every time. I don't know about a real pilot in a real plane, but this sim took a lot more coaxing than I had in me to even maintain altitude with an engine out; if you let your airspeed drop below blue line[1] trying to hold altitude, it get's real ugly real fast. [1] Blue line is the speed below which the rudder cannot overcome the torque effects of a single engine and you can no longer have directional control. I would guess that *many* designs (especially commercial jets) would be much more survivable in those circumstances. And they'd have the added advantage of having a real pilot at the controls. :-) Jet's make it easier, no prop to consider. I'd guess the Part 23 ( and Part 135? ) handling qualities regs are/were easier than those for Part 25. Curt. -- Tony Peden [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Navaids and fixes from DAFIF
Curtis L. Olson writes: In the spirit of keeping code separate from data, would it make sense to put the scripts somewhere in the source tree? Maybe scripts/ or src/Navaids/? Sure -- I just dumped them there for now. Someone suggested earlier that we should modify FlightGear to read the DAFIFT format directly, and I think that's a good idea; at that point, the scripts would be obsolete. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Navaids and fixes from DAFIF
Curtis L. Olson writes: I should also say this really cool to be able to incorporate this data directly. In terms of fixes though 72000 is an insane amount. For anyone wanting to actaully draw these on a map, there is going to have to be some sort of data reduction strategy. Does the DAFIFT file give any hints or ranking of which are the more important or more widely used fixes? There's about 15 fixes right on or very near the KSFO airport property. Different intersections and fixes server different purposes: the ones around KSFO are probably parts of various instrument approaches, and we would need most or all of them to simulate ATC or an approach-certified GPS. Just around Ottawa TCA, we have quite a few intersections. Here are the ones you'll find on an enroute chart, serving both for navigation through the Ottawa area and for transition from enroute to approach: LORKA EBNYR ASHTN AGLIN THURO AVVON REEDO ULAMO LANRK CYRIL HUXLY FANOL But those don't tell nearly the whole story. Most instrument approaches add more waypoints that don't appear on the enroute charts. For example, the ILS or NDB 32 approach adds the TEXEN GPS fix, while the ILS or NDB 07 approach adds the VISOL GPS fix. And so on. The DAFIF contains quite a few additional fields, including a usage code -- you could use that as a filter for generating different kinds of maps. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Modesto Two Arrival
Here's a STAR into KSFO from the west, with lots of waypoints for anyone who'd like to try out the new options and the new fix database: http://edj.net/cgi-bin/echoplate.pl/echoplate.pl?Arrivals/MODESTO%20TWO.GIF All of the five-letter names like FAITH and GROAN represent waypoints that you can specify to FlightGear using the --fix option. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Navaids and fixes from DAFIF
David Megginson writes: Sure -- I just dumped them there for now. Someone suggested earlier that we should modify FlightGear to read the DAFIFT format directly, and I think that's a good idea; at that point, the scripts would be obsolete. I think this is a great idea ... that makes it easier for people to keep their data current even if they are running a fixed release (ie. not cvs.) The one area to be careful of is airports, runways, and taxiways of course. I'd hate to lose a lot of the hand edited data from X-Plane for airports that aren't available in DAFIFT (and for all the taxiways.) The X-Plane taxiway definition approach leaves much to be desired, but it's a heck of a lot better than nothing. 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] Navaids and fixes from DAFIF
David Megginson writes: Different intersections and fixes server different purposes: the ones around KSFO are probably parts of various instrument approaches, and we would need most or all of them to simulate ATC or an approach-certified GPS. Just around Ottawa TCA, we have quite a few intersections. Here are the ones you'll find on an enroute chart, serving both for navigation through the Ottawa area and for transition from enroute to approach: LORKA EBNYR ASHTN AGLIN THURO AVVON REEDO ULAMO LANRK CYRIL HUXLY FANOL But those don't tell nearly the whole story. Most instrument approaches add more waypoints that don't appear on the enroute charts. For example, the ILS or NDB 32 approach adds the TEXEN GPS fix, while the ILS or NDB 07 approach adds the VISOL GPS fix. And so on. The DAFIF contains quite a few additional fields, including a usage code -- you could use that as a filter for generating different kinds of maps. That might be the thing to do. Fixes are something I'd have no hesitation to switching to DAFIFT format. 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
[Flightgear-devel] OT - the physics of the jiggle
This could have application to aeroelastic effects? http://www.gamespy.com/fargo/january02/jiggle/ Dave Culp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Two recent papers (Aug 2002 and Jan 2003)
As some people know, we're using FlightGear in our Smart Icing System research. Two recent papers (Aug 2002 and Jan 2003) on the subject have been posted here: http://www.aae.uiuc.edu/m-selig/apasim.html Regards, Michael ** Prof. Michael S. Selig Dept. of Aero/Astro Engineering University of Illinois at Urbana-Champaign 306 Talbot Laboratory 104 South Wright Street Urbana, IL 61801-2935 (217) 244-5757 (o), (509) 691-1373 (fax) mailto:[EMAIL PROTECTED] http://www.uiuc.edu/ph/www/m-selig http://www.uiuc.edu/ph/www/m-selig/faq.html (FAQ) ** ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] many external models w/ GNU GPL permission
In the last few months, several people have given FlightGear permission to use their external models under the GNU GPL (i.e. they can ultimately be included w/ the fgfs base package). For those interested, I've collected these and posted them here: http://www.aae.uiuc.edu/m-selig/apasim/fgfs-models.html Caveats: Most of the airplanes still need corresponding flight models. Also, some of aircraft have issues w/ the textures (e.g. they are located in the wrong place and some textures are mirror images ... interesting effects). The images shown are those rendered w/ fgfs. This collection builds on a nice group put together by Wolfram Kuss. One key difference, however, is that the models I've posted have been released under the GNU GPL while Wolfram's are not. Wolfram's site is here: http://home.t-online.de/home/Wolfram.Kuss/ Regards, Michael ** Prof. Michael S. Selig Dept. of Aero/Astro Engineering University of Illinois at Urbana-Champaign 306 Talbot Laboratory 104 South Wright Street Urbana, IL 61801-2935 (217) 244-5757 (o), (509) 691-1373 (fax) mailto:[EMAIL PROTECTED] http://www.uiuc.edu/ph/www/m-selig http://www.uiuc.edu/ph/www/m-selig/faq.html (FAQ) ** ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] models under gnu/gpl
Michael I was interested in finding one for the twin-otter, just curious how you went about finding these? Paul ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] models under gnu/gpl
At 2/21/03, Paul D. wrote: Michael I was interested in finding one for the twin-otter, just curious how you went about finding these? A Twin Otter model is here: http://home.t-online.de/home/Wolfram.Kuss/FGFS1/FGFS1.htm This is the one we use w/ our icing work. To find potential GNU GPL models, I started by going to www.flightsim.com. I then searched for things like public domain and MSFS 2000. That gave me several leads. I contacted the authors of ones that stood out and asked if they would release them under GNU GPL. Those that said yes (~~70% did) let all their models go under GNU GPL. The basic models w/o animation work fine (what's seen on the web page), but sometimes the flaps are down or something like that. Trying to get these properly animated will be an exercise from what I've read on the fgfs mailing lists. Ref http://www.aae.uiuc.edu/m-selig/apasim/fgfs-models.html Regards, Michael ** Prof. Michael S. Selig Dept. of Aero/Astro Engineering University of Illinois at Urbana-Champaign 306 Talbot Laboratory 104 South Wright Street Urbana, IL 61801-2935 (217) 244-5757 (o), (509) 691-1373 (fax) mailto:[EMAIL PROTECTED] http://www.uiuc.edu/ph/www/m-selig http://www.uiuc.edu/ph/www/m-selig/faq.html (FAQ) ** ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] models under gnu/gpl
Michael Ok thanks, I have been using the one form wolframs page, but was wondering about the gpl deal. Also thanks for the links, I think a t38 model is in the works at flight gear, as well as f16. Paul ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
