Heads up people the three airports I purchased thru the Marketplace or Orbx many weeks ago do not contain the ILS frequencies all default airports contain. One of them was KPDX, so I deleted it, and the default one now does contain ILS freq as they are supposed to. I just a few days ago reinstalled KPDX and they are still missing. If you have purchased any go to the MFD and search under airport information, FREQ for ILS values–they missing from mine. I zendesked this issue, and they marked it as SOLVED. I just now re-zendesked it.
Report the issue to Orbx, since it’s obviously an issue with their scenery, not with MSFS.
Zendesk is only for issues with the base sim, not for third party addons.
16 Likes
Nothing you should report to zendesk as it is a 3rd party addon.
2 Likes
Nope–this is COMMON to all three airports from different 3rd party devs which implies the SDK simply is leaving these fields out and implies ALL future 3rd party airports will likely display the same issue.
Addons are being sold as in-game purchases and that means they are authorised by MS, this does make it an MSFS issue and Zendesk should provide solutions to these problems. If not then 3rd party addons should not be available inside the game.
My two pennies worth, anyway 
12 Likes
Would they still be missing if you have Navigraph data installed?
3 Likes
I understand your point and thank you for flagging it, but I do agree customers need escalate it to the respective 3rd-party. If vendors are not warning potential customers on the [virtual] store boxes on limitations, regardless if it is “their fault” or not, they (the vendor) should offer refunds IMHO.
If there is really a limitation on the sim/sdk that the 3rd party devs cannot work around, then it’s up to them to hit Asobo in the head until they fix it.
True: I have seen the Navigraph Beta AIRAC for FS2020 re-enables runways (including proper ILS) for airports that are missing from the sim even without installing an add-on.
If you do have an add-on, It remains to be seen how well aligned the Navigraph Runway and corresponding ILS may be with an add-on airport, however.
Also, this is potential proof that there may not be no such ILS “SDK limitation” after all.
2 Likes
It would also be a caveat worth including that if you are a Navigraph subscriber, then these airports may be fully functional after all.
1 Like
EDITED
Disregard what I had here. I re-read your original post and it seems you tested what I was suggesting you try. My bad.
Raise this on the Orbx boards for MSFS Support - there’s a dedicated sub-forum for their add-ons in this sim. They’re very quick to respond.
5 Likes
I just learned someone else who bought KPDX Flightbeam DOES have ILS. I will ask what plane he’s in, and if he added Navigraph update.
Also please be more specific, you mentioned ORBX but there is no KPDX from them. What airport was it?
Orbx had an issue with the exclude polygons in the airport sceneries they first started to port over to MSFS, which excluded MSFS default radio frequencies, ILS approaches and ground services. They have supposedly corrected that now.
Given what you posted, they will mark that as solved every time. Solved only means it’s been removed from the Zendesk stream, in this case as rejected, it does NOT mean the problem is necessarily solved.
In this case, you did not describe a problem that Asobo can address. If instead, you were creating an airport, and you followed the SDK exactly on how to create an ILS, but it wouldn’t work, and you could give them the files and exact steps you used to produce the problem, that is something they could look at and either fix or tell you how to do it correctly.
Based on what you just wrote above, if that’s the problem that you submitted, by definitiion, that is an ORBX problem and will get rejected by Zendesk every time. There is no way Asobo is going to take any responsibility for 3rd party products. They will work with 3rd party vendors who have issues, but will reject all bugs associated with 3rd party products submitted to Zendesk by users.
I don’t mean to be mean, it’s just how the system works, and as it should be.
3 Likes
I am not sure if the information is correct. From what I’ve heard, if you actually dial in the appropriate ILS frequency in the cockpit, you’ll pick it up. It’s just that many of the airports don’t have it available for your Avionics or FMC to auto load into your Approach procedure.
Again, don’t know if this is with a scenery conflict, or what. The ILS frequency is “there” and can be tuned to, it just isn’t published for the user and it doesn’t auto load into the FMC.
I doubt that. I’ve read a thread yesterday where the guy could even program approaches for his scenery airport.
Be that as it may, if the problem is associated with a 3rd party airport, the bug report will be rejected. If you can prove the same happens with a default airport, then that’s a different story.
But, again, that’s a totally different description than what the OP described. How could Asobo address the problem as described by the OP? What you’re saying is a little easier to understand, but would likely still be rejected.
Bug reports have to have every single step used to create the issue described exactly, or they’ll have no way of reproducing the issue, and the bug report will be rejected. They are too busy to have to spend time trying to figure out what people are trying to say.
I was giving an example of a bug that Asobo could address. I didn’t say it is a real problem.
I was replying to the OP, not you. It appears he submitted a similar post in another forum, and it appears that people are able to successfully dial in the correct frequencies manually.
I’ve noticed the same thing on my addon’s but then I usually go to the internet and note the actual ILS frequencies of my destination airport before hand so I have that information available. It’s certainly nice when the FMC on the A320 automatically calls it up, but it’s not a huge issue to dial it in either. Just my .02 worth.
No issues for me with FlightBeam KPDX, but I do have the current AIRAC database from Navigraph. I fly A32NX mostly, and I have noticed that often the ILS frequency isn’t automatically populated on the Rad Nav page like it should be. However, I can add it manually in those cases and the approach always works correctly.
1 Like