Umberto,
May I come back to the gate F4A attribution on landing.
Unfortunately, there is a bug in FS2020 with the choice of a gate on arrival. No problem to chose a gate and if you fly straight forward your flight plan, it work. Simulation will give you the gate you chosen. But if you have saved this flight in a FLT file, just after the loading of the aircraft, in dark cockpit situation and then, later on, during a new session, you load this saved flight and fly it, it wont work !?!
Curiously, you can see on the map of the flight plan editor, that the gate you selected was saved (you can also see that in reading inside the .FLT file), but the simulation ignore this part of the FLT data and give always instead the famous F4A gate. No randomness at all here ! The simulation probably start to read some data list from your BGL and always choose F4A. Don't ask me why ! But maybe you know why and can perhaps remedy.
To be always parked on this F4A location, do not do justice to the beauty of this great scenery ! If we have to be always parked at the same location, because of poor simulation AI, lets almost be parked in the most beautiful part of the airport, on a position with a mobile gateway !
So, if you can fool this poor FS2020 AI to make it to chose, for example the gate 35, in the heart of the airport, this would be great. Maybe it is just a change in the order of the items of the gates data list ?
Of course, I can still choose the gate manually, but because of the bug I describe before, I cannot use FLT save file, having an arrival gate saved in it and I have to rebuild the whole flight plan manually each time I want a specific arrival gate, which might be quite boring, after some time.
Of course this is only a minor suggestion. If it's complicated to do, then we forget !
anyway, thanks to take this into consideration.
