• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Different airport services on different parking types

Messages
278
Country
finland
I have made an airport that should have pushbacks and other services on the large parkings (there are no gates), but no services at all on the small GA parkings. I have not found out how to make this work correctly. Does somebody have ideas on how to do it? And what is the best way to remove all services from small GA airports without affecting other airports? Any tested and working ideas?
 
Look into Airport Services:
https://docs.flightsimulator.com/ht...g_World/Airport_Services/Airport_Services.htm

Add an asset group to your project:
XML:
<AssetGroup Name="services">
  <Type>SPB</Type>
  <AssetDir>PackageSources\AirportServices\EEKU\</AssetDir>
  <OutputDir>AirportServices\EEKU\</OutputDir>
</AssetGroup>

Then create PackageSources\AirportServices\[ICAO] folder and place Services.xml there.

This is what I have in Services.xml for EEKU, which is a small grass airfield with scheduled passenger traffic during winter. It has one medium-sized GA parking spot for a scheduled BN-2 Islander and a few small GA parking spots for Pipers and Cessnas. Small parking spots have no services at all, and the medium parking has a marshaller with 10% probability (appears one time out of ten).

XML:
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="ServiceFile" version="1,0">
    <Filename>Services.spb</Filename>
    <Service.ParkingSpaceServices>
        <ParkingSpace>
            <Name>RAMP SMALL</Name>
            <ParkingTypes>
                <LivingWorld.ParkingEntry>
                    <ParkingType>RAMP_GA_SMALL</ParkingType>
                </LivingWorld.ParkingEntry>
            </ParkingTypes>
            <Services/>
        </ParkingSpace>
        <ParkingSpace>
            <Name>RAMP MEDIUM</Name>
            <ParkingTypes>
                <LivingWorld.ParkingEntry>
                    <ParkingType>RAMP_GA_MEDIUM</ParkingType>
                </LivingWorld.ParkingEntry>
            </ParkingTypes>
            <Services>
                <Service>
                    <Name>Marshaller</Name>
                    <Filename>Shared\Asobo_Marshaller\Marshaller</Filename>
                    <AIType>Marshaller</AIType>
                    <Frequency>0.100</Frequency>
                    <SpawnDistanceParkingRadiusFactor>1.000</SpawnDistanceParkingRadiusFactor>
                    <SpawnDistanceAdditionalOffset>3.000</SpawnDistanceAdditionalOffset>
                    <SpawnAngleFromParking>0.000</SpawnAngleFromParking>
                    <HeadingFromParkingHeading>180.000</HeadingFromParkingHeading>
                </Service>
            </Services>
        </ParkingSpace>
    </Service.ParkingSpaceServices>
    <Service.AirportServices>
        <Services/>
    </Service.AirportServices>
</SimBase.Document>

You can use the same Services.xml to customize the behaviour and models of services too - for example, use a custom refueling truck.
 
Last edited:
Thank you. I already have the asset group and the Airport_Services.xml, but it is not working as intended. I have something wrong. Will compare with your sample to find the error!
 
Naming matters. As far as I know, it has to be in a folder named Shared (for global configuration) or the airport's ICAO code (for local configuration), and the config file must be named Services.xml and nothing else.
 
And it must be in the root directory of the package in AirportServices\<icao>\Services.xml
LivingWorldCfg is in the root directory as well in LivingWorld_Config\<icao>_LWcfg.xml

Spelling must be exact. It took me forever to realize I was missing the underscore in LivingWorld_Config
 
<LivingWorld.ParkingEntry> <ParkingType>RAMP_GA_SMALL</ParkingType> </LivingWorld.ParkingEntry>

Where did you find documentation regarding the <LivingWorld.ParkingEntry> element?

I don't see that in any documentation or the examples. What's it's purpose? All the documentation just shows the <ParkingType> element by itself.
 
The example above was based on my own reverse-engineering of the first public release of MSFS. Documentation didn't exist then. To my best knowledge, it still works, but I haven't tested it recently. ParkingEntry defines the types of parking spots the ParkingSpace definition will apply to.

What's the purpose of the ICAO code in "<icao>_LWcfg.xml"?
As far as I know, living world config file sets values for the whole region at once and more fine grained targeting is not available.
 
Back
Top