Alright after going completely insane and redoing a significant amount of code I decided to take a look at the default GPS to make sure I wasn't a complete idiot. Turns out I'm not - at least I hope I'm not. Nearest Airspace will not work on the 500 either. I've been working on one of my FMC's and a GNS430 but the fact that I can't get nearet airspace to work is driving me nuts. I've set all the variables correctly etc, etc, and the fact that even the default gps isn't working suggests to me something else go astray. Perhaps one of my modules are bad? :Nail Biting:Any help would be appreciated. See attached image I took last night after nearly pulling my hair out. :help:p.s. some of these know emoticons are awesome!edit: attachment not working for whatever reason:

no problrms here.

It is entirely possible that your aircraft is located in one of the many areas of the world where there are no airspaces within the range of the GPS's criteria!I've been bitten on this before. I suggest that you move position to somewhere like Morristown, New Jersey to guarantee that there's plenty of airspaces to be displayed... :(

Sometimes it is the antivirus program, with VISTA even more, which kills the GPS.Btw. my shot was in the NWT, not much airspace there, but always a CENTER.Could you contact ATC? If so there must be some airspace.

Edited February 14, 201214 yr by phjvh

I was at KRUT on the ground. There is ATC there but just to be sure I went to KTEB and all I get is this:http://i18.photobucket.com/albums/b111/EV0317/Misc/1-2012-feb-14-006.jpg

Engjell,You could try an unaltered default plane and panel.Is the standard gps file not edited?Maybe something wrong with code.

Edited February 14, 201214 yr by phjvh

I tried that also Jan. The above is the FS9GPS not edited what so ever. Also tried the 295 on default aircraft and same thing.

New FS install??Rename the old one and try gps again.If ok, use modules and gps in old one after renaming.Some work....!Or build a new fs9.cfg.

Edited February 15, 201214 yr by phjvh

I'm really hoping that will not be the case. I will try messing with modules and stuff.

redoing a significant amount of code ... Perhaps one of my modules are bad? :(

What happens when you load the stock, default C172 and operate the gps_500? And in your custom aircraft/gauge, what is NearestAirspaceQuery set to?

Well I don't have the default C172 but things such as the Piper Cub and R22 I have and same exact thing I displayed above.Just to clarify, I do not have GPS_500 that I've modified. Everything above is the default stuff. I was just testing it to see why some code in another gauge I was using doesn't work I am getting the same results.