Eank1954

Yeah, that kind of routing usually comes down to how the ground network is defined rather than anything the AI “decides” on its own. At airports like DFW, small differences between the real-world taxi logic and the sim’s navdata can lead AI to prefer ramps or connector segments that technically exist in the dataset but aren’t actually used operationally IRL. Once those links are marked as valid paths, the AI will happily use them even if human ops avoid them in practice. It could be coming from the base airport AFCAD/airport file, or from how the traffic injector interprets available nodes (FSLTL or otherwise). Sometimes even a single extra taxi link with lower cost can reroute the whole flow. On the systems side of things, similar issues show up in business tooling too — when routing logic or data mapping isn’t consistent across sources. In those cases people sometimes standardize data flows using platforms like integrate accounting software so all downstream decisions are based on the same structured dataset rather than conflicting inputs. If you want to test it, it might be worth checking the airport layout in a tool like ADE or whatever editor you use and looking specifically at that K → B transition. Removing or adjusting the E ramp connectivity usually forces the correct routing pretty quickly.

Thanks for sharing your insights, especially given your extensive experience with the L1011-500. It’s great to hear from someone with hands-on knowledge of these aircraft, and I totally get why the accuracy of details is so important to you. You’ve raised some really good points about the downstairs lounges and the lower deck space. I hadn’t realized that the -500 variants didn’t have lounges, and it makes sense that the cargo-only space would be more accurate for those versions. It’s good to clarify these kinds of details because, as you said, different airlines could have had different configurations, and sometimes even small inaccuracies can slip in. As for the lower access doors, I also wasn't aware that passengers never used those. It’s definitely something to watch out for in future previews and updates. Thanks for pointing that out! I agree, the color of the exhaust duct and other minor details like the screw heads can make or break the realism in a model, so it's great to hear that, overall, the Tristar is still holding up well in terms of visual fidelity. I’m sure many others who have worked with or flown on these aircraft share your sentiment about wanting it to be as accurate as possible.

The fact that you're getting the glideslope but not the localizer on the primary HSI definitely points to something being off. Normally, both should be picked up together, especially when the localizer frequency is tuned correctly, as it is in your case (110.90 for Miami Rwy 09). If you're getting the DME to the localizer on the standby HSI, but it's not appearing on the primary, it could be a couple of things: Radio Source Selection: Even though you’ve already selected the radio source on the button (INS/GPS vs. Radio), double-check to ensure it’s set correctly. Sometimes after an update, these settings can get reset or might require a manual override to ensure it's sourcing from the proper nav radio for ILS. HDG or CRS Setting: Verify that the heading or course setting on your HSI is properly tuned to match the localizer's course. If the course isn't set to the runway's ILS approach course (around 090° for Rwy 09), it won’t display the localizer properly. Software Bug: It’s also possible that this is still a bug related to the latest update. Sometimes, after an update, certain avionics or display systems take a bit of time to sync up, especially with navigation data. If it’s a known issue, I’d recommend checking the forums or patch notes to see if others are having the same problem, or if there's been any mention of it being fixed in a hotfix. Reset or Reboot: As a last resort, try rebooting the system or reloading the flight. It sounds simple, but sometimes avionics glitches can clear up with a restart, especially if they’re related to software syncing. I totally get how challenging this can be in low visibility, though! Hopefully, this can help narrow down the issue, but if it's still a bug, it might need to be addressed with the next patch. Let me know if you find anything that works!

Hi! iniBuilds has a support section on their website where you can submit a ticket or contact their customer service directly. Usually, there’s a “Support” or “Contact Us” link at the top or bottom of the page. If you’re having payment issues, it’s best to include details like the product you’re trying to buy, the error you’re seeing, and the cards you’re using (without sharing full card numbers). That way, they can help resolve the problem before the discount period ends.