RE: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Vivian Meazza
Drew wrote And a red one for -ve G. With a bit of texture. I never liked the 'red-out' in simulators...do pilot's really see red? I thought it was just called red-out because of excess blood to the brain. In any case, I thought of the same thing, myself (using this for GLOC).

Re: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Drew
I don't buy that argument. It's easier to grow with fgfs in small steps than to adapt everything after major releases. Following the cvslogs mailing list is usually enough, and there isn't such a fast progress anyway. Ok, I'm trying to take your advice, and get a later version of the source.

Re: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Frederic Bouvier
Drew a écrit : I don't buy that argument. It's easier to grow with fgfs in small steps than to adapt everything after major releases. Following the cvslogs mailing list is usually enough, and there isn't such a fast progress anyway. Ok, I'm trying to take your advice, and get a later version

Re: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Andy Ross
Drew wrote: I tried downloading the tar archive of the latest CVS flightear, but it doesn't compile with the latest release of SimGear. Is there an archive somewhere of a development SimGear version, or will I have to install a CVS client to get this code? I'm using Windows, and have never

Re: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Drew
This isn't wasted time. Learning to use CVS to synch to open source projects will be a skill you use for the rest of your life (or at least until everyone moves onto subversion or darcs or arch or whatever). Like it or not, limiting yourself to released versions of software kinda makes you

Re: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Drew
It is very easy with this tool : http://www.wincvs.org/download.html When using CVS, you have to keep SimGear, FlightGear and the data in sync, but it is just a few click with Wincvs. -Fred Thanks for the help. I think I'll put this on hold right now, and try it during the weekend when I

RE: [Flightgear-devel] Re: Blank screen implementation

2005-04-21 Thread Vivian Meazza
Frederic Bouvier wrote Drew a écrit : I don't buy that argument. It's easier to grow with fgfs in small steps than to adapt everything after major releases. Following the cvslogs mailing list is usually enough, and there isn't such a fast progress anyway. Ok, I'm trying to take

Re: [Flightgear-devel] Building airports

2005-04-21 Thread rgerlich
Hi, On Wed, Apr 20, 2005 at 08:51:32AM -0500, Corrubia, Stacie K wrote: Hi --- I am having a problem generating airports within TerraGear. I have been following the recipe from the TerraGear.README file and downloaded Robin Peel's database of airports and managed to create the basic.dat

[Flightgear-devel] Building Photo Scenery

2005-04-21 Thread rgerlich
Hi, I'm having the same problem as described in http://baron.flightgear.org/pipermail/terragear-devel/2004-September/001035.html I know the workaround of editing material.xml, but somehow I refuse to believe that this is the only way. I get the same messages about loading the right texture

[Flightgear-devel] YASim turbo/supercharger issues

2005-04-21 Thread Andy Ross
Vivian Meazza wrote: The attached diff models the output of a gear-driven supercharger I just now got a chance to sit down and puzzle this out. I see where it's going: instead of ignoring the RPM contribution to boost, it adds an extra factor that reduces the boost at lower RPMs. It works by

RE: [Flightgear-devel] YASim turbo/supercharger issues

2005-04-21 Thread Vivian Meazza
Andy Ross wrote: Vivian Meazza wrote: The attached diff models the output of a gear-driven supercharger I just now got a chance to sit down and puzzle this out. I see where it's going: instead of ignoring the RPM contribution to boost, it adds an extra factor that reduces the boost at

[Flightgear-devel] What happened to Flitetutor

2005-04-21 Thread Ampere K. Hardraade
I have been meaning to ask this for a while: Does anybody know what happened to the project? Whoever was working on it seems to have just diappeared. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org

Re: [Flightgear-devel] YASim turbo/supercharger issues

2005-04-21 Thread Andy Ross
Vivian Meazza wrote: I used the power form because it is easier to read, but if the other form produces a performance advantage, then of course we must use it. It's actually not so much about performance, really. Readability can mean different things. The problem is that when I see a

RE: [Flightgear-devel] YASim turbo/supercharger issues

2005-04-21 Thread Norman Vine
Andy Ross writes: Vivian Meazza wrote: I used the power form because it is easier to read, but if the other form produces a performance advantage, then of course we must use it. It's actually not so much about performance, really. Readability can mean different things. The problem

[Flightgear-devel] Another fgfs enabled rating!

2005-04-21 Thread Dave Perry
I passed my instrument rating oral and practical (check ride) this afternoon. Five hours including the oral and ride. Boy was I glad I had done many approaches with the turbulence turned up as all the approaches were in moderate turbulence today with 20 gust to 35 kts and wind shear. The

Re: [Flightgear-devel] Big Nasal Changes

2005-04-21 Thread Jim Wilson
From: Curtis L. Olson Frederic Bouvier wrote: I am not here to endorse Microsoft choices, but I see little point to use C syntax when C++ is available and is the language of choice for the overall FlightGear project. However, the link below should clarify Microsoft point of view :

Re: [Flightgear-devel] YASim turbo/supercharger issues

2005-04-21 Thread Arnt Karlsen
On Thu, 21 Apr 2005 19:46:10 -0400, Norman wrote in message [EMAIL PROTECTED]: Andy Ross writes: Whereas this one is just really obviously a polynomial, and I understand polynomials, they're simple and not scary at all: rpm_norm * (1.11 - rpm_norm * (0.15 * rpm_norm + 0.25))