Hello Umberto,
I tell you what I do with many purchased airports:
Often the sceneries don't reflect the actual usage of runways, cf. flightradar24, flightaware, etc.
1.
If the runways are parallel, but displaced, e.g. EDDB, ...
-----
T
-----
... take-offs and landings are distributed so, that the taxi time from/to the terminal is minimised.
2.
If there are more parallel runways (e.g. KLAX, KDFW), ...
-----
-----
T
-----
-----
the outer runways will be used rather for landings, the inner runways for take-offs.
3.
In more complex runway setups like KORD or EHAM, the rational described above AND wind sectors decide on which runways are used for T/O and landings.
As said, purchased sceneries often ignore this completely:
A. All parallel runways are 'open' for both; this might be fine for the KLAX example since p3d IMHO chooses the closest runway for an approaching or ready-for-taxi aircraft (AI or my 'own' plane).
B. In the EDDB example the shorter-taxi-time setup improves the flow of taxiing aircraft; the AI aircraft less block themselves waiting the first aircraft to disappear after a given time-out.
C. In more complex runway setups sometimes the 7.9° crosswind method make the runways parallel, but this works only nicely if the wind blows accordingly in the direction of the 'paralleled' runways. If the wind deviates beyond a certain degree (not sure, but I think also the wind velocity seems to play a role --- if very weak winds blow...), AI aircraft might use runways which in real life would never be used simultaneously.
I know, it is only a simulation... 8^)
Back to your question regarding C:\Program Files (x86)\Addon Manager\FsDreamTeam\KORDV2\scenery\KORD 040-090_220-270deg:
If I don't like the purchased scenery runway setup in the AFCAD file, I restrict the used runway directions for take-offs and landings, close them completely for certain wind directions, parallel them if necessary with the 7.9° crosswind runways, sometimes 'paralleling' the smaller sector like a V, sometimes 'paralleling' the obtuse angle \_, create additional folders with sectors of paralleled runway directions in its name, create a subfolder \scenery, put in the edited, compiled AFCAD file, rename the original bgl file to ...bgl.off, bind the new sceneries into the simulation, and have only one of this extra AFCAD file activated, depending on the wind 'today'.
This allows even during a flight to change the AFCAD file, if the wind direction of your destination airport has changed in the meantime
(and only if you are not too close to your destination airport; sometimes the simulation CTDs, if the airport has already been loaded. ).
Back to my original question on dis-/appearing terminals and jetways at KORD:
(a) I found a reference in the kord-V2_fsdt.ini file to the AFCAD containing folder (afcad_path = ...). So I added this reference into copied ini files and put them into my wind dependent scenery folders, and switched the original ini off.
(b) the number created alpha-india AI aircraft seems to be too high to show liveries and the KORD terminals continuously. If I reduce the number of AI aircraft, the flicker stops and all is fine.
So, thank you for your hint, which made me look into your ini file! There I had to 'correct' the afcad_path.
Thx again,
André
tl;nr...
