iniBuilds has released another Airbus A350 Airliner update for Microsoft Flight Simulator 2020 and 2024, with the announcement coming from their forum. This new v1.0.3 update hopes to further improve stability and reduce crashes caused by WASM memory allocation issues.
iniBuilds mentioned in their forum post that the A350’s issues are being caused by timing conflicts due to the update rates between third-party services and the A350’s systems not aligning, which can cause issues and crash the sim. Another issue is that certain data exchanges may cause unexpected increases in memory usage, which could also cause a system freeze or sim crash.
They also mentioned that WASM needs memory to run add-ons such as custom systems, avionics and third-party addons, but this doesn’t mean physical RAM. WASM uses virtual memory, which is managed on its own inside the simulator, if WASM runs out of virtual memory or can’t allocate memory correctly it will cause a crash.
To help reduce these crashes, iniBuilds has switched to Smart Pointers, which will prevent memory leaks and automatically free up memory when it’s no longer needed. They have also reduced unnecessary copy constructors, which means better performance and a smaller WASM memory footprint, delays have also been added to third-party data requests. These data requests were originally requesting external data at 30FPS, causing too much load on the WASM environment, these have now been changed to once per second, largely reducing the memory and processing overheads.
iniBuilds hopes that these changes will cause fewer crashes, have more efficient memory use in the WASM environment and improve performance all round.
You can download the latest v1.0.3 update from the iniManager.
iniBuilds A350 Airliner Changelog
Switched to Smart Pointers
- Instead of manually managing memory, we are using smart pointers.
- This helps prevent memory leaks and automatically frees memory when it’s no longer needed.
Avoiding Unnecessary Copy Constructors
- Copying large objects in memory can be inefficient and lead to excessive memory usage.
- We are reducing unnecessary copies, which means better performance and a smaller memory footprint in the WASM environment.
Adding Delays to Third-Party Data Requests
- Previously, we were requesting external data at 30 FPS (30 times per second), which was putting too much load on the WASM environment.
- Now, we limit these calls to once per second, significantly reducing the memory and processing overhead.
Expected Benefits
- Fewer crashes due to memory mismanagement.
- More efficient memory use in the WASM environment.
- Better performance and smoother experience.
