Jon Stockill wrote: > Josh Babcock wrote: > >> This glideslope looks a bit under the weather. It's at the southwest >> corner of KADW. >> http://jrbabcock.home.comcast.net/flightgear/fgfs-screen-002.jpg > > > The navaids were all placed at ground level - since the new scenery has > been created using new SRTM data, and the airport generator has changed > there will be problems like this - but obviously I couldn't do anything > about it before the scenery was released. > >> I also noticed that there are airport beacon models placed at the end of >> each runway just inside the inner markers. Are these supposed to be >> something else, and just got placed with the wrong models? > > > Not so much the wrong model. More the fact that we don't have a model > for an inner marker. I know what outer/middle markers look like - and > there's an appropriate model. We still need inner markers and localiser > models (at the moment the glidescope transmitter is used for localiser > positions). >
I can understand the glideslope model standing in for the localizer, but an airport beacon for the inner marker? Isn't that a little tall, a little in the way of passing air traffic, a little too visible from miles away because it has those nifty bright light animations? Oh well, I guess chaos is the price of progress:) (still, 3 beacons for one airport is a little confusing) Josh PS, I just sent a private e-mail referencing this, ignore the bits about removing these ... ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
