Products Support > GSX Support FSX/P3D

Choice of Ground Handler - How to set preferences?

<< < (3/4) > >>

virtuali:

--- Quote from: Fragtality on July 23, 2020, 02:08:28 pm ---My impression is that customizing the airport is breaking/ignoring the scoring system - is it intended that these features collide?
--- End quote ---

No, it doesn't. Unless, of course, the thing you customized is precisely the operator. But in that case, you would only get ONE operator ( the one you chose ), with no menu choice. That's intended, and it's precisely done ( and it's the only way to ), let users override the rules system.


--- Quote ---- rules files not modified (deleted them and did a live update, just in case something else did)
--- End quote ---

There can be two rules files, the one in %APPDATA% ( created only when you add a new custom texture for a new operator ) is never touched by the Live Update, and by default doesn't have any rules, so it's not doing anything, but if you add rules to it, it will overwrite the same rule on the stock file in the GSX install folder. So, if you modified this a long time ago, it's still there, and it will never be removed or changed, even if you reinstall GSX. Check if you have that one.

Fragtality:

--- Quote ---No, it doesn't. Unless, of course, the thing you customized is precisely the operator. But in that case, you would only get ONE operator ( the one you chose ), with no menu choice. That's intended, and it's precisely done ( and it's the only way to ), let users override the rules system.
--- End quote ---
But how can it be then, that GSX does not score DLH or Fraport higher and makes an "equal choice" between all available operators and might also choose TAP, SAS or AEE? (see my descriptions under customization - even when I start with default/internal configuration and modify only the airline codes, it is happening)


--- Quote ---There can be two rules files, the one in %APPDATA% ( created only when you add a new custom texture for a new operator ) is never touched by the Live Update, and by default doesn't have any rules, so it's not doing anything, but if you add rules to it, it will overwrite the same rule on the stock file in the GSX install folder. So, if you modified this a long time ago, it's still there, and it will never be removed or changed, even if you reinstall GSX. Check if you have that one.
--- End quote ---
The whole installation is only a few days old (tried to clean everything before), so an old "residue" is likely not the case.
But I've searched for "rules" in appdata\virtuali: I have only rules.cfg files for jetwaylogos (GSX\texture\jetwaylogo\texture.xxxx\rules.cfg). There is no texture/rules.cfg for Fraport or EDDF. Only for Lufthansa and all 3 are basically empty (just an entry like "[Airline_Lufthansa_Yellow]" e.g.)

virtuali:

--- Quote from: Fragtality on July 23, 2020, 10:34:18 pm ---But how can it be then, that GSX does not score DLH or Fraport higher and makes an "equal choice" between all available operators and might also choose TAP, SAS or AEE?
--- End quote ---

The thing is, it doesn't do that. As I've said, I tried it, and I get Fraport automatically, because is the only operator with a score of 4 at EDDF.


--- Quote ---I have only rules.cfg files for jetwaylogos (GSX\texture\jetwaylogo\texture.xxxx\rules.cfg)
--- End quote ---

And do any of these specify EDDF ?

Fragtality:

--- Quote ---The thing is, it doesn't do that. As I've said, I tried it, and I get Fraport automatically, because is the only operator with a score of 4 at EDDF.
--- End quote ---
I believe you that it *should not* do it, but sorry, it *does do* that. I have given you many examples?! Did you test with a customization in place?
I've tested it also, the only time Fraport is choosen automatically is when there is no customization. As soon as the airlinecodes are altered (even through GSX UI) and even when _FRA and FRAPORT is added there also, GSX scoring gets irrelevant, meaning it chooses something out of the list.
I've tested something else also: I now edited the rules_handling.cfg and added EDDF as icaoprefix for [LH]. Nothing changes, even though DLH should be scored higher now, GSX will just choose something equally from the list!
But when I remove the all airlinecodes for that gate again, I get a choice between Lufthansa and Fraport (because both score higher now as expected through my customization of the handling rules).
So sorry for me it is very clear: All that scoring is completely ignored as soon as the user customizes the airline code. It is just like that. The big question is now: is it something with my installation, is it intended behaviour or is it a bug?


--- Quote ---And do any of these specify EDDF ?
--- End quote ---
No, I've searched through all of them. No hits for "EDDF" or "Fraport".

Fragtality:
Update:

Customization DOES brake scoring. Proof is given by yourself: http://www.fsdreamteam.com/forum/index.php/topic,14732.0.html and the manual.
So essentially we both forgot to read properly ... me the manual and you my answers.  :P
Also, I didn't expect that cartayna (given all the dedication he put in creating his configs) was ignoring the / didn't know the behaviour of GSX when the airline code (which really means operator code) is changed.

We're back to the point for feature requests:
A) Don't call this option Airline Code, please rename it, it is just confusing (proof: this thread). When it is about choosing preferred operators, maybe call it "Preferred Operators".
B) Please add a system which makes a relationship between airline and operator choice (like you described).
C) If B will not be added, please review if there is some kind of way to alter the operator codes AND have that scoring system. Maybe something like "Use Scoring System for the configured Operators".

And it was no joke when I wrote that I even would help coding to make B (or at leas C) possible. ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page