I’m sure it is a limitation of the simulator (FS2020/ and 2024), but the service volumes for the LOC/GS on 24L/25R in LAX should be extended by quite a bit. LAX is “special” in that it doesn’t conform to normal ILS service volume limits. For LAX I believe the LOC extends to about 85 miles(!)… This isn’t replicated in the sim (for example in the real world, I’ll check LOC performance compared to my LNAV line, and if its strong and matches, I’ll join up with the LOC signal about 50nm out from the airport)
Hi,
We developed methods to calculate the loc ranges in 2020 and 2024. In 2020, the range was limited and hardcoded to 27 NM even when you set a new range. 2024, this should be fixed, but 2024 is more of a surprise package, depending on the updates and whether the sim takes our ranges.
With the current version, I feel that the loc ranges are set to a static value again (which was not the case before). We will see what happens in the future and if ASOBO/MS fixes this.
By the way, KLAX also has, in our database, with our calculation, a range of more than 85 NM, so the data aren’t the issue here.
Cheers
Richard
Oh wow. 85nm… then you got it (24R!). I feel like with this new sim, each update surprises us with (breaking) changes (being on a certain Maddog beta team).
Sorry, wrong airport what I have checked … for KLAX we have calculated:
06L/R = 25 NM
07L/R = 25 NM
24L/R = 50 NM
25L/R = 50 NM
These ranges are included in our dataset, but as you also wrote, they must be tested after every update (client/server).
I hope that helps & sorry for the mistake,
Richard
I’ll give it a test in MSFS2024… For now I was getting 27NM for 24R in the sim. I’m guessing when the data is streamed it may be overriding what navigraph has set.
ESVs for LAX on the westerlies should be- 24R 85nm, 25L 38NM.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.