Ground Services on passive aircraft (aka "AI traffic/live traffic")

Hello folks, I first may introduce myself - I’m Markus, a real life QA test
manager who currently is creating configs to be used by AIG on the legacy mdlx
aircraft models. By now I managed to get jetways and pushback working just
fine on these models which don’t feature nodes, still there seems to be
something magic happening on “generic” models which also is not working on
custom gltf models.

I included
the following lines on each aircraft with different coordinates: aircraft.cfg:



interactive_point.0=0, 37.93, -6.05, 0.02, 0, 0, 0, -86, 72, 16, 85, 3, -2, 33
interactive_point.1=0, -43, 5.2, 0, 0, 0, 0, 103, 0, 0, 0, 0, 0, 0
interactive_point.2=0, -19.5, 2, -4.8, 1, 0, 0, 90, 0, 0, 0, 0, 0, 0
interactive_point.3=0, 28, 1.93, -4.9, 1, 0, 0, 90, 0, 0, 0, 0, 0, 0
interactive_point.4=0, 46.3, 10.78, -8.18, 4, 0, 0, 45, 0, 0, 0, 0, 0, 0
interactive_point.5=0, -10, -54.59, -10.57, 3, 0, 0, -90, 0, 0, 0, 0, 0, 0


max_battery_voltage = 24.0
generator_alternator_voltage = 30.0
max_generator_alternator_amps = 400.0

It somehow seems like the GPU is the first service to be triggered to get the
others working, so I included the simplified electrical section used on mdlx
too. AIGs custom gltf aircraft got a modern, more in depth electrical section
which unfortunately does not work for lights when spawning in midair. Also on
these ones ground services are not triggered. On UI / as an user aircraft all
services work just fine.

could be missing here?
I’d appreciate any answer.

Hello Markus and thank you for the detailed question. Did you specify
something for the externalpower.N parameter?
What are the external power simvars reading? Regards, Sylvain

Hey Sylvain, we at AIG had to “revert” back from the modern FDE to the very
basic lagacy FDE (see the above values) to get lights working with the MDLX
airplanes in SU6. The native MSFS Models (glTF and modern FDE) have been
designed by our guys with these settings. ---------------- [ELECTRICAL] bus.1
= Name:AC_BUS_1 bus.2 = Connections:bus.1#Name:AC_ESS_BUS bus.3 =
Name:AC_BUS_2 bus.4 = Connections:bus.1#Name:DC_BUS_1 bus.5 =
Connections:bus.3#Name:DC_BUS_2 bus.6 = Connections:bus.4,
bus.5#Name:DC_BAT_BUS bus.7 = Connections:bus.4#Name:DC_ESS_BUS bus.8 =
Connections:bus.1, bus.3#Name:AC_CROSS_BUS bus.9 = Connections:bus.10,
bus.11#Name:HOT_BAT_BUS bus.10 = Connections:bus.6#Name:MAIN_BAT_BUS bus.11 =
Connections:bus.6#Name:ALT_BAT_BUS battery.1 =
Connections:bus.9,bus.10#Capacity:28#Voltage:curve.1#Name:Battery_1 ;
Battery_1 battery.2 =
Connections:bus.9,bus.11#Capacity:28#Voltage:curve.1#Name:Battery_2 ;
Battery_2 alternator.1 =
Connections:bus.1#iEng:0#RatedVoltage:28.5#Load:curve.2 alternator.2 =
Connections:bus.3#iEng:1#RatedVoltage:28.5#Load:curve.2 alternator.3 =
externalpower.1 = Connections:bus.8#RatedVoltage:28.5#Load:400 …
---------------------- In one of the olders versions (we are not fully sure
whiche one, but I guess it was before SU5), the same settings worked just

FLTSIM.N Entry found that seems to be the issue: ui_typerole seems to be
required for AI airplanes (tested with glTF). Tested with = “Commercial
Airliner” → worked Tested with = AI Traffic → did not worked

Hello I’ll have this dependency between services and typerole reviewed by
developers. It will be documented if it makes sense and modified otherwise.
Thank you for reporting the issue. Regards, Sylvain

For your information I have not tested the other common values for ui_typerole
that MSFS uses, they might work as well.

I like to create my own custom typeroles for planes. Please make sure to
include the ability to do this. As I approach a hundred or more of airplane
choices, I really need to use this field to help me find the planes I want to
fly (especially how poorly the hangar plane choice menu is implemented, where
only 3 of 4 rows capable of being visible are actually visible (and please
stop automatically jumping the selected plane to the top of the screen. I get
all confused.)).