Hi,
due the missing information of the simulatior type and addon a general answer.
According the FAA, the runway idents for KVLL are 10/28. We have exactly the same in our data and charts. The same for the approach. The FAA database contains only a RNP10 approach into KVLL, no visuals. Also here, our data contains only this RNP10 approach.
Sorry, I don’r know where your visuals come from, nor why your runway idents are wrong.
Hi Mark,
the problem here is, that the MSFS scenery is outdated because as I (and also you) have wrote before, the runway-idents are 10/28 and not 09/27. We offer the RNP approach for 10 and there is no visual approach available in the data, not in our data nor in the FAA.
We may not change the runway idents, even when we could - and there is a limitation in the sim. When the sim can´t assign the procedures to a runway-ident, the sim disable the terminal procedures. Thats not what we have in our hands, that´s a limitation from day one on from MSFS 2020 and we hope, the logic in MSFS 2024 is better but we don´t know.
Here what we offer in our data and what you still have on your system, when the current cycle is installed:
You see no visual approach, only the RNP10 approach. You see also, the procedures with the runways 10/28 - and due this fact, that the idents are differ, the MSFS doesn´t show you these procedures, even when you still have in on your system.
So, please report the wrong runway-idents to ASOBO/MS. As soon, the runway idents are corrected, you will see the correct data.
Thanks, Richard, for the detailed reply. I’m trying to wrap my head around how the sim will prevent the approach from even being an option if the runways aren’t correct (as they change with changing location of the poles, closure of runways, etc). You would think that if the navdata is complete, the sim would still allow the approach to be selected. Even an RNAV GPS approach is basically GPS waypoints.