iniKyle

Hi, I’ll speak with the team regarding the tug parking spot. Additionally, the GSX jetway report indicating that there is no jetway available to connect to is a limitation within GSX itself. We’ve reached out to the GSX team for clarification, as we’ve done everything we can with the development tools provided to us by GSX. Thank you!

I believe we’ve found the issue. The default navdata for Microsoft Flight Simulator 2024 is currently on AIRAC cycle 2608. The mismatch between the AIRAC cycles used by SimBrief and the aircraft is causing issues when importing flight plans. Thanks for your patience while we tracked this down! *NOTE As far as I’m aware, the only way to resolve this would be to update your SimBrief navdata to the most current AIRAC cycle, which requires a paid subscription.

Hi Mark, If you refresh the page, the configuration will appear. Thanks!

That's a great suggestion. I will pass that along to the team for future consideration. Thank you for your feedback!

Hi Alex, Glad you were able to get the 400 resolution maps working. I’ve also noted the issues you’re experiencing with the 1200 resolution maps. Airfield diagrams will be available in a future update, although I’m not entirely sure when at this time. Thanks!

Hi, Believe it or not, this is a real “quirk” of the A220. It can struggle to properly track the LOC until you reach the FAF (Final Approach Fix). I hope this explanation helps! If you still feel like you’re experiencing issues, you can always check the Synaptic Discord, where they may be able to provide further troubleshooting assistance. Thanks!

Hi, Everything is showing correctly on my end, as well as for another team member. If you notice that the scenery configuration is not appearing, please try refreshing the page in the iniManager. Thanks!

Please let me know if that works. Thank you!

Hi, I believe this issue was addressed in an update quite some time ago. My iniManager is working as intended, and I’ve attached a screenshot for your reference. Thanks!

Unfortunately, at this time, I cannot provide any further details. Please keep an eye on our usual social channels for news and the changelog when the update is released. Thanks for your understanding!

Hi David, I’m very sorry to hear you’re having issues with the A350. If you’re willing to do some troubleshooting with me, I’d like to suggest the following: Make sure the simulator is completely closed. Locate your Community Folder. Rename your Community Folder to Community1. Relaunch the simulator. This should create a new Community folder. Once you reach the main menu, close the simulator. Move the A350 from Community1 into the newly created Community folder. Launch the simulator again. Let me know if this helps get the aircraft into a stable state. I have a feeling there may be something within your original community folder that is causing the issue. Thanks!

Hi everyone, This is a great suggestion, and I’ll make sure to add it to the list. While I can’t guarantee anything, I’ll certainly pass it along to management for consideration. Thank you!

Hi, We’ll have more information regarding the A350 v2 soon! Thanks for your understanding and patience.

Hi, After chatting with some of the other team members, I’m wondering if your SimBrief and simulator data may not be matching. Could you confirm which AIRAC cycle your SimBrief is currently using? Thanks!

Hi, Definitely a great suggestion and a nice quality-of-life improvement! I’ll forward this to the team for future consideration. Thank you!

Hi, This was the best available reference material the team had access to when developing the aircraft. If you’d like to see other variants represented in the future, I’d suggest bringing it up on the official MSFS forums. Thank you!

As much as we’d love to do that, ultimately, the decision comes down to Microsoft/Asobo. You could always bring it up with them on their official forums and see what they have to say! Thanks!

You’re on a roll, haha! I’ve logged this with the art team for further investigation. Thank you again for taking the time to report it!

Hi, Thanks for pointing this out! I’ll forward this to the art team for further investigation. Thank you again for taking the time to bring this to our attention!

Hello, This has been logged, and the team is currently investigating the root cause. Thank you!

Hi, Thanks for the feedback. We really appreciate you taking the time to share this with us! If you’ve already reported it on the Synaptic Discord, hopefully they’ve logged it as an issue and will be able to investigate it further. Thanks again for your time and support!

Hi Sam, Glad to hear you’ve been enjoying the 707! Our art team had access to and used this aircraft as a reference during development. I’ve attached some photos for reference as well. Hope this helps, and thanks again!

Hi Carl, Thanks for your help with the troubleshooting. I’ll forward this over to a team member with an Xbox and have them test it. I’ll report back once they’ve had a chance to investigate. Thank you again for your time and help!

Hi Carl, Sorry to hear you’re experiencing issues with the A350 on Xbox. My first suggestion would be to uninstall and reinstall the aircraft through the in-game marketplace, as this can sometimes resolve issues caused by corrupted or incomplete files. Let me know if that helps. Thanks!

Hopefully they can track down the issue. Personally, I haven’t experienced any issues with this behaviour, and I’ve completed around 30–40 flights now. Could a keybind possibly be causing the issue? Do you have any keyboard keybinds assigned to roll, yaw, or any other flight control inputs? Thanks!