ATC have on several occasions assigned me to take off or land on rwy(s) in the opposite (or diagonally) direction of Live Traffic.
Please make ATC assign the same rwy(s) for take off and landings as Live Traffic.
I don’t understand why ATC gives a wrong landing runway when using Live Traffic. Wouldn’t be easier just check what runway is using the real planes to use the same one? Instead, ATC sends me to usually runways that are not used or used only under special conditions.
1 Like
are you using live weather or a preset / custom weather?
ATC should be giving you the runway which is appropriate for weather in SIM… which of course real world traffic won’t follow if it differs.
Some airports have restrictions on runways. In EDDF, for example, RWY 18/36 is only used for take-offs on 18 - no landings on 18 and no operation at all on 36. The sim ATC seems unaware of those restrictions and assigns traffic to runways that make sense according to wind.
Would be great if MSFS was aware of those restrictions. I’m no scenery designer myself, so I do not know if it is possible to tell ATC to use certain runways for certain operations only.
1 Like
Seriously? You expect these people to know the procedures for every airport there is? There are over 30,000 airports in this sim. I think you are being a tad bit nit picky lol.
Well, that’s what nav databases are for. MSFS is totally aware of SIDs and STARs available for certain runways and thus could decide to use only runways with published procedures.
Airports without procedures of course still could use all runways, but they usually don’t have that kind of issue.
The data is there, it just currently has quality issues and is disregarded for the purpose here.
I was not writing about every local procedure for every tiny airstrip.
First, EDDF is not such a tiny airstrip in the middle of nowhere but one of Europe’s major hubs.
Second, EDDF is “handcrafted” and could, for that reason alone, respect those restrictions.
Third, if the sim only used runways that have published procedures this would also solve that issue.
And last but not least, if the AI just used the runway that the planes actually use according to Flightaware we wouldn’t have that discussion, right?
So let’s stay polite, ok?
3 Likes
Seriously? You was expecting the same issues and missing features as in FSX? Even with live traffic which supposedly should use the real data, in handcrafted airports.
Amazing. If Asobo sell you a glitter â– â– â– â– you would say is a cupcake. You must be completely disinterested in IFR flights for not finding this an issue.
I filled a ticket with this on the feedback section of zendesk. Airports should have the option on the SDK to set configs and active runways. And of course the gateway system would simplify this a lot.
On the other hand, I don’t understand why they don’t use the AI for learning the real airport configs.
In Italy, Florence Peretola LIRQ airport has only one runway (05-23)
Due to the presence of a hill for an airliner it’s impossible to make an approach on the 23 therefore the 23 is used only for take-offs and the 05 only for landings. Unfortunately, the FS2020 ATC offers you the approach on the 23 !!!
Anyway, these problems were also there with FSX but using that fantastic tool called ADE Airport Design Editor it was possible to leave a runway open only for take-off or landing even for the default airports. Once a runway closed for landing, ATC simply ignore it.
It would be nice if ATC even directed me to the same runway as ATIS advises 