Vor's not working with analog gauges?

Discussion Hub General Discussion
1

So i wanted to fly a vor to vor route with the new ju-25 but couldn’t get it to work somehow.

So i jumped in the c152, but no succes either. I can remember i did track vor’s in the 152 some time ago.

Tried the c172 (g1000) and it works without problems. Freq dialed in and cdi responded immeadiatly and found my course without problems. Dme was functioning fine too.

So i stepped into the 172 analog cockpit. Tried the same but again with no succes. Altough i can hear the ident, the needles won’t move and there’s no to/from indication. Cdi source is set to nav and freq is not on standby. I tried flying towards the vor at different altitudes and turn the obs in the right direction. Ofcourse all electrical power is turned on.

Adf seems to be working just fine in the 152…

Is there something wrong with the analog planes? Or am i just stupid and missed something obvious? And when a vor is working in the g1000 it should work in analog aswell right? Since the g1000 is set to vloc and cdi set to nav1. Should be the same principle or not?

Thanks

2

It should be the same, correct. Confirm you’ve tried each time with the same VOR?

3

Yes, and multiple vor’s aswel!

4

Community folder empty/renamed?

5

Yes tried that but didn’t work unfortunately. I will try some different vor’s and report back. If i’m unable to get it working with the same vor g1000 vs analog i’ll post a screenshot

6

Just tested LNZ VOR 116.6 and LOWL ILS 26 109.3. Cold & dark.
Works with the 152 and the analog 172.

Starting in flight works as well except for comm and nav 2 on the 152 which are inop.

7

I had this issue about a month ago. Just by chance I re-activated my Navigraph subscription and updated MSFS. This solved the problem so it could be some kind of Airac bug or something related to navaids. No idea how to fix without this except maybe a full reinstall or if there is an option to reinstall the nav database from the Content Manager.

8

No navigraph here.

9

Yeah i got it to work now! Apparently some vor’s in the netherlands aren’t working. The first vor i tried that worked with the g1000 now also works with the 152. So probably a mistake by me somehow.

All the vor’s i tried where vor/dme. But the ones i tried and didn’t work, did show/sound the vor identifier. (pam 117.800 f.e.) Somehow the analog showed distance aswell but the G1000 didn’t. As you can see in these screenshots:

analog
analog2560×1440 172 KB

G1000
G10002560×1440 170 KB

Note that in the 152 the identifier code was also heard.

Edit: I see now that i marked the gps distance

10

PAM has been decommisioned.
Not sure why you can hear the VOR ID.

1 Like
11

Any idea how to find out then wich vor would actually still work? Would make flight planning in the world map alot easier :sweat_smile:

Btw i can find no info about the Vor being decommisioned

12

IRL you would check the relevant NOTAMS as a part of the preflight planning, but this doesn’t explain the ID.

13

Sure, but this is not possible inside msfs. To much hassle for a quick flight imo. I guess the only way is just to gamble then. Might want to avoid the netherlands if you want to rely purely on VOR’s lol.

Thanks for your help though! Atleast now i know where to fly the JU-25

1 Like
14

Here’s a video from a flight i (planned) to do. I picked 5 Vor’s across the netherlands to fly from EHRD to EHGG. (i understand 1 or 2 would be sufficient but just for fun)

The vor’s where 111.200 / 113.950 / 113.900 / 114.700 / 112.400

I read an article this morning about most of the Vor beacons in the Neterlands needed to be shutdown before 2020. So i guess they succeeded.

But both dme and identifiers are still in the running (atleast in msfs). In the video i tried all of the above and all of them showed distance and Ident (sound on)

Only the EEL Vor near EHGG is still up and running (as in real life). So finished my flight anyway, but a little less entertaining it was. (ps. The EEL vor wasn’t identified short after take off from EHRD. is it possible that the vor’s range is less then 100nm?) I was at a few thousand feet allready when i tried them the first time (not on video).

15

Some others have mentioned that the radios were switched off and caught them by surprise.

https://forums.flightsimulator.com/t/official-discussion-junkers-ju-52/458062/116

16

Sure. These are approximate values
Terminal TVOR
1000 - 12,000ft ~25NM.

Low altitude LVOR
1000 - 18,000ft ~40NM.

High altitude HVOR
1000 - 14000ft ~40NM.
14000 - 18000ft ~100NM
18000 - 45000ft ~130NM.

1 Like
17

You could get navigraph navdata for MSFS. Then you know for sure you will only have current VOR/NDBs in the sim. Also, with the latest AIRAC Cycle, Navigraph introduced real world VOR/NDB range to MSFS.
If you fly a lot using conventional navigation, go get it! :slight_smile:

Also, due to the increased popularity of pure VOR navigation, they introduced „VOR only“ route generation to simbrief. So youn can plan your route along VORs and be sure you will be in range of one or another:

1 Like
18

Thanks this is great advice! Though i don’t think i’ll use it enough to be willing to pay fot it (altough it’s only a small fee)

I’m back into this kind of flying again because of the Ju. But i doubt it will take very long :face_with_tongue: i’m gonna wait a few weeks to see if i’m still interested. Till then i’ll keep it in mind.

Most of my ‘gaming’ time is spend 90% with simracing. I tend to go bak to msfs when updates are released or new content is out. And really loving it since the latest wu/su. But soon it will wear out again and probably be back into simracing :see_no_evil_monkey: appreciate it though :+1:

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.