Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

1.0.9 Performance issue

Featured Replies

Hi there, 

I flew 1.0.8 yesterday and performance was acceptable (AMD 7950X3D/64GB RAM/RTX 5090 32MB/ PImax Crystal light) in VR. Today I updated to 1.0.9 and it is simply unusable. I tested also (today) with the FSL A320 (which was the most demanding product on my computer) and had no issues with performance (so this is not an issue with my system)

I am not sure what Inibuilds meant with perfomance improvement on 1.0.9, but it is definitely a huge step backwards for me. Will have to hangar this bird until another update comes along (and hopefully comes with acceptable performance)

Finding the exact same thing. 1.0.8 was fantastic performance wise yesterday, 1.0.9 is not at all useable and sometimes even freezes my sim when loading the aircraft in. Tried loading the Fenix A320 and it loaded fine and performance was smooth as silk, so seems the issue is with the ini A350.  Running MSFS2020 in non-vr mode.

I have the same issue. It dips 20 FPS every 3 seconds, it is cyclic. I had no performance issues on any previous build (2020) except it was originally quite performance intensive it was manageable. If I ALT-G and watch the performance, this dip is constant and when the dip occurs it invokes a stutter. It is something internal in this build. I load in the Fenix A320 and the iFly Max, no issue.

 

Edit: I ended up completely deleting all traces of the A350 and a clean install and that has solved the issue. Indeed I can report quite a big increase in FPS, it now sits at around 70 whereas it used to be about 48 on the ground and I might get to 58 over the ocean. Nuking it seemed to have been the key rather than the incremental update.

Edited by mwa05

texture flickering on the A50 1000. tried a different plane and the problem wasn't there

Screenshot 2025-05-09 200523.png

  • Staff
3 hours ago, mwa05 said:

I have the same issue. It dips 20 FPS every 3 seconds, it is cyclic. I had no performance issues on any previous build (2020) except it was originally quite performance intensive it was manageable. If I ALT-G and watch the performance, this dip is constant and when the dip occurs it invokes a stutter. It is something internal in this build. I load in the Fenix A320 and the iFly Max, no issue.

 

Edit: I ended up completely deleting all traces of the A350 and a clean install and that has solved the issue. Indeed I can report quite a big increase in FPS, it now sits at around 70 whereas it used to be about 48 on the ground and I might get to 58 over the ocean. Nuking it seemed to have been the key rather than the incremental update.

Thank you for your feedback.

By deleting it, you mean off the app and deleting whatever is left in your community folder? I did that and barely above 30

 

Can confirm that your latest update has made this totally unflyable. stutters every few seconds. How do you get this so wrong Inibuilds?

Please allow rollback to the previous version

Fully removing and reinstalling has made no difference for me. 

Can't even change a view without it lagging. Vatsim traffic also stuttering and not moving smoothly.

This issue was not there in V1.08 yesterday. If I Switch to Fenix and FSLabs these issues do not exist either.

This is another Inibuilds induced problem 😡

10 hours ago, mwa05 said:

I ended up completely deleting all traces of the A350 and a clean install

What do you mean by deleting all traces of A350? 

I tried to do a full reinstall including deleting wasm folder but the stuttering is still there? 

I also agree 1.0.8 was more stable.

Im not having stutters, but EICAS warning of Pitch out of range for takeoff (when its where its supposed to be), and , ZFWCG errors, ringing the bells and alarms for take off....

 

Also, from first flight, engine won't start unless it gets cooled?, leg 1.

Sadly, I have to "ground" my inibuilds A350 until a new, stable update is released... hopefully sooner than later.  Version 1.0.8 ran beautifully for me. Would be nice if ini, at the very least, offered rollbacks to previous versions should an update (like 1.0.9) broke the functionality and stability of the addon.  

On 5/10/2025 at 11:26 PM, UA124567 said:

What do you mean by deleting all traces of A350? 

I tried to do a full reinstall including deleting wasm folder but the stuttering is still there? 

There is another folder to delete which the uninstall process does not take care of, and it contains the state.cfg which seemed to be part of the issue I had. When I ran the updater from the App and it installed 1.09 over 1.08, the A350 was simply not usable with the cyclic FPS drop.

C:\Users\?????\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\

Delete the ini A350 folder, as well as the WASM folder from its location, uninstall the aircraft via the App, and then manually delete anything left over in your community folder (or other addon folder if you use sim link).

I suspect the state.cfg maybe why some people experience the EGT issue however I can’t confirm that theory as I have not experienced it (yet).

v1.0.8 worked well for me (2020) was excited to try out v1.0.9 yet all the update has done is ruin a perfectly acceptable plane. Gunna have to leave it until a fix comes out for it, I cannot even look at the screens in sim without issues, the one time it did work the FMS would not let me insert a flight plan of any kind. to be honest, regret buying this. 

11 hours ago, mwa05 said:

There is another folder to delete which the uninstall process does not take care of, and it contains the state.cfg which seemed to be part of the issue I had. When I ran the updater from the App and it installed 1.09 over 1.08, the A350 was simply not usable with the cyclic FPS drop.

C:\Users\?????\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\

Delete the ini A350 folder, as well as the WASM folder from its location, uninstall the aircraft via the App, and then manually delete anything left over in your community folder (or other addon folder if you use sim link).

I suspect the state.cfg maybe why some people experience the EGT issue however I can’t confirm that theory as I have not experienced it (yet).

Hmmm I don't seem to have this directory/folder in my pc. Are you using MSFS2020 or 2024?

12 hours ago, mwa05 said:

C:\Users\?????\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\

I do have the location of the folder above but there is no Localcache/simobjects folder for that matter. Are you sure that is for 2020 version and not 2024 version? 

My sim is also not installed on my C drive, it is installed onto different drive specifically reserved for flight sim. 

Right so was able to find the folders with the State.cfg and cleared all traces including WASM folder, did a full reinstall, and it loads in fine now, and performance is ok again, however the engines still will not start. Stuck on "cooling," so still can't fly her.

I too am experiencing stutters and performance, however it creeps in slowly, during preflight to cruise everything is ok, then after 2-3 hours flight the stutters and sudden FPS drops kicks in, I have noticed this issue since v1.0.7, I thought 1.0.9 would fix this but it is still there.

20 hours ago, CWallace1983 said:

Right so was able to find the folders with the State.cfg and cleared all traces including WASM folder, did a full reinstall, and it loads in fine now, and performance is ok again, however the engines still will not start. Stuck on "cooling," so still can't fly her.

If you wait enough than they should start automatically after completing the cooling phase. Did you wait to reduce the egt or abort the start up?

Sane here, engine 1 never start

1 hour ago, ekosif said:

如果等待足够长的时间,它们应该会在冷却阶段完成后自动启动。您是否等待降低 EGT 或中止启动?

 

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.