Products Support > GSX Support FSX/P3D

Issues still evident [P3Dv4.5]

<< < (2/2)

trisho0:

--- Quote from: Supera380 on August 26, 2022, 04:46:58 pm ---At least for the Justim LEPA issue I was able to solve this.

The "No Jetway can Operate at This Position" warning was generated from what I can tell by the aircraft position not being close enough to the jetways. Once I discovered that, I was able to slew the aircraft to a closer position and then the SODE jetways were operating once more. Boarding of crew and passengers proceeded as expected. LEPA now working in P3D.

--- End quote ---
Try testing with scenery without SODE xml file but with gsx.INI file only and see if it works.

Patricio Valdes

fnav77:
I an also having difficulties with UK2000 EGLL.... If you delete the GSX config file .ini and also delte all the config files provided by the scenery developer, then GSX works again (and reads the AFCAD file) and allows me to edit the gates again, etc.... However, that way, you lose all the work you have done before for that airport, which is a shame.
If you try to save the data from the old file and then paste it into the newly created config file, then GSX no longer works and no longer recognises all the gates in the AFCAD (back to one gate only).

Is there a change in the way these airport config files are written, that GSX no longer recognises them?

liamr685:

--- Quote from: fnav77 on August 26, 2022, 07:36:09 pm ---I an also having difficulties with UK2000 EGLL.... If you delete the GSX config file .ini and also delte all the config files provided by the scenery developer, then GSX works again (and reads the AFCAD file) and allows me to edit the gates again, etc.... However, that way, you lose all the work you have done before for that airport, which is a shame.
If you try to save the data from the old file and then paste it into the newly created config file, then GSX no longer works and no longer recognises all the gates in the AFCAD (back to one gate only).

Is there a change in the way these airport config files are written, that GSX no longer recognises them?

--- End quote ---

I cut the INI files and pasted them elsewhere so a new set would be generated.
This didn’t work for me, it didn’t bother to generate new ones.

liamr685:

--- Quote from: fnav77 on August 26, 2022, 07:36:09 pm ---I an also having difficulties with UK2000 EGLL.... If you delete the GSX config file .ini and also delte all the config files provided by the scenery developer, then GSX works again (and reads the AFCAD file) and allows me to edit the gates again, etc.... However, that way, you lose all the work you have done before for that airport, which is a shame.
If you try to save the data from the old file and then paste it into the newly created config file, then GSX no longer works and no longer recognises all the gates in the AFCAD (back to one gate only).

Is there a change in the way these airport config files are written, that GSX no longer recognises them?

--- End quote ---

Just want to make sure im moving the correct files.

for UK2000 EGLL, which files am i removing, and where are their locations?

Navigation

[0] Message Index

[*] Previous page