MikeS.

Hehe, you're right. But I meant a PAX-airliner, sorry. (but I guess you know that... ;-) )If you fly a cargo-airliner, a single entry RAMP is needed in the cfg because you will possibly find your cargo-jet at a gate with Jetways... most notably if the GATE entry stays before the RAMP in the cfg. Relating to your link above the first entry is prefered. You may notice my way of thinking. It generates less complications if you use a single entry. Either GATE for (PAX)-airliners, RAMP for GA's, or CARGO for cargo airliners, MIL_CARGO for military...etc...best regardsMike

That's very new to me but interesting. But for me there is anyway no need for a RAMP entry do to the fact, that I never will park on a Cargo or GA-Stand with an airliner. But thanks for this information.best regardsMike

HiI'm really satisfied with this new SP1c. But I was also satisfied before indeed... :-) Thanks to PMDG for this restless efforts.But I noticed that there is still an entry in the aircraft.cfg's I wondring everytime why it is like this...:atc_parking_types=GATE, RAMPSo far as I know this entry makes no sense to the FSX-ATC and it will not handle a double entry. It should be GATE or RAMP (in this case GATE, for a BBJ RAMP would be fine) but not both together because FSX will handle it the same way as no entry at all behind the = sign. It just will select a parking-stand wich will fit with the aircraft wing-span.This often results in unsuitable parking-assignments anywhere on the airport. But as a "Pilot" of an airliner we prefer Gate-Stands of course :-)It would be great if you could fix that in a possible next update (just delete the "RAMP"-entry). I everytime did this by myself of course but it's a little bit awkward to do that after each SP I...for all aircraft cfg's and all liveries...Thanks a lot in advance!Best regardsMike