iniKyle

Hi Helmut, When you encounter this error, you can simply reselect the FMS screen you were previously on. If you continue to experience issues, please consider reaching out to Synaptic through their official discord for further assistance. Thanks!

Hi, Thanks for your feedback. I’ll take a look shortly and report back once I have more information. Thanks again!

Yes, I believe that wait time is to be expected. It’s most likely a console-related limitation, as I believe the process is much quicker on PC. That being said, I’m glad you were able to get everything working as intended! Enjoy your flights. Thanks!

Hi Mark, Sorry to hear that the troubleshooting steps you’ve tried haven’t yielded any results. I’ll ask around with the team and keep an eye out for any other users reporting the same issue. As for your feedback regarding the iniManager, I’ll pass that along to the team for further consideration. Thanks!

Hi, Definitely a great suggestion! I will forward this to the team for future considerations. Thank you!

If you open up the file structure, do you see this?

Hi Mark, I’m not sure why it isn’t showing on your end. I tested it with another member of the team, and both of ours are working correctly. Could you try uninstalling and reinstalling the scenery to see if that resolves the issue? Thanks!

Hi, Xbox does not currently support Navigraph Sim Data, so your NAVDATA should be set to SIM DEFAULT. You are correct that this is why your FMS flight plan is not transferring over. Once your aircraft is set to SIM DEFAULT data, the only way around the AIRAC mismatch would be to upgrade your SimBrief AIRAC to the current cycle. Unfortunately, I’m not aware of any free alternative at this time. I hope this helps clarify things. Thanks!

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!