I could wait a couple of weeks to find out, but what's the fun in that :DI was watching a video recently posted here in these forums which showed a MD-11 landing in a sim where the HUGS changed modes to display the rwy overlay (i hope that's what it is called). For the NGX, I believe this functionality is there or will be there eventually. Where does this data come from? FSX Scenery or stored data from your navdata (I didn't see rwy data any where in the AIRAC files, but I could be wrong)Since each one will be using different scenery packages, the rwy placement, even though arguably should be same, is quiet unlikely. And stuff like landclasses, terrain mods, FSG UTX etc should be affecting them. I remember having read (or from Nick's video) that the terrain database uses data from the FSX Scenery so that's a relief, it must be matching where our ground is. EDIT: Disregard that last line, just saw a post by Ryan that the terrain database is custom.So, does the rwy overlay go where we see the rwy is in our scenery, or where it thinks the rwy should be :) And on that note, is there anything we should be watching out for that are potential conflicts between what is on the HUGS and what we actually see out our virtual windows?Blue Skies!!Charan

I think you don't need a degree in nuclear science to figure out how it works. The information about the runway doesn't come from any particulat database, it comes from the ILS, localizer. The placement of the localizer is enough for the HUGS software to draw those two lines on the side. The width of the localizer signal, its particular attributes which as we know can be runway-specific are no doubt processed by some fancy arithmetic behind the HUGS and you get this image.

Well that's what I thought, but wanted a clarification...I thought the elevation data and the width of the rwy would matter.Charan

You enter the runway elevation and length into the HGS panel (located on the center console).In the PMDG NGX, it displays very nicely, right where it should, and the collimation really comes in handy when you move your viewpoint around to access various switches in the VC.

Beautiful...thx for the clarification!!