iniKyle

I’ll definitely take note of your suggestions and pass them along to the team. I can’t make any promises, but I’ll make sure your feedback is heard and shared with the appropriate people! Thanks André!

Hi, I’ve seen this issue before (unrelated to iniBuilds), and it appears to be caused by missing textures. In those cases, a fresh installation of GSX has resolved the issue. Hopefully, this helps! Thanks!

Hi everyone, Please keep in mind that using any sim update BETA can result in unforeseen issues, as these versions are still undergoing testing. As someone else mentioned, a fresh install may resolve the issue. If that doesn’t help, you may need to consider rolling back to a stable version of the sim. Thanks! *EDIT I hadn’t realized that SU6 had been publicly released, my apologies! Please try a fresh installation and let me know if that resolves the issue. Thank you!

Hi everyone, Apologies that it took us so long to respond. Although I'm not very familiar with how the sim runs on Xbox, I can suggest a few troubleshooting steps. Do you have the scenery downloaded, or are you streaming it? A complete reinstall should hopefully resolve any major issues. Thanks!

Hi, Sorry to hear that the troubleshooting method mentioned above did not work. If you're willing to run through some more troubleshooting with me: rename your old community folder to something like community1, launch the sim (it will create a new community folder) once at the menu, shut down the sim place the a340 folder inside the newly created community folder, launch the sim. Let me know if that works. Thanks!

Ok, thanks. Just wanted to varify we weren't missing a step in the troubleshooting.

Hi everyone, I have confirmed with the team that we have submitted an update for the Skyvan as part of a broader round of aircraft and avionic updates. This issue, among others, has been addressed and should be resolved as part of that update. Although I cannot provide a definitive timeline for the update at this time, we want you to know that we genuinely appreciate all of your feedback. We are continuously working to improve our products and provide the best possible user experience. Thanks!

Hi, If you're willing to run through some troubleshooting with me: rename your old community folder to something like community1, launch the sim (it will create a new community folder) once at the menu, shut down the sim place the L1011 folder inside the newly created community folder, launch the sim. Let me know if that works. Thanks!

Hi Alex, On Xbox versions of Microsoft Flight Simulator, real-world and custom airline liveries are subject to strict trademark, copyright, and platform security requirements. As a result, official or third-party branded liveries must have the appropriate legal licensing agreements in place and be officially distributed through the in-sim Marketplace. Hope this helps. Thanks!

Hi Andy, Sorry to hear you’re having issues with the A340. As a troubleshooting step, would you mind reinstalling the aircraft directly into your Community folder, without using add-on linker, to see if this helps resolve the issue? Thanks!

Hi, Sorry to hear you’re having a less than ideal experience with our London City scenery. If you could elaborate on the issues or concerns you’re experiencing, I’d be happy to forward them to the team for further evaluation. Thanks!

Hi Faisal, Just wanted to add one more troubleshooting tip, in case it hasn’t already been covered. Can you confirm that your throttle is assigned to “Throttle 1 AXIS” in the MSFS settings? There is a second option called “Throttle 1 AXIS (0-100%)”, which should not be used. Thanks!

Hi André, I’ve noted this and passed it along to the team. Thank you for taking the time to share your suggestions with us, we really appreciate your feedback. Thanks again!

Hi, Just a quick follow-up: this issue was resolved in v1.0.4. Please make sure your aircraft is updated to the latest version. Thanks!

Hi, Sorry to hear you've been having issues with the A220 capturing the glide slope. I personally haven't encountered this issue, despite completing over 30 flights. The A220 should automatically switch from the magenta diamonds to green diamonds once it has captured both the LOC and GS. I've attached a screenshot as an example. If you haven't already, I would also suggest joining the Synaptic Discord, where the community may be able to offer some additional support and troubleshooting suggestions. Thanks!

Hi André, This is a great question! I’ll forward it to the team for clarification and a response, as I’m not entirely sure myself. Thanks!

Hi, I've noted this for the team to look into. Thanks!

Great news, enjoy your new aircraft!

Hi, Once you enable boarding through GSX, I believe that's what may be causing the issue. Try loading the aircraft manually before starting the boarding process through GSX. Let me know if this resolves the issue. Thanks!

Hi, This is great news! I'm glad we were able to troubleshoot this together and get you back up and running. Enjoy DFW and, most importantly, enjoy your flights! Thanks!

Hi, As zbrainlezz mentioned, this would ultimately be best brought to the attention of the Working Title team through the MSFS forums, as they would be in the best position to investigate the issue. Thanks!

Hi, As this is a Local Legends collaboration, I don't believe we'll be releasing a paint kit for this aircraft. That said, this may be something worth bringing up on the MSFS forums, as Microsoft/Asobo ultimately controls the availability and implementation of features related to the Local Legends aircraft. Thanks!

Hi, From my understanding, if you disable the aircraft through the MSFS Marketplace, there shouldn't be any files left behind. You could take it one step further and delete the WASM folder as well, just to ensure everything has been removed. Once that's complete, install the aircraft through iniManager, which should place the aircraft directly into your Community folder. Let me know if that helps! Thanks!

Hi, As this is an MSFS "Local Legends" aircraft, I don't believe it will be available through iniManager. That being said, while browsing the MSFS forums, I came across a user who was able to resolve a similar issue using the following method: "The issue appeared to be caused by the payment method I was attempting to use and was fixed by changing the method of payment." Hopefully, this helps resolve the issue on your end. Let me know if you're able to get it sorted. Thanks!

Glad to hear it! Hopefully, it gets approved quickly and resolves his issues. Thanks so much for your help!