Bob Scott

BTW, for those that are just now acquiring the P180, let me save you some work. There is a convoluted mess of old outdated info regarding the 2024 version and importing Simbrief flight plans. Discord at it's confusing worst, and the existing docs are no help, either. First the add-on did it natively, then they removed it in V2 in favor of a user mod, which no longer works with the newest release (v2.2.0). The "final" answer is to use the Simbrief/Navigraph EFB, view the latest Simbrief flight plan, and import it into the sim using the EFB. Also, the dementedmonkey mod to remote the FMC to a tablet was written for v1.9.0 and does not work with the current version.

OK guys, this is squarely in the realm of politics, and that dog don't hunt 'round here. Locked.

It's the departure end of 05L--that's where a stopway would be located. The question is why the pavement stub beyond the marked threshold (to the left of the acft in the OP's screenshot) isn't designated a stopway. Are you saying that the pavement has been demolished/removed? The latest Google Earth pic from Mar 2025 shows it there as in the scenery.

The FFX CitationX, Piaggio P180, and HondaJet are on sale, US $17.50 (30% off) through June 17th at 10:00 PDT (17Z) in the MS Marketplace. AFAIK, each includes both MSFS 2020 and 2024 versions (the CitationX and Piaggio do, I believe the HondaJet does also, but I'm unsure as I don't have that one).

All it does to the sim is install packages from their online store into your community folder. All that's needed to remove them is to delete the product's folder in the community folder. Outside the sim, it serves as an online storefront for their products.

Using a VPN? If so, try without it, or connected to a different VPN server outside Canada. I remember seeing multiple posts about issues with a VPN in Canada...can't remember if it was PMDG or someone else, but it suggests one or more of the anti-spam services blacklisted a popular Canadian VPN.

For some reason, with this City Update, you have to exit the sim and restart after installing the update, otherwise it shows "Disabled-Not Available" after the install.

Interesting. Took some brown-belt level Google-Fu to find where they moved Content.xml in the Steam version, which for anyone interested is: C:\Users\[YourUsername]\AppData\Roaming\Microsoft Flight Simulator 2024\[Your Xbox Name]\ That one is apparently the one being used, at least for activation/deactivation (but not for package order any more). I note with interest that all the packages from FS2020 are listed in there as well as the FS24 stuff. The packages I've disabled in FS2024 do have the active="UserDisabled" attribute set. But many of the FS20 entries show active="Activated", which now has me wondering what's getting loaded from the other sim, and whether it has any bearing on this issue.

I keep all of my third-party add-ons in a separate folder, with scenery organized by region, country, and (in the US) state. I move my Orbx sceneries there as well, and when active (via a symbolic link placed in the real community folder by Addon Linker) the Orbx Control Center finds them and updates them as if they were in the real community folder. Some others, most notably the iniBuilds manager, require you to move the scenery back to the Community folder when updating.

I'll probably add it to the Tips and Tricks forum after some more testing. So far everything is working as it should and several confirmation excursions have reproduced the problem when I add a bunch of Asobo streaming stuff back in. I haven't tried to separate out Asobo's streaming sceneries from the acft/liveries bundled into the premium edtions to see if only scenery has this unhappy effect, but I do suspect that's the case. As I understand it, after SU4 or 5 the Content.xml file was deprecated and is no longer used by the sim. I'm positive it's no longer used to establish loading priority, and after removing a whole lot of Asobo sceneries, they still appear in my Content.xml (but not in the package reorder tool), and the file has not been altered in months. I suspect that your utility is something of a placebo now as a result.

I don't have any of the Asobo stuff downloaded/installed locally, but I'd guess that the effect is the same. My guess, absent decent documentation, is maybe there's an internal navaid table overflowing as the result of too many active scenery add-ons, including the enabled streamed sceneries. I also noted that the VOR at KATL was inop while this was going on as well. I use the absolutely marvy Addon Linker utility to selectively activate the 3rd party add-ons used for each flight, so it's not a matter of 3rd party stuff...but the accumulation of Asobo stuff in all the World/City updates is substantial, especially for the Deluxe+ versions of the sim. Just the loading time improvement alone from doing a selective cull was worth the tedium of sorting through it all. Go into Marketplace -> My Library at the main menu, and you can select packages and disable an entire package or items within it there. A bunch of stuff can't be disabled for some reason, like Challenges/Missions (they're marked as such), but much of the stuff included in the World/City updates, as well as Asobo aircraft/liveries can be disabled individually. The Aviator edition has an absolute buttload of sceneries, airplanes and liveries for them, which might explain why I'm among the first to notice this.

I think I have it solved...turns out the issue is having too many streamed packages active. See detailed discussion here: https://www.avsim.com/forums/topic/697181-missing-ils-approaches-from-too-many-streamed-packages/

Spent an entire day working on a pernicious issue with the ILS not being received in any plane on any runway at the new Orbx Atlanta airport in MSFS 2024. It appears the issue is related to having too many Asobo FS24 streaming packages active in conjunction with the very object-intensive KATL scenery. The Orbx guys responded quickly to my support ticket, and showed me a LitteNavMap snapshot that verfied the ILS approaches are present in the scenery. I did the same, and yup, they're there. But none of my planes--default or add-on--could receive an ILS on any runway there. I cleared out the community folder, and still had the same problem, so it wasn't a conflict with a 3rd party add-on. Then I started progressively disabling the city and world updates, and the hundreds of airplanes and liveries included with my Aviator edition of FS24. At about the halfway point, the ILS came back...then I got out of the sim and restarted, and the ILS was gone again. Disabled some more, and the ILS was alive after a restart. Then I re-enabled a bunch of the disabled stuff and the ILS disappeared again. Then I selectively disabled batches of different packages to see if maybe there was a conflict specific to one or more of them, but no, the killer was pretty clearly related to the number of packages active, not any specific package. I watched resource usage throughout, and didn't come anywhere close to VRAM/RAM limits (~14GB out of 24GB VRAM, peak physical RAM ~34GB out of 64 GB, and swapfile a reasonable 15GB on a fast SSD with 2.5TB available). By going through and selectively enabling only the FS24 streaming packages that I actually use, I was able to stay under the threshold that triggered this issue. So my conclusion is that there is some internal limitation associated with keeping a very large number of streamed packages enabled, even though they came as part of the sim and are not used during the session. Oh, and startup times improved noticeably, from ~4 min to 2.5 min. The object count shown during startup now climbs to ~950 where it was over 3000 before.

KORD...FINALLY!!

Here's the official explanation: https://docs.flightsimulator.com/msfs2024/flighting/html/2_DevMode/Menus/Tools/Virtual_File_System_Information.htm