RE: [Flightgear-devel] Runway distance remaining signs +placementscript done.
Would adding in ILS/glidescope aerials (where they exist; that's easily checkable off Robin's database) count as too much clutter? Giles Robertson -Original Message- From: Gene Buckle [mailto:[EMAIL PROTECTED] Sent: 08 September 2004 22:31 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Runway distance remaining signs +placementscript done. life, we should aim to include them in FlightGear. First, however, we need to start toning things down a bit. I take it this means no FOD sweeping gnomes? Drat. g. ___ 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
Re: [Flightgear-devel] Runway distance remaining signs +placementscript done.
On Thu, 9 Sep 2004 08:14:33 +0100, Giles Robertson [EMAIL PROTECTED] wrote: Would adding in ILS/glidescope aerials (where they exist; that's easily checkable off Robin's database) count as too much clutter? On the contrary, that would add realism to the airports. The risk right now is overequipping the airports with stuff so that even the smallest paved strip looks like a mini KLAX. Small airports typically have one or two runways, sometimes paved. When the runways are under 4,000 ft (or so), there is only one windsock in the middle of each runway -- in fact, the airports often contrive to have only one windsock shared by all the runways. There might be a rotating beacon, but it will not be on a fancy tower right beside the runway. Taxiway signs are a toss-up -- sometimes you'll see them (especially if the airport has instrument approaches) and sometimes you won't. There will almost always be some hangars beside the apron and some kind of FBO building, often with fuel pumps or fuel trucks parked beside it and an antenna on top or beside it for the UNICOM. If there is scheduled air carrier service, there will generally be a small public temrinal building beside the FBO (no jetways, of course). The runway markings are often simple and faded, and the taxiway markings are almost non-existant, especially at VFR-only airports. Busier airports (a small minority) have control towers, but many do not, even those with commercial commuter air service. Once there is a tower, you can count on taxiway signs (i.e. A, B, etc.). One thing we could add, at least for my part of the world, are animated groundhogs all over the airport -- also flocks of birds near the threshold. I also heard a story recently of cows eating the fabric covering of a tube-and-rag airplane. All the best, David -- http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runway distance remaining signs +placementscript done.
On Thu, 9 Sep 2004 06:40:53 -0400, David wrote in message [EMAIL PROTECTED]: One thing we could add, at least for my part of the world, are animated groundhogs all over the airport -- also flocks of birds near the threshold. I also heard a story recently of cows eating the fabric covering of a tube-and-rag airplane. ...that kinda realism might haven an impact on both the 3d model and the fdm's. ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runway distance remaining signs+placementscript done.
One thing we could add, at least for my part of the world, are animated groundhogs all over the airport -- also flocks of birds near the threshold. I also heard a story recently of cows eating the fabric covering of a tube-and-rag airplane. Should we use YASim or JSBSim for the bird FDM? The AIAircraft FDM will do it. A non-flapping bird, like an orbiting hawk will be easy (it's just like the KC-135). The flapping kind will take some animation work. As for flocking behavior, that's a whole 'nother thing. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runway distance remaining signs+placementscript done.
On Thu, 9 Sep 2004 22:25:02 -0400 Ampere K. Hardraade [EMAIL PROTECTED] wrote: Also, why can't we have our own airport database that extends Robin's? Presumably, we can; it's just a big job and nobody's stepped forward to do it. It'd certainly be nice to have another layer between Robin's database and our use of it. Corrections that fgfs users make to airports could become available more quickly than they are by passing them up to Robin and waiting for the next issuance of his database. And things like the complete disappearance of KSQL, the training airport used in some of FlightGear's new user docs, could be easily caught and corrected for. But it could end up being a lot of work. Also, there *are* occasional updates to Robin's data, and they seem to be fairly big -- lotsa stuff comes in from the X-Plane users, I guess. So one would have to take that new dataset, and then compare against local changes to the old dataset, and adjust accordingly. And how do you deal with cases where we have local changes to airport X, and airport X has changed in Robin's latest database, and the two changes disagree? Anyway. I think the short answer is that someone'd have to commit to doing it. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgpEWMZqOoGQt.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
