iniSteven

I can't say I'm sharing your experience, I'm currently getting ~90fps on the ground in the A350 in Su4. I also can't see the photo you've posted of the A350 fps, only the Fenix. Could you repost it? It would help to diagnose what might be hurting your FPS. -Steven

All of the improvements we made for performance have been applied to both the 2020 and 2024 versions of the aircraft. None of the changes we made for the sake of performance were 'only' applied to 2024.

I take it you didn't read all your NOTAM's before you flew 😉 These waypoints are an issue IRL as well. The correct procedure is to plan direct from MUDOT to UNSEK when flying eastbound.

The reason the OIS is supported by touchscreens is that it's coded in JS and runs outside the WASM module of the aircraft. the MFD, as a core part of the aircraft avionics, has to be part of the WASM module and it is not possible for these screens to be controlled by a touchscreen.

Hi, the only way to fix this is to increase your texture resolution. There is nothing we can do to 'exclude' the airport navigation texture from being reduced in size by this setting.

Hi all, you can now download the A350 terrain data from the inimanager if you have trouble downloading it within the sim🙂

These things would have had to have been installed by the user in the first place. So of course as with any 3rd party modification we can only say that they need to be removed in the user added them 🙂

Thanks Rerem, I've found the issue. If you're on the NEW WAYPOINT page and press LSK R5 the key BELOW return, it crashes. I've passed it on to the team.

Hi, could you provide the full flightplan you tried to enter? And is this repeatable or it just happened once? Were you on Navigraph or Sim Default navdata? -Steven

Hi all, this issue happens when the aircraft doesn't fully initialize, and it's been an issue with the Su4 beta primarily. It can be rectified by restarting the flight - some users have reported that waiting a few moments before pressing "shift-c" to enter the aircraft helps make sure its initalized.

Are you on the Su4 beta? Runway and Air starts are broken in the beta at the moment.

Can you confirm that you're running a compatible livery?

The author of the ACA livery will need to update it to be compatible with the newest version.

Are you sure the weather isn't just getting colder? Aircraft perform better when the air temperature decreases.

No worries, glad I could help 🙂

Hi, please try restarting your flight. This issue occurs if the module doesn't fully initialize, and it seems to be more common in the Su4 beta.

Hi, please try with the addon scenery removed and see if the waypoint is correctly placed. If the waypoint is correct without the scenery installed, then you need to contact the creator of the scenery as there is an issue with the exclusions within the scenery. Many sceneries ported from 2020 to 2024 have this issue, and the only fix is for the original creator to update the scenery to fix the error.

Hi all, this issue is caused because you have something in your community folder that is incompatible with the aircraft. 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 the low-res texture pack as well as any conflicting addons from your community folder (zHUES core library is a common one, it needs to be updated if you have it).

Hi all, if you have this issue it is because you have some kind of incompatible file in your community folder. 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 the low-res texture pack as well as any conflicting addons from your community folder (zHUES core library is a common one).

It's doesn't always happen, but there is an issue in Su4 where the WASM doesn't always fully initialize. Often restarting the flight fixes it, but sometimes you have to restart a few times to get the WASM package to fully initialize.

Hi, can you confirm your livery has been updated to the newest version? -Steven

Hi all, as mentioned in the update post here, the cabin packs are being retired and will no longer work.

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.