Much appreciated! A GTN would be nice to have but not necessary. The PMS GTN is freeware with a premium version that has many more features. The freeware version is feature complete for typical use though. I know there’s extensive documentation for integration, but since I’m not a developer myself, I have no idea how that works.
Like I said, it would be nice to have but don’t make yourself crazy over it. The GNS is perfectly usable.
There used to be some discussion about this on FSdeveloper.com There is a discussion here on the forum about it. I think 30nm might be “working as designed” It all depends on what type of VOR it is, and the altitude of the plane. And I don’t think there’s anything you can do, it’s related to the scenery design. I got this from a search for msfs vor range
In Microsoft Flight Simulator (MSFS), VOR range depends strictly on the station’s type (High, Low, or Terminal) and your aircraft’s altitude. Because VOR signals are line-of-sight, you must fly high enough to overcome Earth’s curvature. [1, 2]
Standard VOR Service Ranges
MSFS generally follows FAA Standard Service Volumes (SSV), though exact ranges can vary based on individual station coding: [1, 2]
Terminal VOR (T-VOR): ~25 nautical miles (NMI). Used primarily for airport approaches and immediate terminal areas. [1]
Low-Altitude VOR (L-VOR): ~40 NMI up to 14,500 feet. [1, 2]
High-Altitude VOR (H-VOR):
Up to 40 NMI below 14,500 feet.
Up to 100 NMI between 14,500 and 18,000 feet.
Up to 130 NMI at typical cruising altitudes above 18,000 feet. [1, 2, 3, 4, 5]
MSFS-Specific Behavior
Hard Cutoffs: MSFS models VOR reception as an absolute on/off switch. You will lose the signal immediately when flying beyond the station’s coded maximum boundary, whereas real-world radios often pick up faint signals much farther away. [, 2]
Incorrect Station Coding: Some regions in the default MSFS database suffer from incorrectly coded VOR types, resulting in ranges that appear artificially short. [1, 2, 3, 4]
Tips for Better Reception
Climb Higher: If your NAV radio is not capturing the signal, you likely need to increase your altitude to achieve a line-of-sight path.
Use Navigraph: For more accurate global navaid data and up-to-date ranges, many users integrate custom navigation data into their sims.
Third-Party Fixes: If you frequently fly in heavily affected areas, there are community-made mods (such as the Japan VOR Range Fix) available to correct known range discrepancies. [1, 2, 3]
Not to mention, I think MSFS might even take terrain into account. So your question about which VOR and also the aircraft’s altitude is very valid.
Are you saying people fly outside the United States, hmm I didn’t even imagine that..
Good point. I can check both. I’m on my other computer installing both versions now (2020 is my main sim, but I dabble in 2024 until I get frustrated).
For the forum in general, when saying you’re having a problem, every… single… detail… matters.
Imagine if Asobo had enough information to be able to replicate all the bugs people complain about. It would be such a better sim. And people go on wondering why their report got binned, when all they said was “X doesn’t work”… I feel Asobo’s pain in this regard. It’s gotta be soooo frustrating.
On the liveries, there’s a paint kit, right? Might be a good time to see if you have artistic talent. I’ve haven’t picked up the AA5 yet, but I was considering using it as my first test of seeing if I have any talent because it being a Grumman has inspired so many cool paint schemes.
So, got into both 2020 and 2024 with the Tiger with the VFR radios, and you’re right, the click spot on the knob that switches between com1 and com2 doesn’t work in 2024 but does work in 2020.
If you set the speaker to com2 on, you can listen to com2 without switching to Com2 (which is the way the real one worked, at least in the plane I owned). I usually put ATIS on com2 and listen while com1 is active so I don’t miss any ATC calls. And the knob does respond to switching with the ATC window open and selecting the com2 page, it turns to com2 and back to com1 when you select the com1 page.
Once again, we really need to know the details to help you. This plane has a LOT of options.
I just tried the 2024 Tiger with the GPS430 panel. Starts up fine for me (once I remembered to turn on the fuel tank, lol)
Which plane, which panel? It sounds like you’ve done the full checklist to start ( fuel to either tank, battery and alternator on, magnetos on, fuel pump on, prime 3 times, starter button), so it’s definitely an interesting issue.
Ahhh, very interesting find. I switched over to 2D and the POH works just fine, however when I switched back over to VR that’s when the POH is no longer clickable. At least we’re getting somewhere now, lol. And thanks for your response back addressing all of the issues.
On a flight now in the AA-5 Traveler from 29Palms Twentynine Palms KTNP to iniBuilds Palm Springs KPSP-handling OK for now with my TCA sidestick.
Also doing a flight in the AA-5 Cheetah from UK2000 Wittman Regional Airport KOSH to M’M Simulations Appleton International Airport KATW, again no vices handling wise.
What sensitvity settings would you recommend using with the TCA Sidestick for piloting the AA-5’s?
Just acquired the Grumman. How is everyone getting on with the mixture lever? I’ve tried it in all the variants, with/without bindings and it seems that only keyboard shortcuts work in FS2024. I tried all the various iterations of Mixture Axis & Mixture 1 Axis, to no joy. Only my keyboard bindings for “mixture full” & “mixture cut” have any effect. (again, FS2024)
Also pretty disappointed with the night lighting situation. Instrument lights are a red light emanating from overhead, and the map lights just glare in your face and you can’t move them. There are no internal lights for the gauges? Is that typical for the AA5?