Eddie

Of course! 🙂

Hello, We made changes to the model meaning all liveries must be updated. Most ones on the iniManager are updated to "1.0.1" which will work with the new update. Third party liveries need to be updated to fit the new version. Thank you

Thank you for the feedback. Will pass this along to the team.

Very odd. Initial load is the only one that should be taking a while. Clearing your WASM folders as well as re-installing the aircraft entirely may be a fix if you haven't already, same for you @Jure Let me know if re-installing resolves the issue. Thank you and apologies for the inconvenience!

iniManager does not allow clickable links. Also, there's nothing hidden. Searching "how to clear wasm folder iniBuilds" on Google will take you straight to the FAQ.

Hello Phil, Please update to the newest version (1.0.4, make sure you clear your WASM folder as well, guide here: https://forum.inibuilds.com/topic/24917-how-to-clear-the-wasm-folder/) and let me know if you are still experiencing issues. We sincerely apologize for the inconvenience; I understand dealing with these WASM crashes is not fun whatsoever. If your issue isn't fixed, please do let me know what lead up to the crash so that we can fix it going forward. Much appreciated and enjoy your weekend!

We have been very very consistent with updates, granted, first few were focused on bug fixes of course but we do sneak in features with every patch. 1.0.4 just came out, which is this week's second update. This is our flagship product, our creme de la creme; we have some great things planned for this bird and have so far shown a strong commitment on delivering much more. Whether you decide to purchase or not, it'll always be there ready for you; but to reassure you, yes, great things are planned, we will continue to fix issues and add features. Thank you for the support and question 🙂

Hello, For the MSFS2020 version there are no plans to add a cabin, no. Also, for future reference, please only communicate in English on the forums 🙂 Thank you

Thank you for the report! In the mean time, please try clearing your WASM folder if you haven't already. I've passed this along to the team nonetheless! Thank you and apologies for the inconvenience 🙂

Hi there, Can you please let me know what lead to this crash? What was the absolute last thing you remember pressing/doing? Thank you

Hello, Yes the A350 specfic RA callouts will be added in a future patch, hopefully soon 🙏

Should be fixed now with 1.0.3 🙂

Hello, Has this been resolved for you in the 1.0.3 update?

1.0.3 has resolved this issue 🙂

Hello, We fixed a mirroring issue with the later version that no longer causes this, that is why. We just released version 1.0.3, hopefully making its way to the marketplace as soon as possible. I would consider having your order transferred to our iniManager to avoid delays if you'd like 🙂

Hello! This has been noted and we are working on adding a toggle option in the OIS! 🙂

Hello, Thank you, I'll let the team know 🙂

Hello, Thank you, informed the team. 🙂

Hello, Thank you for the report. Passed along to the team! 🙂

Hello Thank you for the report. We are working very hard to resolve instability and a patch is coming Tuesday (tomorrow). with more detail on what’s going on. Thank you

Hello, Please make sure you have tried the following: Clearing your Scenery Indexes - To do that locate your folder by following the path below: MSFS 2020 MSFS 2024 Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS. This should solve the issue.

Hello! If I have come across this way, I do apologize as that was never the intention. Could you please point me to where you feel I have been passive aggressive? Thank you 🙂

Yep, we did indeed identify a TCAS issue; has been logged and we are working on a fix. Thank you so much for your patience.

We have indentified something similar and working on a fix already; so yes, avoid TCAS for the time being 😉 Thank you so much for your patience. I know this is not very fun having to deal with these issues. We're working on it!

Hello, Thank you for the report! We'll look into it with a fix hopefully very soon! 🙂