iniSteven

Hi all, understand that it's disappointing that we've removed the cabin packs so just want to post an explanation here. The changes made to the model to reduce node and bone counts were really necessary, and not just for those on low-end hardware but even for those on higher end hardware, especially Intel and non-x3d chips. As mentioned in our post these changes significantly reduced stutters when looking around the aircraft or changing views, which of course benefits all of us even on the highest end chips, and also helps with stability as these stutters can effect that as well 🙂 Regarding the cabin packs, unfortunately these changes broke them completely, and they were already very difficult for us to maintain as any minor changes to the interior 3d models had to be repeated manually for every cabin pack across every variant. With this change, it was a bit of a final straw and we've decided that the manpower needed to maintain them is simply not sustainable for us, and these efforts are better focused on the core aircraft as well as our other upcoming projects. Hope that helps clear up the factors that led to our decision and can understand it wasn't taken lightly 🙂 -Steven

Hi, two things: 1) Please select either the Default or No Cabin variants. As mentioned in the NOTAM, support for the cabin packs is being deprecated in this update. 2) Please remove any conflicting addons from your community folder (zHUES core library is a common one). These will need to be updated by their creators for compatibility in 1.1.7

Hi, Please make sure that you are selecting either the Default or No Cabin variants, as mentioned in the NOTAM support for the Cabin Packs is being deprecated. Secondly, please make sure you do not have any conflicting addons in your community folder. zHUES core library being the most common we have noticed. These will need to be updated to be compatible with 1.1.7.

Hi, I'll take a look 🙂 -Steven

The Hydraulic Isolation switches are irreversible in flight. They must be reset on the ground by maintenance. See FCOM DSC-29-20 P 6/16: This is why it's guarded - once you press it, you can't un-press it.

This seems to be an issue in the newest Su4 beta build. If you restart the flight it should correct itself.

Hi all, are you all running in Su4? If so, keep in mind that it is a beta version of the simulator and new builds are being pushed quite frequently. As such, we cannot test and guarantee stability in all situations as there are multiple updates a week oftentimes. If you are unable to fly the aircraft, I would recommend returning to Su3 in the meantime until Su4 is finalized.

No, you need to try removing the custom scenery for RJAA if that is the airport you don't have SIDs and STARs at. The issue is most likely because there is an exclusion as part of a custom scenery package that is removing the procedures at the airport. This will effect ANY base navigation database whether it is Navigraph or Default. Do you have any other scenery items at RJAA? Did you maybe download some kind of scenery fix from flightsim.to? Personally, I am not able to reproduce the issue - and this is with the Drzewiecki RJAA installed - so there must be something on your end causing them to be excluded. -Steven

Are you using a custom scenery for RJAA? Try uninstalling it as some custom sceneries are excluding the default navdata as part of their exclusions. This will affect all aircraft using default navdata (even the navigraph base data), but not those using custom navigraph data. Our A350 and A340 have the option to use custom navigraph data, so they would not be affected by this.

That's because the A340 has two switches to control the Dome Light - there's the brightness switch as you are moving, and then a separate CTL switch that turns it on or off when the brightness switch is in DIM or BRT.

The crash and stress damage in the base simulator is extremely simple, and often triggered by the sorts of workarounds devs use to accurately simulate complex aircraft. We are not the only developer who encourage you to turn off the base simulation damage as they only harm complex aircraft - as proven by the issues here 🙂

Hi, are you using a custom scenery for your arrival airport? If so, try removing the custom scenery and see if the arrival works properly. If it does, you'll need to contact the scenery maker as they are excluding waypoints in their file. This problem only affects aircraft using default navdata. Aircraft with the option to use Navigraph navdata will be unaffected as this data is unaffected by scenery addons. -Steven

Hi, are you by any chance in Su3?

Here's my attempt at recreating a takeoff from youtube. I think we're pretty close. Absolutely nowhere near the 4000fpm you're claiming. Here's the data and their initial climb rate, vs. mine. I've included the full video of the takeoff for you. 2025-10-17 18-46-24.mp4

Yes, that's my suggestion as that is my personal experience. Microsoft have made a lot of improvements particularly in VRAM management in SU4 that should help with performance, and I have seen users complaining of mainthread issues in Su3 that seem to have been remedied in Su4.

I just did that and I wasn't even able to take off. This is at TOGA, 276.2t, 34c, standard pressure. MMMX runway 05L: I appreciate your passion for the aircraft, but we have to trust the book numbers and the word of real pilots that the model is accurate. -Steven

Hi islay, Both downloading and streaming are supported equally, so it's totally up to you 🙂 -Steven

Hi all, We've seen reports not just with our aircraft of people having degraded performance in Su3. I would suggest giving the Su4 update a try as I personally have experienced much better performance on my lower-end system 🙂 -Steven

Hi Solod, Any chance you can provide a video of this behavior? Doing some testing at the moment to see if I can re-create but in the meantime it's always helpful to have a reference of exactly what is happening 🙂 -Steven

Thanks for the feedback! At the moment we are working hard on A350 as well with fixes going into testing for some longstanding issues. That said, keep in mind the A350 and A340 are different planes and do have different FBW feels as described by our real world pilot advisors. That said, rest assured A350 is still getting all of the love and attention it deserves and you can continue to look forward to improvements as we continue to learn and grow as a company 🙂 -Steven

Hi all, we're still working on the fix for the ETE issues as it was not part of the 1.1.6 update. We're hoping to have it resolved in the next update which is going into testing shortly, but will keep you updated here 🙂

Because there are so many variables in a youtube video we can't account for. We don't know the weather, we don't know their airlines thrust calculations. I mean we don't even know what thrust was used in the original video of this thread! We have to the best of our knowledge replicated the by the book values of the manuals we have. If you can find hard data that contradicts us and provides us the necessary data to fix it, then we will do so. But if you can only find youtube videos, then there's nothing we can change as we aren't going to fiddle with the flight model based on vibes when we have actual performance tables and real pilots saying that our model seems accurate.

Hi, this is a known issue in the Su4 beta. Hopefully should be fixed in an upcoming build of the sim 🙂

Hi everyone, if you're having an issue where the aircraft systems freeze, but the clock is still running and there is no "WASM is now dirty" message in the console, please try and fly in Su4 and see if you still have these issues. -Steven

I would give Su4 a try and see if you continue having issues. If so, please let us know 🙂