Asobo very kindly gave us an example Services.xml file in the SDK.
Unfortunately, the syntax they used is wrong in real life. Granted, we should check everything so the author should always check filename paths, but it’s taken me 4 months of working on this aspect and 3 hours of testing today trying to figure out why I couldn’t call a fuel truck at my airport (“No fuel trucks are available” response from ground control) before I figured out a solution. Everybody’s files I’ve looked at, we all assumed the example was correctly written.
The Services delivered with the game are in …\OneStore\Asobo-services\AirportServices\Shared. The rather unfortunate thing is that the directories in this directory are named differently than they are listed in the example file.
The example file for instance suggests the the service for fuel trucks should be written as
<Service name ="Fuel" Filename="Shared\Fuel\Fuel" ParkingType="VEHICLE" Frequency="1"/>
In actuality, it should be
<Service name ="Fuel" Filename="Shared\Asobo_Fuel\Fuel" ParkingType="VEHICLE" Frequency="1"/>
All of the Service scripts are in directories that start with Asobo_, yet this is not on any of the example paths. When I fixed the filename path to account for this, I could start calling a fuel truck again at my airport that I used Services.xml and ICAO_LWcfg.xml files to reduce traffic and get rid of pushbacks. This is true for all services, for instance, Shared\Asobo_GroundPowerUnit\GroundPowerUnit, not Shared\GroundPowerUnit\GroundPowerUnit
I hope this helps someone figure out how to get their services files working.
While it’s not a critical error, I’m sure a lot of people will miss this. I submitted a bug report to Zendesk on it. I’m kind of sad I spent my afternoon figuring it out. But I’m glad I fixed it, for me at least.