Ground services small ga airfield, parking ramp without workers

[DeltaTango]

Hi all,

i am working on a small GA airfiled. A small GA airfield in general has no ground workers, where can I switch the workers off?

There is a Edit button. But nothing happens when I am push this button

 

[Christian Bahr]

Hi!

I also had the problem. Here in the forum there is already a thread for this topic, which has become a bit confusing for my taste. But I was still able to get the information relevant to me there.

You would have to create two new sub-folders in your package subfolder, i.e. where your project was compiled:


...\Packages\"YOUR ADD-ON"\AirportServices\EDLE

For me it looks like this: ...\Packages\bahrometrix-flughafen-edle\AirportServices\EDLE

The subfolder EDLE must correspond to the ICAO code of your airport! Then copy this file into it: Services.xml

The trick is to create the add-on package in the Scenery Editor in the Interspector (Build all).

 

[DeltaTango]

Hello Christian,

first thank you for your hints! I have made so, but unfortunately it doesn't work.

For me is unclear how I have to copy this in the package folder? The package folder is the compiled folder? And how knows the layout.json the service.xml.

I have done following:

1) Made folder airportservices\ICAO\
2) copied service.xml into
3) New entry in inspector

4) made same folder structure in packagesources \ airportservices\ICAO\ and copy also service.xml into

My packagesource folder is EDKF!

5) fill out Service field in inspector

6) compiled

Result is an additional file in packages

in layout.jason has been added this entry

Why does this not work?

 

[DeltaTango]

So now I got it right.

The service.xml must be in the packagesource directory
no matter what it is called, it contains the service.xml. In the Inpector this is specified as assetDir. Specify OutputDir. In this appears then afterwards only the services.spb. In layout.json is then also only this entry.

So only step 4,5,6 is necessary!

 

[pontiac51]

Something changed with the new update (1.12.13.0).

If the output path is set to "AircraftServices/<ICAO>" (mandated by compiler), the SPB is now generated in "Packages/<package_name>/scenery/AirportServices/<ICAO>" (instead of "Packages/<package_name>/AirportServices/<ICAO>").
This seems to be a bug, as the file is not loaded.

I noticed something similar with the polygon BGLs, which used to have their own "scene" folder, but are now located where the scenery BGLs are.

Solution:

1. Compile your project as stated above
2. Move the folder "AirportServices" up one level ("Packages/<package_name>", same level as "scenery")
3. Edit the layout.json file
4. Remove "scenery/" at the entry for service.spb

Does anyone have a simpler solution?

 

[pontiac51]

I have compiled a complete instruction from the sources found here. I hope that helps others.

Remove Airport Ground Services (1.12.13.0) - SDK Discussion / Airports - Microsoft Flight Simulator Forums

 

[BrBlazer]

The most simple solution is to set the parking as "Dock GA" instead of GA Small, Medium or whatever. Dock GA will not spawn pushback and workers.

 

[pontiac51]

Yes, I have also used that solution previously on land based airports.

But I have some airports that have TRUE docks and ramps (like CWOB - Brevoort Island • Flight Simulator 2020 or CJN7 - Little Churchill River / Dunlop's Fly-in Lodge • Flight Simulator 2020) and then people would get their planes wet.

 

[BrBlazer]

Yes, I have also used that solution previously on land based airports.

But I have some airports that have TRUE docks and ramps (like CWOB - Brevoort Island • Flight Simulator 2020 or CJN7 - Little Churchill River / Dunlop's Fly-in Lodge • Flight Simulator 2020) and then people would get their planes wet.

True that. But hey, free wash

 

[Skuxxanator69]

My issue is that I would like the fuel truck to still be there and also have pushbacks on one lot of small or medium spots, but not for another if possible.

I also found that the SDK fails to tell you that the "Shared" base game files have the file path "Asobo_" so the file path is actually Shared\Asobo_IdleWorkers\Large etc.

By adding Asobo_ the workers will spawn in. Without it they will not spawn. So my Ground worker will spawn in the correct spot with the red cone and all, but still, no fuel truck.

Fuel truck is there without the services XML, the parking spot is there and connected etc.

I have tried a few things, removing the space before the "=" before the name=, thought that was wrong?
Changing name to FuelTruck as that's the AIType, but didn't work so changed back.

Here's my XML as I left it.


<SimBase.Document Type="ServiceFile">
<Service.ParkingSpaceServices>
<ParkingSpace name="N_PARKING">
<ParkingTypes>
<ParkingEntry ParkingType="RAMP_GA_SMALL"/>
</ParkingTypes>
<IdleWorkers>
<Spot Frequency="1.0" SpawnDistanceParkingRadiusFactor="1.0" SpawnDistanceAdditionalOffset="0.0" SpawnAngleFromParking="-90" HeadingFromParkingHeading="82" > <IdleWorker Filename="Shared\Asobo_IdleWorkers\Large\V1" EntryWeight="1"/>
</IdleWorkers>
<Services>
<Service name="SmallPushBack" Filename="Shared\Asobo_Pushback\SmallPushback" AIType="SmallPushBack" Frequency="1" SpawnDistanceParkingRadiusFactor="1.0" SpawnDistanceAdditionalOffset="2.0" SpawnAngleFromParking="-10" HeadingFromParkingHeading="150"/>
</Services>
<SleepingActivities>
</SleepingActivities>
</ParkingSpace>
</Service.ParkingSpaceServices>
<Service.AirportServices>
<Services>
<Service name="Fuel" Filename="Shared\Asobo_Fuel\Fuel" ParkingType="VEHICLE" Frequency="1"/>
</Services>
</Service.AirportServices>
</SimBase.Document>

 

[Finni]

Have you made a gate with the type 'vehicle' and connected it to the taxiways/vehicle paths? At least one gate is needed for the fuel truck to spawn in afaik

Sent fra min MAR-LX1A via Tapatalk

 

[Claviateur]

I am trying this and I discovered two things:

According to the tutorial here and the one published by @pontiac51 on flightsimulator.com

- If we create AirportServices/ICAO inside the PackageSources folder, and we enter this path in the inspector as mentioned in the tutorial "airportservices\Z190\" we get an error when we build the package. The reason is that the path shows the AirportServices/ICAO as if it's located outside the Packagesources. Now if we move it outside, it compiles but once the package is installed in community and loaded, the Service remains as default, thus not removed. Yet if I fix the path to point inside the PackageSources and compile, all ok, but when the package is in community, the default services are still there. Also the Fuel Post is there and no way to exclude it even if in the Airport entry I enabled the checkboxes to Delete everything in the default airport.
- The bug and workaround for 1.12.13.0 seems to have been fixed. Perhaps in the latest small patch or update I got few days ago... Now the compiled packages seems to put the airportservices folder at the right place and the Layout.Json shows the right path

 

[pontiac51]

Does it actually compile the XML to a SPB? Or is it still an XML in the Packages folder? Where does the new file land?

 

[Claviateur]

Does it actually compile the XML to a SPB? Or is it still an XML in the Packages folder? Where does the new file land?

Yes it does. This is an example of where the spb is:

Community / AirportPackageName / AirportSecvices / Z123 / service.spb

But now I am trying to find a solution for the default airport's layout not being excluded with my new airport. So I wonder if these are related.

Edit: I just noticed that my service file is missing the (s) at the end! Let's see if the typo will fix the issue.

 

[pontiac51]

It usually does not matter how you name the file.

 

[Claviateur]

It usually does not matter how you name the file.

You're right. So I suppose this has something to do with the fact I can't exclude the default airport layout.

 

[pontiac51]

I have now a different problem. Users tell me that all services on ALL airports disappear when they use my sceneries.

Any idea how to fix this?

 

[pontiac51]

I have removed all AirportServices files and changed all parking spaces to SMALL with a radius of 5 meters.

This seems to get rid of most of the workers. At least I saw none when loading all of the airports several times.