MSFS24 How to remove default helipads in MSFS2024?

WildLynxPilot · 13 Oct 2025

I have made an add-on called "Finland Medical Helipads" for MSFS20. It works fine also in MSFS24, but as MSFS introduced the helipads in MSFS24 there are some rooftop helipads that are covering the ones I have made. I have tried to find out how to remove those MSFS helipad structures, but haven't succeeded. Exclusion rectangles or polygons do not help. Does anyone have an idea on how to remove specific, individual MSFS helipads and their 3D structures?

GaryGB · 13 Oct 2025

I have noticed a recent increase of Helipads in MSFS 2024, but have not yet attempted to ID what default scenery type they are.

Since we have also recently seen a very large increase of 3D Photogrammetry buildings with collision-enabled attributes that could work as "platforms", one might wonder if a specific exclude of that scenery attribute type might merit testing ?

GaryGB

WildLynxPilot · 13 Oct 2025

Here is an example (from EFPT) with the MSFS version on top of my version. The MSFS version is a hand crafted 3D model, the markings on the helipad are different on different helipads, so not autogen of some kind. They appear on normal scenery and on photogrammetry scenery and they all look very similar (except for the markings).

GaryGB · 13 Oct 2025

Hi again;

I just checked the MSFS 2024 Docs and found this exclude parameter under Airport XML:

deleteAllHelipads

I am away from my FS computers presently but the Docs made it clear the Helipads are Elements within the airport XML, so an airport XML code wrapper must underlie the building with a Helipad.

I would examine the options for airports excludes to see if a check box is available in the exclude object properties.

Otherwise perphaps the raw individual airport XML might be edited to exclude these ?

Note that the Helipad is an Element that calls an AFD subobject which may still be a 3D meta-object.

Does your add-on have the Helipad built-in as part of the 3D model, such that you want to exclude the generic default Helipad types ?

GaryGB

GaryGB · 13 Oct 2025

Looks like our posts crossed on the server < must be Trump monopolizing the world bandwidth again ;-) >.

In the example shown, both Helipad types look good, but I like yours better.

So, IMHO, the default should go, but not sure if you will find a Helipad exclude option for an airport XML object in a Polygon; I'm thinking that should be an option via an Exclusion Rectangle which targets airport XML code.

GaryGB

WildLynxPilot · 13 Oct 2025

Aaah. Silly me. Now I found it! Simple. It is in the Delete section for the airport - just a tick in the box Delete all helipads and poof - the MSFS version is gone! Additionally it need an exclusion rectangle to exclude the 3D object. Thanks for your help - it was the deleteAllHelipads finding that put me on the track!

jgarnold · 11 Aug 2026

Hi Gary,

may I join?

I just found out about 24 and helipads.

I have (another) water airport (CAM9) built in 2020 but works in 2024 EXCEPT 2024 puts a helipad at my airport possibly using AI as in google satellite view it is possible to see very worn helipad markings on one of the floating docks even though Harbour Air advised me that although they own it and it used to be used, they don't plan using it again.

I assume that to prevent 24 placing a helipad I need to be the creator of the airport or should I be able to exclude it in my project airport?

GaryGB · 11 Aug 2026

Hi John:

IIUC, you refer to this Helipad in MSFS 2024 default scenery at CAM9 ?

msfs_2024_default_cam9_helipad-1-jpg.100576

Personally, I like having the Helipad at CAM9 as I would prefer to fly something like a Helo or the Astro / Jetson etc. to inspect scenery.

But, AFAIK, you could use a "deleteAllHelipads" XML 'attribute' in your custom airport at CAM9 to eradicate MSFS 2024's default Helipad.

As in any version of FS, your exclude project layer should have higher priority (aka "load later") than default scenery to be excluded.

That means In content.xml, your CAM9 exclude layer should be closer to the bottom of the layers stack in content.xml than the default CAM9.

MSFS 2024 currently limits on-screen display of Debug info in DevMode as to what method / files it uses to "place" default scenery.

AFAIK, if one chooses a proper 'Airport' option in a new project, Scenery Editor can access / extract hidden MSFS 2024 airport AFD XML code.

To update XML code you already have in your custom 2020 CAM9 you may wish to inspect 2024's default CAM9 airport XML also.

I would do a Google search via this query string:

Code:

MSFS 2024 SDK Docs Replace Airport

...as well as this query string:

Code:

MSFS 2024 SDK Docs deleteAllHelipads

...and review this info in MSFS 2024 SDK docs:

https://docs.flightsimulator.com/ms...rts_And_Facilities/Airport_XML_Properties.htm

This tutorial in the SDK also explains how to selectively exclude airport 'elements' rather than deleting the entire airport:

https://docs.flightsimulator.com/ms...s/tutorials/creating-or-replacing-an-airport/

IIUC, it is possible to force inclusion of MSFS 2024's more complete airport XML into a project if we avoid use of global <DeleteAirport> tag parameters that do not also have a "deleteAllHelipads="TRUE" 'attribute' within its <Airport> -to- </Airport> sub-element code section.

That way we use a multi-element deletion hierarchy in Scenery Editor to purge selected conflicting legacy (or copied default) airport assets.

GaryGB

jgarnold · 12 Aug 2026

Thanks Gary

Yes maybe some people might like having a helipad HOWEVER Asobo 'overwrites' my lifelike floating dock with one which doesn't have correct textures, only minor I guess but I don't like it.

Here is my scenery, not wonderful but closer to he real thing (2dn image) and better than Asobo (I will make mine more weathered gray)

GaryGB · 12 Aug 2026

I like the look of your version for the floating Helipad.

So, IIUC, you will replace the MSFS 2024 default CAM9 Helipad with your custom version ? :scratchch

[EDITED]

IIRC, MSFS Helipad placement normally has assigned Altitude, which may require a locally adjusted value AMSL for the floating dock surface:

https://docs.flightsimulator.com/ht...ilities/Airport_Definition_Properties.htm#h11

BTW: This refers to your prior threads elsewhere:

https://www.fsdeveloper.com/forum/t...he-elevation-of-default-terrain.456363/page-3

https://www.fsdeveloper.com/forum/direct-messages/3d-people.21102/#convMessage-88129

...but, what water surface Altitude AMSL in Meters or Feet, did you decide to assign at CAM9, considering the local IRL tidal range is 14 Feet ?

https://imageserver.fltplan.com/afd/Canada/09JUL2026/CAM9-2681.PDF

It would be fun if CAM9 had floating dock SimObjects with conditional display variables for positioning that rise / fall with the tide range. :idea:

Your floating dock might be made as a flat "boat" SimObject, with an attached Helipad:

https://docs.flightsimulator.com/ms...ular_SimObjects/SimObjects/Boats.htm#helipads

...with a AttachedAirport attribute:

https://docs.flightsimulator.com/ms...uration/CFG_Files/sim_cfg.htm#AttachedAirport

...and a HasMovingPlatform attribute:

https://docs.flightsimulator.com/ms...ation/CFG_Files/sim_cfg.htm#HasMovingPlatform

PS: I'm thinking this thread might do well to offer more info on where / how Helipad data is both implemented and disabled in airport XML.

Would you consider posting your CAM9 project airport XML here in this public thread as a worked example ?

Or perhaps you might do so in your original DM thread here...

https://www.fsdeveloper.com/forum/direct-messages/3d-people.21102/#convMessage-88129

...and then make some- or all- of that thread a new topic in the FSDEV public forums ?

[END_EDIT]

GaryGB

jgarnold · 13 Aug 2026

Wow Gary, my head is spinning reading your reply.
Firstly I changed the texture color and plank widths for the floating dock (helipad) to better match the real one

GaryGB said:
So, IIUC, you will replace the MSFS 2024 default CAM9 Helipad with your custom version ?

I don't know how to. I read the sdk docs on deleteallhelipads and couldn't work out if the attribute would work in my airport package plus it seems to be a new (2024) attribute and if so then I will need to publish TWO packages, 1 built in 2020 and the other with the attribute built in 2024. Currently I have one (main) package which works in both 3020 and 2024 and a small 'supplement' package for 2024 just to add some simobjects to populate the docks with DHC2 Beavers.

I used the default altitude of the water. I never set altitude. There may be a tidal range but I have never noticed it in 2020.

GaryGB said:
It would be fun if CAM9 had floating dock SimObjects with conditional display variables for positioning that rise / fall with the tide range.

Whoa up fella. I'm not into python? coding.

A lot of your reply is making my head spin.

John

Here is the code from the xml file for the airport (2020)

<Airport displayName="Vancouver Intl Water" groupIndex="38" groupID="1" groupGenerated="FALSE" name="Vancouver Intl Water" ident="CAM9" lat="49.17678733318485" lon="-123.16957009041663" alt="0.09839957673103" magvar="0.000000" trafficScalar="1.000000" airportTestRadius="2441.62810953994585" applyFlatten="FALSE" isOnTIN="FALSE" tinColorCorrection="TRUE">
<TaxiwayParking displayName="Harbour Air Dock 1" parentGroupID="1" groupIndex="2" index="2" type="DOCK_GA" lat="49.17701422559621" lon="-123.16835458651238" heading="90.961647" radius="15.000000" name="E_PARKING" number="2" suffix="NONE" numberMarking="FALSE" has3DMesh="TRUE" numberBiasX="0.000000" numberBiasZ="0.000000" numberHeading="0.000000"/>
<TaxiwayParking displayName="SEAIR DOCK 1" parentGroupID="1" groupIndex="1" index="0" type="DOCK_GA" lat="49.17699358728468" lon="-123.17060906091095" heading="103.489128" radius="15.000000" name="W_PARKING" number="1" suffix="NONE" numberMarking="FALSE" has3DMesh="TRUE" numberBiasX="0.000000" numberBiasZ="0.000000" numberHeading="0.000000"/>
<Runway displayName="East-West" parentGroupID="1" lat="49.17557934127676" lon="-123.16865649352003" alt="-1.34377869311720" heading="94.23078155517578" length="924.39453125000000" width="25.00000000000000" patternAltitude="304.79998779296875" surface="{067A3DE8-8ABD-49C5-B908-393670EF823A}" transparent="FALSE" number="EAST" designator="NONE" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.00000000000000" secondaryMarkingBias="0.00000000000000" groundMerging="TRUE" excludeVegetationAround="TRUE">
<Markings edges="FALSE" threshold="FALSE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="FALSE" alternateTouchdown="FALSE" dashes="FALSE" ident="FALSE" leadingZeroIdent="FALSE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE"/>
<Lights center="NONE" edge="NONE"/>
<RunwayStart end="PRIMARY" lat="49.17590433933132" lon="-123.17489190843743" alt="-1.33554384764284" heading="94.23078155517578"/>
<RunwayStart end="SECONDARY" lat="49.17529250045176" lon="-123.16248321989069" alt="-1.32784774061292" heading="274.23077392578125"/>
</Runway>
<Aprons/>
<PaintedElements/>
<ApronEdgeLights/>
</Airport>

GaryGB · 13 Aug 2026

Hi again:

It is always an option to complete projects solely according to one's own existing goals ...for both the workflow to be used, as well as for the outcome.

If you are inclined to consider MSFS 2020 SDK methods for use of the "deleteAllHelipads" XML 'attribute' in your custom airport at CAM9, that exclude type has been implemented for both MSFS 2020 and 2024.

My first reply to your initial post above can direct you to the info you may require to achieve your project goals.

If you are not yet certain as to where airport XML may have been utilized in your project, this would be an opportune time to acquire that certainty, by either reviewing the info I cited in my first reply to your initial post above, or by linking to your project file set, so we can examine the XML source files in order to answer your questions further.

GaryGB

GaryGB · 13 Aug 2026

jgarnold said:

Here is the code from the xml file for the airport (2020)

(Reformatted by GaryGB for easier proofreading via NotePad++ > Menu > Plugins > XML Tools > PrettyPrint > Indent Attributes)

Code:

<Airport
         displayName="Vancouver Intl Water"
         groupIndex="38"
         groupID="1"
         groupGenerated="FALSE"
         name="Vancouver Intl Water"
         ident="CAM9"
         lat="49.17678733318485"
         lon="-123.16957009041663"
         alt="0.09839957673103"
         magvar="0.000000"
         trafficScalar="1.000000"
         airportTestRadius="2441.62810953994585"
         applyFlatten="FALSE"
         isOnTIN="FALSE"
         tinColorCorrection="TRUE">
    <TaxiwayParking
                    displayName="Harbour Air Dock 1"
                    parentGroupID="1"
                    groupIndex="2"
                    index="2"
                    type="DOCK_GA"
                    lat="49.17701422559621"
                    lon="-123.16835458651238"
                    heading="90.961647"
                    radius="15.000000"
                    name="E_PARKING"
                    number="2"
                    suffix="NONE"
                    numberMarking="FALSE"
                    has3DMesh="TRUE"
                    numberBiasX="0.000000"
                    numberBiasZ="0.000000"
                    numberHeading="0.000000"/>
    <TaxiwayParking
                    displayName="SEAIR DOCK 1"
                    parentGroupID="1"
                    groupIndex="1"
                    index="0"
                    type="DOCK_GA"
                    lat="49.17699358728468"
                    lon="-123.17060906091095"
                    heading="103.489128"
                    radius="15.000000"
                    name="W_PARKING"
                    number="1"
                    suffix="NONE"
                    numberMarking="FALSE"
                    has3DMesh="TRUE"
                    numberBiasX="0.000000"
                    numberBiasZ="0.000000"
                    numberHeading="0.000000"/>
    <Runway
            displayName="East-West"
            parentGroupID="1"
            lat="49.17557934127676"
            lon="-123.16865649352003"
            alt="-1.34377869311720"
            heading="94.23078155517578"
            length="924.39453125000000"
            width="25.00000000000000"
            patternAltitude="304.79998779296875"
            surface="{067A3DE8-8ABD-49C5-B908-393670EF823A}"
            transparent="FALSE"
            number="EAST"
            designator="NONE"
            primaryLanding="TRUE"
            primaryTakeoff="TRUE"
            primaryPattern="LEFT"
            secondaryLanding="TRUE"
            secondaryTakeoff="TRUE"
            secondaryPattern="LEFT"
            primaryMarkingBias="0.00000000000000"
            secondaryMarkingBias="0.00000000000000"
            groundMerging="TRUE"
            excludeVegetationAround="TRUE">
        <Markings
                  edges="FALSE"
                  threshold="FALSE"
                  alternateThreshold="FALSE"
                  fixedDistance="FALSE"
                  alternateFixedDistance="FALSE"
                  touchdown="FALSE"
                  alternateTouchdown="FALSE"
                  dashes="FALSE"
                  ident="FALSE"
                  leadingZeroIdent="FALSE"
                  precision="FALSE"
                  alternatePrecision="FALSE"
                  edgePavement="FALSE"
                  singleEnd="FALSE"
                  primaryClosed="FALSE"
                  secondaryClosed="FALSE"
                  primaryStol="FALSE"
                  secondaryStol="FALSE"
                  noThresholdEndArrows="FALSE"/>
        <Lights
                center="NONE"
                edge="NONE"/>
        <RunwayStart
                     end="PRIMARY"
                     lat="49.17590433933132"
                     lon="-123.17489190843743"
                     alt="-1.33554384764284"
                     heading="94.23078155517578"/>
        <RunwayStart
                     end="SECONDARY"
                     lat="49.17529250045176"
                     lon="-123.16248321989069"
                     alt="-1.32784774061292"
                     heading="274.23077392578125"/>
    </Runway>
    <Aprons/>
    <PaintedElements/>
    <ApronEdgeLights/>
</Airport>

To ensure MSFS 2024 XML code is used, the above MSFS 2020 XML code should be compared with that created by a MSFS 2024 SDK Airport Replacement project as discussed above:

https://www.fsdeveloper.com/forum/t...fault-helipads-in-msfs2024.460350/post-941531

By loading your packages in MSFS DevMode Scenery Editor, you can add the "deleteAllHelipads" XML 'attribute' to your custom airport at CAM9, for both MSFS 2020 and 2024 packages.

GaryGB

jgarnold · 13 Aug 2026

Reading the sdk docs for deleteAllHelipads (see below) I think that I need to create a NEW Airport project in 2024 for CYVR and add the parameter there.
I have to assume that the helipads are part of the CYVR airport/scenery as it is adjacent to CAM9 if not which ICAO do I create it for?

I have in the past (in 2020) created projects for the same ICAO as existing so no problem there.

<DeleteAirport>

This a sub-element of the <Airport> element and is used to remove certain features from the area the airport occupies. Since most of the airports that are going to be edited are preexisting airports within the simulator, it is important to understand the behavior behind the <DeleteAirport> structure: when loading two packages that cover the same airport, the simulator will load both versions of the airport from each package, adding the data from each package together, rather than overriding one package with another. In the case that this is not what you want, you need to use this element to remove features from any previously loaded airport (including those that are defined as part of the base sim).

GaryGB · 13 Aug 2026

I will need to see where MSFS packaged CAM9:

* Part of CYVR, thus inside the same MSFS default airport section, and inside the same BGL as water RWYs for the land-based airport (unlikely, as it would have the same ICAO)

...or:

* A stand-alone airport separate from CYVR, possibly in the same BGL, but in a separate airport section, and having a separate ICAO

I may be able to import the MSFS 2020 default airport BGL to ADE for MSFS or Airport2Project, otherwise I may be able to decompile it using MSFSBGLXML.

Even if MSFS 2024 airports are "hidden", and CYVR / CAM9 'may' be "World Hub" Airports, most of the AFD XML code is likely identical to MSFS 2020 airport versions.

The goal is to preserve all airport features in the default XML code rather than accidentally omitting some AFD and Nav data with a global DeleteAirport element.

Then we can pick and choose in your CAM9, what we "Delete" from the run time instruction set for the default CAM9 airport (which is actually also still 'loaded' internally by MSFS' rendering engine).

If a proper 'full-featured' airport for CAM9 is copied via MSFS 2024 SDK Scenery Editor into the XML code with intent to replace or modify the default, we will see any differences from MSFS 2020.

https://docs.flightsimulator.com/msfs2024/html/7_Samples_Tutorials/Tutorials/Creating_Or_Replacing_An_Airport.htm?rhhlterm=replacing replace&rhsearch=Replace

https://docs.flightsimulator.com/ms...=deleteallhelipads&rhsearch=DeleteAllHelipads

[EDITED]

jgarnold said:
I read the sdk docs on deleteallhelipads and couldn't work out if the attribute would work in my airport package plus it seems to be a new (2024) attribute and if so then I will need to publish TWO packages, 1 built in 2020 and the other with the attribute built in 2024. Currently I have one (main) package which works in both 3020 and 2024 and a small 'supplement' package for 2024 just to add some simobjects to populate the docks with DHC2 Beavers.

PS: MSFS 2020 SDK did eventually add the "deleteAllHelipads" XML code option as did MSFS 2024 SDK:

https://docs.flightsimulator.com/ht...=deleteallhelipads&rhsearch=deleteAllHelipads

[END_EDIT]

GaryGB

GaryGB · 13 Aug 2026

jgarnold said:
Reading the sdk docs for deleteAllHelipads (see below) I think that I need to create a NEW Airport project in 2024 for CYVR and add the parameter there.
I have to assume that the helipads are part of the CYVR airport/scenery as it is adjacent to CAM9 if not which ICAO do I create it for?

I have in the past (in 2020) created projects for the same ICAO as existing so no problem there.

Hi again, John:

Just as background info on CYVR and CAM9 airports in FS...

FSX CYVR included CAM9 scenery but did not place a Helipad locally:

MSFS 2020 CYVR did not include CAM9 scenery, and also did not place a Helipad locally:

msfs_2020_cyvr_no_cam9_ade2020_alpha_21-jpg.100597

If you have not already done so, you may wish to preview the CAM9 Helipad and adjacent area in MSFS 2024 ...in this configuration:

DevMode Menu > Debug > Airports > Draw Debug (checked) > Debug airport override (checked) > Airport Coloring (checked)

I suggest initially spawning a flight in MSFS 2024 at the CAM9 Helipad in TopDown view:

cam9_msfs_2024_default_helipad_debug_floating_dock_info-jpg.100593

...then use Developer Camera to scan the vicinity for other Helipads to be excluded:

cam9_msfs_2024_default_helipad_debug_local_info-jpg.100594

IIUC, the on screen info shows that Asobo placed MSFS 2024 default Helipads via a hidden streamed BGL separate from CYVR airport code.

Notice as well that a MSFS 2024 Helipad "H" 'mast' aerodrome marker appears out in the Fraser River, but others only show as a Cyan Blue "H"

Next, I would repeat the procedure described immediately above in MSFS 2020.

Notice as well that a MSFS 2020 "I" 'mast' POI marker appears out in the Fraser River, but none show as a Helipad "H" 'mast' aerodrome marker or Cyan Blue "H"

Google says:

"AI Overview

In Microsoft Flight Simulator 2020, a Point of Interest (POI) marker with an "I" icon typically indicates an informational landmark, objective, or specific point designated during activities like bush trips or discovery flights. These markers highlight notable sights, cities, or airports."

If you attach or link to your CAM9 airport project we can load it in MSFS 2024 DevMode to test a "deleteAllHelipads" XML 'attribute' at CAM9.

Pending your reply, I'll plan some tests to see where / how MSFS 2024 SDK Scenery Editor writes the "deleteAllHelipads" XML 'attribute'

IIUC, you plan for your custom CAM9 project / package to replace Helipads from MSFS 2024 default, but also any from The_Joelster / Project_SCNE CAM9 packages at flightsim.to ? :scratchch

https://flightsim.to/addon/46192/cam9-vancouver-international-seaplane-base

If so, you may wish to also make excludes for any unique scenery in that package which differs from the default and your own scenery at CAM9.

GaryGB

jgarnold · 14 Aug 2026

Hi Gary After reading your response I looked closer and noticed that without my CAM9 airport, 2024 has a selectable airport "CAM9 HarbourAir Seaplanes Richmond (Yvr Sout" with only the H01 helipad selectable as a starting location and so the helipad is part of that airport and not CYVR.

Later I will attempt to add Asset Group AIPORT to my small supplement project which simply adds simobjects to my 2020 built CAM9 airport.

I am a bit over all of this as its just a small part of my scenery which is overwritten by an Asobo helipad.

BTW do you have 2024 and if so how much ram does your PC have? As they recommend 32gb for 2024 since it now streams more I will replace my 16gb with 32gb.

GaryGB · 14 Aug 2026

jgarnold said:
Hi Gary After reading your response I looked closer and noticed that without my CAM9 airport, 2024 has a selectable airport "CAM9 HarbourAir Seaplanes Richmond (Yvr Sout" with only the H01 helipad selectable as a starting location and so the helipad is part of that airport and not CYVR.

Later I will attempt to add Asset Group AIPORT to my small supplement project which simply adds simobjects to my 2020 built CAM9 airport.

I am a bit over all of this as its just a small part of my scenery which is overwritten by an Asobo helipad.

I examined the XML from your current VANCOUVER_INTERNATIONAL_WATER_AIRPORT_pReSP at flightsim.to in:

[path]\VANCOUVER_INTERNATIONAL_WATER_AIRPORT_pReSP\vancouver-int-water-airport-cam9\Scenery\airport-cam9-vancouver-intl-water\scenery\CAM9.bgl

You may wish to note that it appears as though part of its code extent may overlap that from MSFS default CYVR airport.

AFAIK, coverage extent for a "deleteAllHelipads" XML 'attribute' is the Test Radius (boundary) of a local <Airport XML section in the code.

https://docs.flightsimulator.com/ms.../Airport_XML_Properties.htm?rhhlterm=boundary

https://docs.flightsimulator.com/msfs2024/html/7_Samples_Tutorials/Tutorials/Creating_Or_Replacing_An_Airport.htm?rhhlterm=boundary boundaries

Thus it may be best to make sure CAM9 is an airport entirely separate from CYVR ...to prevent also deleting CYVR's separate Helipads. :yellowfla

Limiting the Test Radius (boundary) of a local Airport may impact its visibility distance like a LOD would, so CAM9 3D models may require LOD fixes. :idea:

jgarnold said:
BTW do you have 2024 and if so how much ram does your PC have? As they recommend 32gb for 2024 since it now streams more I will replace my 16gb with 32gb.

Yes, I do have MSFS 2024 running on 128GB of system RAM.

MSFS 2020 and 2024 both are efficient compared to P3D, but I think 32GB system RAM is entry level, along with 8GB VRAM on the video card.

AFAIK, part of the streaming mechanism allows for local context-specific download of only content in a nearby radius of the user aircraft.

IIUC, that effectively may place less burden on ones system RAM and VRAM due to smaller "chunk" size in loaded BGLs.

Additionally, less local disk storage / caching would be required on the end user computer

But I do dislike the idea of loading via web streaming, rather than from my purpose-built fast (and costly) computer hardware intended to do all loading.

If you are having run time rendering issues in DevMode Scenery Editor GUI at CAM9, I posted pertinent info in a reply to your recent DM.

I'll be interested to see how your Helipad exclusion works.

GaryGB

jgarnold · 15 Aug 2026

Hi Gary

I have at last created and built a 'supplement' package for CAM9 after some difficulties.

Firstly with the latest 2024 upgrade the thumbnail size has changed to 360 x 240. Apparently, it is in the release notes but I never read them. And would you believe the latest project samples contain thumbnails of the old wrong size. I can't believe Asobo.

Secondly devmode was automatically adding an extra '-' character to my package name eg (example) cam9-remove-helipad--blah. I had to manually remove it from folder names and inside xml files!

When I select object Delete Airports there isn't a parameter deleteAllHelipads so I selected Delete All .

And it worked. yay! Strangely H01 still display as a start point BUT if it is selected 'FLy Now' is 'grayed' out.

Anyway the scenery object has gone. Yippee.

[ADDED LATER]

I have found that deletallhelipads is part of the properties of the airport asset (stupid me) and so that is now 'under control' but it onloy seems to remove H01 as a selectable departure point and doesn't remove the scenery object.

I will get there eventually I hope.

GaryGB · 15 Aug 2026

jgarnold said:
I have found that deletallhelipads is part of the properties of the airport asset (stupid me) and so that is now 'under control' but it only seems to remove H01 as a select-able departure point and doesn't remove the scenery object.

I will get there eventually I hope.

IIUC, you refer to this for the Helipad "H" marker mast and AFD code exclusion; ...but the visible 3D model remains ?

https://docs.flightsimulator.com/msfs2024/html/2_DevMode/Scenery_Editor/Objects/Airport_Objects.htm

The latter (2) screenshots in my post above show a MSFS2024 source for the helipad (AFD ?) object:

"package: microsoft-scenery-helipad-worldwide

(file scenery/microsoft/helipad_plc/qmid_5_5_24.bgl)"

You may wish to review the above info via a Google search using this query string:

<CODE>

package: microsoft-scenery-helipad-worldwide (file scenery/microsoft/helipad_plc/qmid_5_5_24.bgl)

Perhaps the visible 3D helipad object "placement" is removed separately via a Polygon or ExclusionRectangle ?

https://www.fsdeveloper.com/forum/t...fault-helipads-in-msfs2024.460350/post-941569

GaryGB

MSFS24 How to remove default helipads in MSFS2024?

WildLynxPilot

GaryGB

WildLynxPilot

GaryGB

GaryGB

WildLynxPilot

jgarnold

GaryGB

Attachments

jgarnold

GaryGB

jgarnold

GaryGB

GaryGB

Attachments

jgarnold

<DeleteAirport>

GaryGB

GaryGB

Attachments

jgarnold

GaryGB

jgarnold

GaryGB

MSFS24 How to remove default helipads in MSFS2024?

Attachments

Attachments

<DeleteAirport>​

Attachments

<DeleteAirport>