Eddie

Hello, Will bring this up to the team and we'll see what can be done. No promises however 🙂 Thank you

We have already reviewed the model and looked into what needs refinement. It is on our development plan but it will unfortunately not be anytime soon.

Hi there, I've forwarded this to the team. We'll take a look if there's anything we can do on our end 🙂 Thank you!

Hello, Thank you for your suggestions! We have a large list of scenery requests on this forum already (https://forum.inibuilds.com/topic/23417-scenery-wishlist/page/7/). We wish we could make every airport out there! 🙂

Hello, Before I move on to the other points you've brought up, I'd like to mention that we are already working on the VNAV system; said improvements will roll out as soon as they're ready. As for all the other points you've brought up; will have a conversation with the team in regards to each topic and will get a reply out to you once I have more information on each. I understand that issues not being fixed may come across as a lack of care however that couldn't be further from the truth. We love this aircraft and love what we have created. We strive for you all to feel the same way as evident by the frequency and richness of updates, even if they have slowed down now. As mentioned above, we are working on refining the VNAV behaviour as well as bring a slew of other fixes on issues that have been reported. The A350 has a good future! 🙂 In addition to that, we also understand skepticism towards our upcoming A340. It is important to understand we have learned a lot from you all, on our own and from the continued work on both the A350 as well as other projects. Ultimately, we want you all to be happy, which I'm sure you can understand is quite an unrealistic wish (can't please everyone!). I personally think we have delivered a wonderful aircraft and whatever major shortcomings were present were quickly looked into and fixed. I am not saying the aircraft is perfect, however, I think it's pretty damn good! Thank you for taking the time to type all of this up; will make sure the right eyes see it! This post will however be locked for clarity as the main message contains all we need. If you would like to add anything, please reach out to me directly @dectenor1 Have a lovely week everyone! 🙂

Hello, I've passed this along to the team. Thank you 🙂

Hello, This should now be resolved. Apologies for the wait. Enjoy 🙂

Hello, Glad to see it finally resolved! Sincerest apologies on the delay 🙂 It was indeed due to the LOD changes introduced with SU3. Enjoy!

Hello, Are you referring to the livery library on our iniManager? There should be 7 ULR Singapore liveries up right now. Let me know if not, preferably with a screenshot after you've typed "ULR" into the search window. Thank you 🙂

Hello. Unfortunately not much I can share at this time. We're aware and looking into the quickest and most effective fix. When it comes to VR, the issue goes deeper into a platform-level problem which naturally makes things take longer; that's why I am not confident in providing you false hope in the form of an ETA.

Hello, There should be a FedEx PW livery up on the iniManager now. Apologies for the wait. We'll look at adding more in the future. Thank you

Awesome! Also something to keep in mind, incase autosave didn't properly load, try a second time and always from a runway. Sometimes first load of the save may not initialise properly; a second one usually does the trick. Thank you 🙂

Hi there, Thank you for the follow-up. We'll take a look! Did you try loading in using the autosave? It's a quite a neat feature.

Hello, It will become functional in a future update 🙂

Hi there, Unfortunately the shader only works using MSFS2024 techniques, as indicated by the disclaimer. We appreciate your understanding and continued support 🙂 Thank you

Hello, We are indeed working on a fix 🙂 It is a priority and will be out as soon as possible! Thank you

Hello, Yes

Hello, Since the last communication from us we have still been unable to reproduce the issue. We need some more information. First of all, please ensure ALL assists are disabled in the MSFS options (auto mixture, crash simulation etc). Also, if you continue to encounter this problem, please enable Developer mode and check Debug -> Aircraft -> Wheels to see if there's any brake input present (see image)

Hello Carlos, Please try the following: As for the Simbrief issue, please ensure you have correctly put your ID into the EFB. You can try either ID (numbers) or username (letters) if one or the other fails. Thank you 🙂

Hello, Thank you for the report! Very sorry that you experienced this crash. It is very much worth it to keep autosave going in the background as it not only beneficial for you, but for us also as it helps identify WASM crashes a lot easier. I've forwarded your information to the team regardless. Thank you 🙂

Hello, What do you mean by other windows don't support it? When you click RALT + LEFT CLICK does the window of said screen not pop up for you?

Hello, Please try "re-streaming" the aircraft; may resolve the issue you're experiencing as things may have not loaded correctly since first initial-load. Thank you

Hello, Unfortunately, the situation is a bit more complex. SU3's beta has been around for a while, and the LOD change has been present for some time. However, given the nature of beta environments, we chose not to rebuild the LODs for the aircraft based on a system that was still subject to change, or potentially addressed by Asobo directly. This approach does carry the risk that the issue persists into the final release, potentially resulting in a broken feature, which is what happened here. While not ideal, we felt it was the most prudent path given the circumstances. That said, we are actively working on a fix, and it should be in your hands shortly. Thank you for your and everyone else's patience 🙂

Via Options/Assistance options/User experience, and turn off “aerodynamic visualization (CFD)" Either ALT+5 or ALT+6 should disable it by default - the keybind can be configured via the settings as well.

Hello, This is a MSFS setting that can be disabled by pressing ALT+5. It can also be disabled via the settings; "Aerodynamic Visualization"