• 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.

MSFS24 Remove Power Pole

Hi again:

To be clear, rhumbaflappy's example package (generously created and attached above) for LFET scenery exclusion, 'works' ...loaded by itself.

https://www.fsdeveloper.com/forum/threads/remove-power-pole.461070/post-941410

fsdev_oldpat_lfet_rogue_powerpole_msfs24_devmode_load_rhumbaflappy_my_lfet_project-1-jpg.100492


Once I load (also- or instead-) any of Pat's LFET builds, the rogue Powerpole appears as seen in the original OP post- and in my screenshots.


I am glad that Pat's current build of his LFET scenery fixes the issue in the OP for this thread for his- and others'- MSFS 2024 installs. :)


But, for unknown reasons, Pat's current build of his LFET scenery does NOT fix the issue in the OP for this thread on 'my' MSFS 2024 install. :scratchch


FYI: I have not previously had occasion to examine or manually edit, my "active" Content.XML.

Nor have I previously had occasion to examine or manually edit, the list in DevMode Menu > Tools > Package Reorder Tool dialog.


When I loaded my "active" Content.XML, I was surprised to see old add-on entries were retained after emptying \Community2024 folder.

When I loaded my DevMode Menu > Tools > Package Reorder Tool dialog, I was surprised to see only MSFS 2024 default entries were listed.


This might otherwise require considerable study / testing to sort out, with no guarantee of resolving the issues I now see in MSFS 2024.


So, at this point I am inclined to assume my MSFS 2024 install has become internally corrupted somehow, and may require a reinstall.

I do not have time available to do that right now; but after I reinstall MSFS 2024, I shall retest the latest build of LFET, and will report back.


It is my hope that, at that time, I shall see Pat's LFET continues to "cut the mustard" as one of the finest GA airport add-ons near Dijon. :cool:

https://en.wiktionary.org/wiki/cut_the_mustard


[EDITED]

PS: The assumption my MSFS 2024 install has become internally corrupted should not be seen as a consequence of loading any LFET add-ons.

Rather, it may be a culmination of changes to my installation over time, as MSFS 2024 controller config "cloud" data I/O has been problematic.


And I may have inadvertently tested robustness of the VFS sub-system by use of redundant symbolic link I/O in my \Community2024 folder.


The latter may have been "the last straw" that 'broke the back' of MSFS 2024's W.I.P. struggles to access data in my NTFS-ADS format files. ;)

[END_EDIT]

GaryGB
 
Last edited:
GaryGB said:
Hi Pat:

The latter DM'd Scene.XML compared to the prior DM'd Scene.XML in NotePad++ with Plugins > XML Tools > PrettyPrint > Indent on ...show:

* Both have 3436 lines.

* I have not yet compared them further aside from confirming they do not place the rogue Powerpole by GUID


FYI: In MSFS 2020 that object is from:

C:\Users\[user_name]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\scenery\Global\Asobo_Props/Asobo_Props.BGL


MCX ID's the object as:

Friendly Name: Streetlamp_Wood02

GUID: {EC72F2F6-E120-689E-8693-B7C1D9F7F72C}


IIUC, one cannot confirm it is placed by the MSFS 2024 native LFET "generic airport" in scenery/0601/apx49150.bgl, inside:

C:\XboxGames\Microsoft Flight Simulator 2024\Content\minimalcache\fs24-fs-base-genericairports\minimal.fsarchive


My tests thus far suggest the rogue Powerpole: Streetlamp_Wood02 - GUID: {EC72F2F6-E120-689E-8693-B7C1D9F7F72C}

...is mistakenly placed by either MSFS 2024 default scenery, or an add-on in the Microsoft section of the MSFS 2024 'system' folder chains.


BTW: I had not yet mentioned that since 2025 there are reports of an ongoing unresolved issue with display priority of certain such content in MSFS.

https://devsupport.flightsimulator....rriding-with-my-streamed-airport-add-on/14590


A Google search using this query string:

Code: 
microsoft-scenery-gliders-worldwide-part1 priority

...may help explain this (and other MSFS display priority scenarios).


Use of a XML Package "Hint" may help in 'some' situations, but reportedly one must still manually edit layer assignments in Content.XML. :banghead:


So, I also plan to test if DevMode Menu > Debug > Terrain > Debug Shapes > Vector Data Debug > Draw Package Name:

"microsoft-scenery-gliders-worldwide-part1"

...seen at LFET, has an actual impact on scenery display priority at LFET


https://www.fsdeveloper.com/forum/threads/microsoft-scenery-gliders-worldwide-part1-solved.459562/

I also plan to test manually editing \Community2024 add-on layer assignment positions down to the bottom (higher priority level) of Content.XML.


More to come as time permits. ;)

GaryGB
Click to expand...
I would like to help you further, but I think this is beyond my expertise.
I have posted several messages on flightsim.to (on the forum and my page) to see if others are in the same situation.
As soon as I get a reply, I will let you know.
 
You must log in or register to reply here.
Back
Top