Basic exclusions causes CTD

Bug Reports Airports & Sceneries
,
1

Maybe I am missing something, however, I read through the SDK documents regarding my goals and cannot determine the absolute minimums needed to do what I want to do.
My Goal:
Revise an airport as follows:

  1. Remove two fuel (Starts) that don’t belong.
  2. Remove badly placed Beacon.
    I do not want to recreate the entire airport. All other objects are acceptable.

If that 1&2 go well, I want to add missing buildings, proper fuel start, and some realistic parking spaces as I remember from working on this airport years ago.

Doing just the basics causes CTD when zooming into this airport from World Map.

STEPS:
Developer Mode. (SDK 0.21.1)

SDK
SDK926×551 80.2 KB

Start flight from a parking space.
New Project
Airport…
Add Exclusion Rectangle (for Beacon)
Add Airport (Exclude Starts)
Build without Errors.
Exit Developer Mode and sim. Copy Packages (airport directory) to Community folder. The only entry in my Community Directory:

D__MSFS 8_31_2023 8_58_23 AM
D__MSFS 8_31_2023 8_58_23 AM1274×921 23.2 KB

Start Sim.
Select World Map, zoom in towards that airport. get CTD.

This is the airport XML:
The only True are:
excludeBeaconObjects=“TRUE”
deleteAllStarts=“TRUE”
All other settings are False.

<?xml version="1.0"?>
<FSData version="9.0">
	<ExclusionRectangle displayName="Exclude Beacon" latitudeMinimum="40.23646413104872" latitudeMaximum="40.24096334368650" longitudeMinimum="-85.39247547584603" longitudeMaximum="-85.38659151561879" excludeBeaconObjects="TRUE"/>
	<Airport displayName="Delaware County Rgnl Airport" groupIndex="1" groupID="1" groupGenerated="FALSE" region="Delaware County Rgnl" country="USA" state="Indiana" city="Muncie" name="Delaware County Rgnl Airport" ident="KMIE" lat="40.24264775044914" lon="-85.39517290870360" alt="285.29687405750155" magvar="0.000000" trafficScalar="1.000000" airportTestRadius="2000.00000000000000" applyFlatten="FALSE" isOnTIN="FALSE" tinColorCorrection="TRUE">
		<Aprons/>
		<PaintedElements/>
		<ApronEdgeLights/>
		<DeleteAirport deleteAllApproaches="FALSE" deleteAllApronLights="FALSE" deleteAllAprons="FALSE" deleteAllFrequencies="FALSE" deleteAllHelipads="FALSE" deleteAllRunways="FALSE" deleteAllStarts="TRUE" deleteAllTaxiways="FALSE" deleteAllVectorPlacement="FALSE" deleteAllBoundaryFences="FALSE" deleteAllJetways="FALSE" deleteAllControlTowers="FALSE" deleteAllDepartures="FALSE" deleteAllArrivals="FALSE" deleteAllPaintedElements="FALSE" deleteAllLightSupports="FALSE" deleteAllTaxiwaySigns="FALSE" deleteAllILSs="FALSE" deleteAllTerminalWaypoints="FALSE" deleteAllTerminalNDBs="FALSE"/>
	</Airport>
</FSData>

Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000eb9427
Faulting process id: 0x0x4F98
Faulting application start time: 0x0x1D9DC2476D65AEC
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: c3638009-601c-4cc2-8c86-adbceb643f71
Faulting package full name: Microsoft.FlightSimulator_1.33.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

2

Hello @PropDust,

We will need you to provide us with the dump file and the scenery project, please.
Please see section 2) and 3) here : How to report a bug or crash

Regards,
Boris

3

Hello @PropDust ,
We’ve been able to reproduce the CTD, so we no longer need your project and dump file.
The CTD does not occur when the deleteAllStarts checkbox on the airport element is unchecked.

This will be reviewed.

Thank you,
Regards
Boris

4

Thanks for verifying this.
As a retired validation engineer, for SOCs (System on a Chip), we have to test all possible combination of inputs with outputs. So this surprises me that this type of issue is not caught during validation of the SDK. We ran regressions (a group of tests) with each release to verify existing “good” components are not broken by some other update.

The most concerning of this issue is that this simple design does not produce any warning or error during build.

Since you disabled the only “true” in delete Airport command, I am curious as to which other single delete commands will cause a similar event or which minimum number of true entries would not cause CTD.

So if I make deleteStarts TRUE with DeleteAirport and use DeleteStarts sub-element.

Referring to the SDK document How do I use <DeleteStart /> sub-element with <DeleteAirport />?

The type Enums do not match that of the fuel box. Available are runway, helipad and water.
Designator is also not related as it is displayed as GATE (PARKING 42 - FUEL BOX).

<DeleteStart type="" number="42" designator="NONE" />
<DeleteStart type="" number="46" designator="NONE" />

This is what I would expect to use:

<DeleteAirport deleteAllApproaches="FALSE" deleteAllApronLights="FALSE" deleteAllAprons="FALSE" deleteAllFrequencies="FALSE" deleteAllHelipads="FALSE" deleteAllRunways="FALSE" deleteAllStarts="FALSE" deleteAllTaxiways="FALSE" deleteAllVectorPlacement="FALSE" deleteAllBoundaryFences="FALSE" deleteAllJetways="FALSE" deleteAllControlTowers="FALSE" deleteAllDepartures="FALSE" deleteAllArrivals="FALSE" deleteAllPaintedElements="FALSE" deleteAllLightSupports="FALSE" deleteAllTaxiwaySigns="FALSE" deleteAllILSs="FALSE" deleteAllTerminalWaypoints="FALSE" deleteAllTerminalNDBs="FALSE">
		<DeleteStart type="FUEL BOX" number="42" designator="NONE" />
		<DeleteStart type="FUEL BOX" number="46" designator="NONE" />
		</DeleteAirport>

Regards.