I’ve done two flights since the patch dropped using a 152 to do VOR navigation. Both flights were in the southwest US
Both times, the VORs were off by about 2-4 degrees when I was navigating.
Has anyone else done any VOR only navigation since the patch?
I noticed the same thing this evening. It seemed off between CLL and IDU. Was in the 172.
You were using VORs to navigate in the 172, not GPS? Did you compare GPS to what the VOR was reading? I haven’t tested that yet. Were you in the glass cockpit 172 or the steam gauge?
I just loaded up little nav map and connected it to the sim so I could see my position. I had lines drawn off the VORs and compared my plane’s position on the line compared to what the NAV radio gauges were showing in the sim… definitely off by 2-3 degrees.
It also seems more pronounced the further you are from the VOR.
Steam gauges (with FltPlan Go as my moving map)
I’m starting to think that every VOR is offset by the same degree rotation. Doing a few more tests.
It’s broken. It’s also broken ILS approaches, it seems.
Yes. I had the same problem as well. I was flying VORs across Florida, Alabama into Louisiana. Every time I switched from one VOR to another, I found I was off by many degrees. The first one I thought it was a fluke or maybe I did something wrong. I only had one beer, so it wasn’t the alcohol. But after the 2nd, then 3rd and the 4th. I realized it wasn’t me, something was definitely wrong. Here’s the route I took. MAI V198 LOXLY V241 SJI V20 SLIDD
All of the VORs on this route didn’t line up. I’d fly each leg to the midway point, swap over to the new freq and course, but the needle would be all the way against the side of the gauge. On Air tracked my ugly course adjustments to get back on track. Something is broken with VORs.
My first flight was with the Cessna 208. The 2nd one was with the Carenado PA44. It did the same thing, just before it crashed to desktop about an 1 1/2 into my flight. 
Thanks for posting this, I thought I was going crazy.
I just several more flights and the VORs were all off.
Ugh. I imagine VOR navigation is broken for at least another two weeks…
2 weeks at the very least. Hopefully bug reports to Zendesk and in the bug forum can bring some attention to this.
This is the worst for playing NeoFly. I always start out in a 152 and use VORs extensively to navigate.
I haven’t had a chance to test this yet, but could it be related to Navigraph data?
When you say 2nd, 3rd, and 4th… did you mean VORs or beers?
I’ve been using Little Nav Map for several months and the VOR navigation and info on that has been spot-on until this latest patch.
I’m pretty sure its the sim and not the map source.
That could be… I’ll check that with and without Navigraph installed.
I too use VORs (and Victor airways) quite a bit to fly VFR in the 172 Steam Gauge A/C, so having accurate vectors is important.
Certainly worth a try. I’d love to test it but I’m stuck at work.
Me too at the moment, but plenty of time coming up the next few days…
It’ll be good to know your results, I’m also a Navigraph user and if VORs are broken that would be a pain.
Can you confirm if you’ve done flights on the same airways before the patch? Trying to work out whether it’s something that the patch has actually caused or whether it’s something you’ve only just noticed.
Secondly what charts are you using to fly the airway radials?
I’ll load a “known good” flight plan tonight created in Little Navmap.
I’ll try the flight both with and without Navigraph loaded up.
Will report results…
Does little nav map use the sim data or it’s own?
I’m suspecting this issue is due to a problem with the station declinations. If little nav map is using the in sim data to give you radials It shouldn’t create an issue. If it uses some other database then the problem may lay with the Msfs base nav data.
Be sure that little nav map is giving you radials rather than magnetic courses. In the USA these two values can differ significantly as the navigation aids haven’t been updated for years. As an example IDU shows 8E 1965 on the FAA’s eNASR site. The actual Magvar in the area is closer to 3E