The MDA is not relevant for the AP, it’s for the callout “minimums”, at which altitude you have to have the runway in sight or declare missed approach.
The fact that it’s not auto-filled is that it depends on the type of your approach and equipment, you can find it on your ILS chart in a table.
And don’t forget to check the alternate minimums as well…
F.Y.I. Solved means added to the Bug tracker as explained below. There’s no need to resubmit.
https://flightsimulator.zendesk.com/hc/en-us/articles/360014232420-Zendesk-Bug-Reporting-FAQ
Ticket Statuses Explained (Bug Reports)
- Open: The report is in the queue. A bug report will remain open until it’s updated or marked as solved.
- Awaiting your reply: Our team contacted you to request more information and is waiting for your reply.
- Solved: The bug report has been handled—our team has recorded the bug in our internal bug and issue tracker. Please note this does not mean you will see the bug fixed in the next update, but has been recorded and prioritized accordingly.
I also have Navigraph. How do I find out if I have the current AIRAC database into the sim?
Look in the community folder; you should have navigraph beta and a paid subscription.
Thrust settings?
Just checked right now and I don’t have anything for navigraph in my community folder
So, all of this time I’ve been playing without it? What does it supposed to do or what difference will it make?
Also, how do I make it go to my community folder?
There are two pieces of software:
Navigraph FMS Data Manager
Navigraph Data (the Beta already discussed)
For me FMS Data Manager is only aware of LittleNavMap.
The Navigraph Data (Beta) program is the one that installs the data into MSFS.
I’ve not yet created an account on the Navigraph forums, and I believe that is where a thread is tucked away with the download links, but I got my copy from the following Reddit post:
Once installed, you should see the following folder:
Zebdesk “SOLVED” really means that ZenDesk have finished Processing the submitted bug/request and it in now i the system for Asobo to deal with. The report is “solved” as far as Zendesk is concerned because they have finished processing it.
“Solved” is a most misleading word to use, (but its their SCRUM “Buzz word”).
A Much better word in this case, to present to the Customer might be “Submitted” or “Processed” .. and not a word that implies the issue is Solved/Resolved.
Their use of the word “Backlog” also has a very specific “Scrum” meaning, that is not obvious to the typical user probably meaning different things to different users.
Backlog can be is short for “Product Backlog”
As described in the Scrum Guide, the Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
Then again, backlog could be short for “Sprint Backlog” – but I doubt it
Definition: A sprint backlog is a segment of Product Backlog Items (PBIs) that the team selects to complete during a Scrum sprint. These PBIs are typically user stories taken from the product backlog.
yeah, I am NOT a Scrum fan !!!
No it doesn’t. That would imply that Asobo is responsible for anything that a 3rd party screws up. Your two pennies are worthless.
You also can’t blame the cow because it produces burger patties for McDonald’s which make you fat.
I am using a lot off Orbx scenerys and what i flown in there with ils are all worked fine
no matter what plane from the Airliners.
With all newest scenery updates taken..
cheers
What a weird response?
I purchased a car. On the extras list I chose a sat nav/media system. This was not made by the car manufacturer but they took responsibility when it failed. Sorry, bud, but your response is screwed.
Its not a question of deciding who you think you want to complain to.
The ones to FIX it is the one you should be talking to ..assuming you really want it fixed,
In any case, I get the impression that it is already fixed, so all you need is an update ???
The sat nav system in your car was installed by the car manufacturer and provided to you as part of the total “new car package”.
But, if you buy a sat nav system after you already own the car, and have it installed by a specialty shop not associated with the car manufacturer, it is not the car maker’s responsibility to fix the system if it doesn’t work right. That would be something you would have to take up with the maker of the sat nav, or the shop that installed it.
An add-on airport is made by an independent third party who is not part of Asobo, and it would not have been included as a part of the base sim. If something like the ILS at the add-on airport does not work because a bug in the sim itself is preventing it, then I would agree that Asobo has the responsibility to fix the problem.
But if the ILS doesn’t work because the designer of the airport made a mistake in building it, then there is nothing Asobo can do. Only the author of the airport (who has sole access to the source code for the product), can fix it.
I can attest that it ISN’T a bug in the product. I have several 3rd party airports and had different results on three of them flying the default A320 using a High Altitude IFR flight plan without a specific arrival or approach.
KPDX. The ILS was NOT auto tuned when I chose an approach from the FMC. Manually dialing in the frequency in the FMC did bring up the localizer and allowed the plane to track the localizer on approach (albeit, low on the glidescope). KPDX has a bigger bug in that it routes everything to Runway 3 despite other aircraft using the other two larger runways. That’s another topic though.
CYVR. The ILS WAS auto tuned when I chose an approach. I was expecting to have to dial it in, and delightfully found that it was already there. Nice. The aircraft tracked the glidescope as close as “properly” as it currently does.
KATL. The ILS was NOT auto tuned when I chose the approach. Entering it in the FMC, once again allowed me to see the localizer and allowed the aircraft to track the glidescope.
So this isn’t a bug with the original simulator, or else it would affect all third party airports.
One thing to keep in mind, the ILS localizers were all there. So it’s not as if you couldn’t dial into them. And if you go into the flight planner and turn on navaids, you could zoom to each airport, and click on the localizer and get the frequency. So it’s not as if the airports are masking them, or making them unavailable. They just aren’t auto loading the frequency into the avionics.
That’s the bug, and it appears to be with the 3rd Party designer, not Asobo. But should that stop you from buying ALL 3rd party airports? I don’t know, that sentiment seems to be a little “over-cooked”.
Royal: this problem is common to 3 different airports from 3 different 3rd parties, which suggests something COMMON between them. I did reach out to Orbx, they really just shined it on w/ no solution proposed. That will be the END of all future airport purchases until this is sorted out.
I did actually quite a while ago and they esssentially shined it on. I went back just yesterday to repost the issue has not been addressed. Once again people this issue is COMMON to all thru airports: ILS frequencies are missing in the MFD. Now, this is in the TBM930 which displays all ILS freq for default airports. So I’ve not checked but will w/ another aircraft or two.
Can you expound on “shined?” Did they outright deny it? Obfuscate? Redirect? In situations where you need to establish accountability, it’s important to be clear about what people did or did not say, or did or did not do. I’m trying to understand how they exactly responded. This is important to me in the sense that I have invested a lot of money in previous FSX products from Orbx, and I would want to understand level of commitment to the new simulator (or not as the case may be).
Didn’t you post on Avism too?
There’s nothing wrong with addon airports friend.
John Burgess on the Orbx forum replied:
Please let me know if there is an Orbx airport where the ILS frequency is genuinely missing and I’ll pursue the issue.
Maybe you can post your experience with KPDX and discuss with him there? He’s a Team Member, so you have an opening…
https://orbxsystems.com/forum/topic/202150-no-ils-frequencies/