Re: [Flightgear-devel] nav.dat.gz fields
Chris Metzler wrote: Yeah, I had fetched some VORTAC images off the web and had started to make a model for it in Blender when suddenly one appeared in the Models directory (and at KSFO). It could use some texturing though, and at some point it might be cool to have two flavors of these things -- when they're at airports, and when they're not -- so that the ones at airports can have e.g. checkerboard textures. Another thing I'd like to do at some point . . . Well, once they're all placed any updates to the model in the base package will affect all of them, so texturing them will just improve the scenery as a whole. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] nav.dat.gz fields
On Sat, 25 Sep 2004 00:27:47 +0100 Jon Stockill <[EMAIL PROTECTED]> wrote: > >> Can you elaborate on what this means? Putting models that look like >> VORs at all the VOR locations, etc? > > Yes. > > Curt was talking about including it in the next distribution of the > scenery anyway, but the script I bodged together this week, and the > Objects/Terrain split of the scenery makes it possible to create an > add-on package which just places all the objects in the right place. Cool. I've been thinking about pursuing this for quite a while, but hadn't found time. I'm glad you're doing this. > Curt was talking about including it in the next distribution of the > scenery anyway, but the script I bodged together this week, and the > Objects/Terrain split of the scenery makes it possible to create an > add-on package which just places all the objects in the right place. > > There are already models for VOR/DME, TACAN, and ILS aerials in the > Models directory of the base package. Yeah, I had fetched some VORTAC images off the web and had started to make a model for it in Blender when suddenly one appeared in the Models directory (and at KSFO). It could use some texturing though, and at some point it might be cool to have two flavors of these things -- when they're at airports, and when they're not -- so that the ones at airports can have e.g. checkerboard textures. Another thing I'd like to do at some point . . . -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 pgp0DxZWyGjbg.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] nav.dat.gz fields
Chris Metzler wrote: On Fri, 24 Sep 2004 20:28:30 +0100 Jon Stockill <[EMAIL PROTECTED]> wrote: Does anyone have a list of the field specs for nav.dat.gz? http://www.x-plane.org/users/robinp/AptNavFAQ.htm#nav.dat I'm considering creating an Objects tree to add them to the scenery, the main field of interest is the first which I assume is the beacon type, but while some are obvious, others aren't - it'd be nice to use the right model for each one, rather that just a generic one. Can you elaborate on what this means? Putting models that look like VORs at all the VOR locations, etc? Yes. Curt was talking about including it in the next distribution of the scenery anyway, but the script I bodged together this week, and the Objects/Terrain split of the scenery makes it possible to create an add-on package which just places all the objects in the right place. There are already models for VOR/DME, TACAN, and ILS aerials in the Models directory of the base package. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] nav.dat.gz fields
On Fri, 24 Sep 2004 20:28:30 +0100 Jon Stockill <[EMAIL PROTECTED]> wrote: > > Does anyone have a list of the field specs for nav.dat.gz? http://www.x-plane.org/users/robinp/AptNavFAQ.htm#nav.dat > I'm considering creating an Objects tree to add them to the scenery, the > > main field of interest is the first which I assume is the beacon type, > but while some are obvious, others aren't - it'd be nice to use the > right model for each one, rather that just a generic one. Can you elaborate on what this means? Putting models that look like VORs at all the VOR locations, etc? -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 pgpSR4qIiGI7T.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
