No option 6

[flapsup]

Hi Umberto,
At EGLL (UK2000) and EDDM (AS) there is no configration option at these two airports. Only get 1-5 on the menu. Tried different gates, and if you want to test, gate 309 EGLL and Gate 246 at EDDM.

[sjt375]

I've received similar results at LGAV (flytampa) and EDDM (Aerosoft)

[virtuali]

As explained on the manual, it's because all these airports already have a customization made by us, so the parking editor won't work there.

For Aerosoft EDDM, we made a quick-n-dirty customization, just indicating where all the jetways are, which usually cover the most annoying problem of seeing all stairs on a gate, but Fly-Tampa Athens is fully customized, and we are doing ( still not finished, though ) a full-blown customization with 100% precise vehicle placement for UK2000 EGLL, there's really no need to customized these ones.

You can check which airports have been customized by GSX, by looking at the fsdreamteam\Couatl\GSX\airports folder, the file names should be self-explanatory. Yes, you can remove our customization by deleting a file, but keep in mind it will restored automatically with the first Live Update.

[Bruce Hamilton]

As explained on the manual, it's because all these airports already have a customization made by us, so the parking editor won't work there.

Any possibility of changing that, for those who like to tweak their FSX?

[Paul Humphries]

I have lost option 6 at EGBB. I edited once on Sunday. Can't see the file in the said folder?

[Paul Humphries]

Arh right. Once you have edited the parking and applied you can't re-edit unless you delete the ini file created in C:\Users\username\AppData\Roaming\Virtuali\GSX?

[virtuali]

Arh right. Once you have edited the parking and applied you can't re-edit unless you delete the ini file created in C:\Users\username\AppData\Roaming\Virtuali\GSX?

Surely not, you can edit a few parkings, then continue another day, etc...

[flapsup]

Not after an update anyway. I have always had to delete the ini files after a major update. Applies to any airport, default and 3rd party.

[virtuali]

Update or not, doesn't make any difference, an .INI file previously created with an older version is forward compatible, the update only added new commands, but old one are still supported.

The only thing that might affect this, is if you started working on an airport with a different AFCAD than the one currently in use.

[Paul Humphries]

The only thing that might affect this, is if you started working on an airport with a different AFCAD than the one currently in use.

Yep thats what happened with me, I tried updated AFCAD after 1st attempt at editing EGBB (UK2000)

All sorted now.
Thanks Umberto

[flapsup]

The only afcad I have ever altered is KLAX and that was to adjust gate assignment. So I still can confirm that I need delete the ini files after a major update.

[virtuali]

I can only confirm there's no need to delete the .ini file after a major update, unless the AFCAD has changed.

[Pooch]

Umberto, in the past I had to rename the respective .pye-file in fsx\fsdreamteam\couatl\GSX\airports, which was placed again by every update and I renamed it again everytime as the .pye-file overrides the .ini-file resulting in no option 6.

In the manual page 25 I read :

"With version 1.5 and the Graphical Editor, the restriction you can’t edit an already-customized airport, no longer applies, since you are now able to specify all vehicle positions with no restrictions."

does this mean, the .pye-file can remain unchanged and the .ini-file still works ?
Thanks, Peter

[virtuali]

does this mean, the .pye-file can remain unchanged and the .ini-file still works ?

The .ini file takes precedence over the .pye file, but that doesn't mean the .pye file is ignored if there's an .INI: is still used, but the parkings defined ( or redefined) in the .INI file will be used instead, everything else will come from the .pye file. And things that only the .pye file can do (at this time), like custom Pushback paths, custom gate names and custom docking systems, will still be taken from the .pye file, even if you customized that parking with the graphical editor, only the vehicles starting position will be overridden with those in the .INI file.

It's working exactly as one would want to, an already customized airport can be simply refined with the .INI file, with no need to do everything from scratch. The .INI files we posted for FSDT sceneries in the Sharing area, are supposed to AUGMENT the customization that was supplied with the .pye file. In fact, they are supposed to be used together with the default .pye files.

[Pooch]

Thanks for the clarification.
Peter