I noticed the VOR serving Granada (LEGR) airport in Spain is grossly misplaced in FSX, making it impossible to simulate VOR approaches. The real beacon is located roughly ten miles west of the airport, but in FSX it is placed in the same spot with the inner marker!Anyone know of a fix for this?EDIT: in fact I noticed the VOR is completely missing, there is only a DME set up with the inner marker in FSX

Fixing bad VORs in FSX is a problem. I think the only effective solution is to replace the default NVx file with a modified one. In this case, NVX05020.BGL. I don't have a lot of experience with it in a production environment, so I haven't tested it hard, but you can try the "EasyNavs" tool from here:http://pagesperso-orange.fr/hsors/navaids.htmlwhich will let you extract and edit the GDA vor, then save an xml file which you can compile using the BGLCOMP from the FSX sdk (requires deluxe or accel). The main problem with this approach to solving the problem, is that if different airports require their own mods to this same file, there is no easy way to coordinate the changes. It would be up to the user to keep track of his files.another potential problem is that MS typically creates a waypoint in the corresponding ATx file for the VORs. This becomes an issue when the VOR is part of the ATS route structure, as the V and J routes will pass through the waypoint, not the VOR as intended. The GDA waypoint doesn't have any associated routes, so it could be left alone or moved as well. I did a quick test without modifying the waypoint, and the flight planner seemed to work OK on a VOR to VOR plan.scott s..