How to rename "...A" Gates

[Zwackelpeter]

Gud evening lads,

I did a full renaming of all the Parking positions at KATL, but cant get hold of how to rename the ...A positions
In this case in Atlanta there are only three of them but I'd like to know, how my lines should look like, so the renaming doesnt go into the void entirely.

This is how I tried and as mentioned, those lines let GSX ignore the whole renaming and goes to default:

In the .ini file the Gate is named "[gate d 8a]"

Code: [Select]

    GATE_D_8A : {
        None : (),
        8a : (CustomizedName("Ramp 4| Gate D8A"), ),
    },

Edit:
London Gatwick for example takes it even further - Position 230 is default(and in reality) divided into 230, 230L and 230R.

Code: [Select]

[parking 230]
[parking 230l]
[parking 230r]
I happened to renamed 230 like this:

Code: [Select]

    PARKING : {
        None : (),
        230 : (CustomizedName("Maint Area 3| Ramp 230"), ),
    },

And now I have just three times "Ramp 230"

What am I missing and how can I rename and sort those Positions?
Manual doesnt mention this case.

[Zwackelpeter]

Hello again!

A fellow flight simmer on flightsim.to gave me a hint, which was very helpful.
And turns out I wasnt able to read the manual properly. It is indeed mentioned on page 107.

So at KATL, there are three positions who required this adjustment.
Renaming D8A worked in the "bigger group" of customized names but I had to keep the other two seperate like this, or it wouldnt work:

Code: [Select]

GATE_D : {
        None : (),
        ##Ramp 4
        (...)
        6 : (CustomizedName("Ramp 4| Gate D6"), ),
        8 : (CustomizedName("Ramp 4| Gate D#§"), ),
        10 : (CustomizedName("Ramp 4| Gate D10"), ),
        (...)
    },

     GATE_D_ : {
        None : (),
        1 : (CustomizedName("Ramp 5| Gate D#§"), ),
   
    },

    GATE_D_ : {
        None : (),
        11 : (CustomizedName("Ramp 5| Gate D#§"), ),
   
    },
At Gatwick it worked fine to have them in bigger groups:

Code: [Select]

PARKING: {
        None : (),
        (...)
        ##Maintenance Area 3
        230 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        231 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        232 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        233 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        234 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        235 : (CustomizedName("Maint Area 3| Ramp #§"), ),
        (...)
       },

So eventhough I got it to work, I'd still be interested in an answer on why at KATL I had to seperate the other two postions.
Anybody got an idea?

[virtuali]

This line:

GATE_D_

It's surely an error, because you aren't free to use any name here, it can be only one of the names listed in the manual, or None. This because those matches the actual enums used in the original .BGL file, so those are the only values possible.

So, that line should have been GATE_D but, you already had a dictionary for GATE_D, and I think that line also caused a Python error or, at most, a parking not found.

[Zwackelpeter]

This line:

GATE_D_

Thank you so much for pointing that out. After a while I go crosseyed, when I look at code too long.

Another question:
Is there a way to somehow sort those positions out?
When renaming Marseille(LFML) I recognized that there are multiple "1" positions:

Code: [Select]

[none 1a]
[none 1c]
[none 1p]
By now I know that "#§" does the trick in general.
But here's the problem that 1P is a different Apron, on the other side of the Airport and even more problematic, it is a helipad.
Is there any possibility to sort those positions out/give them a different name/etc?
Or is this just an unfortunate design by the creator and we have to live with it?