Bob Scott

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

There's a handy utility called DIView on the Leo Bodnar website that shows you the hardware-level inputs your HID devices are making. I would get that and monitor the yoke while exercising the buttons/axes, and see if those spurious inputs are, in fact, coming from the controller. If they are, and occur randomly without moving the yoke, then I'd try re-flashing the firmware (see: https://www.ifixit.com/Guide/Flash+and+re-install+the+firmware+of+TCA+Yoke/177099 ) If moving the yoke makes the button issues appear, then I'd strongly suspect a loose connector or broken/pinched cable between the yoke head and the USB module inside the unit. That might be user-repairable. I've done mods and repairs on their joysticks a bunch of times, but haven't yet had occasion to open up my yoke.

Anyone else not receiving ILS/VOR on KATL? I can't get a localizer signal on any of the runways. Using v1.0.3. Tried reinstall, cleared scenery indices, disabled Navigraph data...no luck at all.

I see he's already got it in the database.

So has anyone using PSXT sent Nico the tblo.zip file for Orbx KATL yet?

See: https://www.avsim.com/forums/topic/696911-pmdg-operation-center-2

Read through this thread: https://www.avsim.com/forums/topic/695375-pmdg-oc2 There's discussion of several .ptp file decompilers that will allow you to take a ptp file, decompile it, and manually install it into the sim. Cumbersome, but better than nothing.

My guess would be either the condition of the pavement is no longer suitable to hold a heavy aircraft, or they have installed elevated (e.g. lighting) structures there.

I think a data feed issue is best addressed with Balthasar at: [email protected]

"total reset and install" -- what exactly is that? Reinstall of Windows and everything else? Just the sim apps? Are you running a single PC or a networked config? Your Orbx installation issue might be an antivirus or other security software getting in the way. I'd also check your firewall settings when having interconnect issues. Have you set up your simconnect.xml, simconnect.ini and (if running remote) simconnect.cfg files properly? Have you installed all the legacy versions of the SDK in order (FSX, FSX SP1, FSX SP2, FSX Acceleration) from the legacy folder included in the P3D install? Many P3D add-ons use older simconnect versions for compatibility, so you need to install all of them, from oldest to newest (they exist side-by-side).

When you put hardware on a different PC (or the same PC with a fresh install of the OS), Windows generates new GUIDs used to identify each hardware controller. It seems likely that the configs MSFS stored in the cloud are tied to the GUIDs on the old machine. Try binding something like an unused button to something innocuous like smoke on/off and see if the MSFS controls UI recognizes the input. If not, I suspect you'll need to rebuild your configs.

Our tech is investigating turning that off...it's boilerplate intended for those that use the forum software for a storefront.

I'd say something like the Virpil Aeromax stick looks promising. Don't have one personally, but I like what I see. Left and right stick heads available, too.

Airside: Streetside:

go to support.pmdg.com, create an account, and then login and create a ticket for your problem.

Probably best to ask this on PMDG's support forum, or via a support ticket on their site. Which airport? I think the FMC is only populated with airports having runways long enough for a 777.

Nico is on vacation until June 8th, and so I'd surmise that the airport database hasn't yet been updated for the new Orbx KATL.

AFAIK, in MSFS 2024 GSX does not yet replace the jetways with GSX versions like it did in FS2020 and P3D. The jetways are configured by the scenery developer and generally rely on the door placement coordinates in the aircraft.cfg. GSX can change the position of the acft only.