KCLM missing RNAV 27

[hughesj2]

@Gilandred Yeah was gonna say think Nick just uses the sim AIRAC, MS or Navigraph if installed so might be worth raising with Navigraph on their forums

[hughesj2]

Just checked mine and it's the same, there's no RW27 there in 2020, 8 & 26, assume a magvar issue?

[hughesj2]

According to Google (Gemini) the runway designations were changed from 08/26 to 09/27 in October 2023 lol

[Gilandred]

I believe there’s a way to update the magdec.bgl file. I’ll see about doing that.

[jmarkows]

There is, there's a guy who generates them at least once a year. I should probably update mine in both sims.

[hughesj2]

@jmarkows I thought both were updated much more regularly? Might be wrong though. Strange it's ok in 2024. Something similar happened recently with EDDL or EDDK I think where the numbers were off for ages, people posted about it in the MSFS forums IIRC

[jmarkows]

I don't think the sim ever updates them, and I'd have to look again how often the guy who generates the new mag var files does it.

[hughesj2]

@jmarkows https://devsupport.flightsimulator.com/t/reliability-of-magvar-in-facility-records/13762/2

WMM2025 used in 2024 apparently? But this thread reads like even if magvar upto date the facilities file? may ignore it? Maybe that's why not all runways are updating automatically with magvar updates? Who knows, one for a scenery dev I guess....Be interesting to see if updating the magvars does actually fix this issue though if you're going to try it anyway? I'll leave mine stock for comparison
Cheers
James

[Gilandred]

I updated the magvar file and it didn’t make a difference. Note that I only tried this for add on scenery and not default. Default scenery is generally so poorly done I never fly anyplace with it.

[hughesj2]

@Gilandred Yeah so I don't think the runways "read" the magvar so I'd expect that someone (Asobo/MS for this airport) would have to manually amend the runway numbers and maybe localisers etc? Probably just been missed