The problem hasn’t changed from what I can tell.
I was vectored to KORD ILS 10C recently on VATSIM and didn’t pick up the localizer until much closer than the chart indicates it would be available.
I would really like to learn how MSFS models it’s localizers and glide slopes and hopefully work on a fix.
Is there any indication that modifying navaids globally will be possible with the scenery hub/gateway one day?
A Navigraph subscription will likely address your problem. They have much better navigation signal modeling.
I worked directly with Navigraph to propose solutions and it is still inadequate due to in-game limitations.
A different localizer system is necessary.
Same for the ADF ..
Ref ALL Radio systems, including both Nav Radios & ADF
As far a actualy Receiving a signal, be it noisy at longer ranges or not, cuuenrly its far to DIGITAL.
25 miles an it’s a good signal
25.1 miles and there is no signal at all
The 25 mile number in the Database is the maximum GUARANTEED reliable range, not the maximum detectable range.
Nav signal need NOISE at longer range, both on the processed information, as well as the Audio>
This should have improved in 2020, and not be so poorly simulated , as it was so many years ago in FSX
Is there any chance that improved simulation of radio-based navaids is coming for MSFS 2024?
Will edits of these NAVAIDs be possible in World Hub?
This topic only has 10 votes, so I fear it hasn’t and won’t garner attention despite the current model’s negative impacts on simulated IFR flight and air traffic control.
Instead of arbitrary, invisible lines in the sky that define localizer courses, something at least quasi-realistically modeling radio propagation based on antenna placement/function would be fantastic.
This ideally needs an update, it’s been 5 years now and this is still broken even with accurate certification ranges from navigraph. From what I understand the glideslope range is forced to be equal to 75% of the localiser range which makes huge issues at places like LOWI, where the glide and localiser are at around 20nm.
I’d appreciate this being looked into perhaps with a signal degradation curve and 50nm+ ranges
I wrote this up as a bug very early in the MSFS 2020 release period, which I discovered using the SDK to design or modify airports. The SDK container for the ILS includes a range property that I found is ignored by the compiler. Navigraph has confirmed this. Just another example of sloppy software development configuration management.
So it’s a fixable thing that Microsoft could finally sort out?