Eddie

Hello, We're investigating as to why the configuration options do not show up. It is quite tricky because it shows up for all of us internally as well as, from what Ive seen, many others. I am in talks with our iniManager guys and we're looking into it. Will get back to you once I have an answer. Thank you for your patience.

Hello, Please try uninstalling it entirely and re-downloading the .exe from the website to go through the setup again. https://inibuilds.com/pages/inimanager-v2?srsltid=AfmBOootl0XV64WoMKmHTAOfhBSfpKPNcnqoGxw36HNS7peg7Z699JT8 Let me know if that resolves it. Thank you 🙂

Hello, Apologies for no replies here. Please reach out to direct support if you want a guaranteed quick reply from us. This is a community forum. We do of course reply to everything as fast as possible but sometimes some threads are missed here and there. Apologies for that. Thank you for sharing how you made it work. Enjoy!

Hello, Apologies for the lack of a reply here. As for the issue itself, this was noted already but I will prod the team regardless. Unfortunately, as you may have realised, the nature of updating the default aircraft is a lot different than ours. Thank you for your understanding.

❤️

Hello, Thank you for the report. How reproducible is this for you? Are you able to get the same result in the latest update? (1.1.2). Thank you 🙂

Hello I'm very sorry to hear your frustration with the aircraft. Fortunately, we do indeed care. We are working tirelessly to figure out a way to patch all these WASM crashes. It is not one. It is many different ones that happen in very very specific situations and absolutely not for everyone; what does this mean? Our testing team can not catch each single one. Impossible. Some feel easy to catch to the person affected but in reality, it isn't the case. The aircraft has been updated plenty of times, more and more features released and it has stabilised for the majority since long ago. I am not dismissing your concerns by saying this, but at the same time, it is important to stay fair. We're doing one big effort with the community to try to squash these WASM crashes once and for all (see linked post below). Again, I apologise for the inconvenience. We do care and we truly wish our customers didn't have to experience these crashes. Not sure why you'd think we want our customers to be angry and frustrated. Thank you

Hello all, We are doing a massive push on these WASM issues "once and for all". Our efforts are seemingly not enough for the small percentile of users that are facing these issues. Completely understandable if you do not wish to partake but please understand with your help we can squash these HOPEFULLY entirely. Like we've communicated in the past, some lingering WASM issues are mostly due to the way the simulator is currently handling WASM as a whole. Your efforts will also help us help MS/Asobo. We've created a dedicated server for this, please ONLY join if you are FULLY committed to help report the WASM crashes you experience and also committed to help our development team troubleshoot alongside you. This thread is now locked for more replies. Mentioned discord server: https://discord.gg/DuNYA4Mb Thank you very much!

Ok thank you, will escalate to the team.

Hello, Can one, or preferably, all of you try running the aircraft in the community folder on its own? You can do so by renaming your community folder to 'Community1' then copying the F406 in to the new empty community folder MSFS creates when you restart. This will rule out any other conflicting addons and we'll know for sure it's the aircraft causing this. We're unable to reproduce this internally so we'll need a little more data ^ Thank you 🙂

Hello, There shouldn't be a need for calibration from our side. Are you having issues with your peripherals?

Hello. We've tweaked this for the upcoming update 🙂

Hello, Forwarded to the team. Thank you!

Hello, We'll take a look. Thank you!

Hello, Thank you, forwarded to the team.

Hello, We aren't able to reproduce this in-house. Is anyone able to grab me a video of this happening to better diagnose what's happening? Much appreciated

Hello, I have not seen this while attempting to reproduce. What variant are you using? Or do all variants give you this issue?

Hello, Thank you for the feedback. Have made the team aware! 🙂

Hello, Do you mean visually on the livery or the ident. MSFS uses? When selecting the aircraft, you click modify (bottom left) and you're presented with the variant selections. One of the tabs is named "Identification". There you can change your registration. Let me know if this still doesn't help! 🙂

Hello, Forwarded this one to the team as well. Much appreciated! 🙂

Hello, Unfortunately there's not much we can improve here as the visuals of rapidly spinning objects in the simulator isn't always going to be accurate. I'll still forward this to the team and we'll take a look if we can improve it further. Thank you 🙂

Hello, Thank you for the report. I've forwarded this to the team 🙂

We'll continue to look into it and hopefully be able to get you an answer as to why this is happening. I am starting to lean towards it being some kind of binding issue but not ready to confirm that just yet. Your patience is very much appreciated and I understand this is frustrating issue to be having.

Hello. Thank you very much for the follow-up! That doesn't look right indeed. How often does this occur? If you zoom in with the camera, does the flashing stop?

Hmm, sounds odd. Seems indeed like a WASM crash. If you find the time, it would be very much appreciated if you could share some information regarding said WASM crash so we can look into it. You can follow this guide here: (first linked is for MSFS2024, second for MSFS2020)