Products Support > GSX Support FSX/P3D
GSX malfunctions when using user-created logos
CaptainSazzman:
--- Quote from: virtuali on May 31, 2023, 03:43:33 pm ---
--- Quote from: CaptainSazzman on May 31, 2023, 02:26:20 pm ---GSX has also started ignoring the atc_parking_codes value I set in the aircraft CFG.
--- End quote ---
GSX never used the atc_parking_codes in the aircraft.cfg, except for choosing the ULDs, are you referring to just these ?
--- End quote ---
Yes. The atc_parking_codes rule seems to be ignored by GSX when choosing which ULD texture to load. This has been happening since April.
I also noticed that the ground handlers I type in the parking settings box are mostly ignored. Same for the catering handler. This second issue has been happening since the end of May update.
Do you have some hints on where to look, please?
Before these issues I had GSX set up like this:
- Imagine I am flying at Frankfurt airport on the PMDG 747.
- My catering handler is WISAG and the ground handler is Fraport (as set in the GSX menu).
- When it is time to board, Lufthansa ULD containers show up because I modified the aircraft cfg to add atc_parking_codes=DLH
Today, none of that is possible. I am not blaming GSX, far from it, I am just giving an example that could help the team.
virtuali:
--- Quote from: CaptainSazzman on May 31, 2023, 07:39:29 pm ---I also noticed that the ground handlers I type in the parking settings box are mostly ignored. Same for the catering handler. This second issue has been happening since the end of May update.
--- End quote ---
This is not an issue. It's how GSX was always supposed to work so, it's really a fix.
The parking codes in the parking spot should NOT directly decide the handler. They should only give a preference, but only if the matching code is for an operator that would otherwise always being chosen, being with an higher score than all the others so, parking code in the parking, were *supposed* to be used ONLY as a tie-breakers for all operators at the maximum score.
However, it didn't work exactly as documented, so using those codes, you could affect the choice of the handler directly, and being able to select handlers which wouldn't be chosen otherwise.
The update you are referring to (in fact, it's not the end of May update, which didn't change anything about codes), it was the one at the end of April instead.
That update, which allowed to choose MULTIPLE EXPLICIT operators (it wasn't possible before), made using parking codes obsolete, because now you can choose any (multiple) operators, bypassing completely the built-in rules.
So the parking codes are finally back to work as originally designed, just as scoring boosters, because the new system is far easier to understand and it gives you more flexibility.
CaptainSazzman:
--- Quote from: virtuali on May 31, 2023, 11:58:51 pm ---
--- Quote from: CaptainSazzman on May 31, 2023, 07:39:29 pm ---I also noticed that the ground handlers I type in the parking settings box are mostly ignored. Same for the catering handler. This second issue has been happening since the end of May update.
--- End quote ---
This is not an issue. It's how GSX was always supposed to work so, it's really a fix.
--- End quote ---
Thank you for the explanation. So if I understand correctly, I should use the multiple-select function in a drop-down list instead of typing the codes right?
Also, I still have a doubt about the atc_parking_codes. I like to use different handlers and different ULD textures based on where I fly. For example, if I am flying Alitalia in Paris Charles de Gaulle I will use Air France as the ground handler and the atc_parking_code to choose a specific ULD livery.
Today, GSX seems to ignore the atc_parking_codes and choose the ULD logo based on the ground handler. How do I set them specifically?
EDIT: I noticed after testing that GSX still ignores the catering livery selected, even after using the multiple select option of the drop-down list. Even after specifying a catering company, a random livery is spawned each time.
virtuali:
--- Quote from: CaptainSazzman on June 01, 2023, 02:24:01 am ---Thank you for the explanation. So if I understand correctly, I should use the multiple-select function in a drop-down list instead of typing the codes right?
--- End quote ---
Yes, if you are making a custom profile, it doesn't make much sense to rely on parking codes, which would only control a preference amongst the ones following the built-in rules. With the multiple custom operators, you can choose any operator, so they are clearly more flexible. Parking codes for handlers/catering should only control what GSX will do with no customization, that was their original design intent.
--- Quote ---Also, I still have a doubt about the atc_parking_codes. I like to use different handlers and different ULD textures based on where I fly. For example, if I am flying Alitalia in Paris Charles de Gaulle I will use Air France as the ground handler and the atc_parking_code to choose a specific ULD livery.
--- End quote ---
As I've said, with the custom operators you can control the handlers by airport, terminal or individual parking, so that's a no issue. About ULDs, then yes, they are still supposed to work with parking codes as they always did.
--- Quote ---EDIT: I noticed after testing that GSX still ignores the catering livery selected, even after using the multiple select option of the drop-down list. Even after specifying a catering company, a random livery is spawned each time.
--- End quote ---
That's not what is supposed to happen. Please clarify exactly which P3D you are using, because you piggybacked into a thread which is specifically P34, since user created logos are only possible there, so I need to know if you are also using P3D4, because in that case, operator logos are handled a bit different, and it is possible there's an issue, because clearly most of our tests are made in MSFS, but the time we give to P3D is almost entirely in V5.
fslogin:
The issue I detailled in this post was for P3D v4
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version