babybus Posted July 22 Share Posted July 22 2024-07-22 16-39-57.mp4 Link to comment Share on other sites More sharing options...
richboy2307 Posted July 23 Share Posted July 23 Thanks, this is a WASM Crash. You'll need to exit to the menu and start the flight again to fix. Also if you just updated, please also try to clear the contents of this folder. It will regenerate these files (for each variant seperately) next time you load the A300.Steam: Quote %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: Quote %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 Additional Info Are you getting this crash consistently by repeating the same steps that you did? If not, then this type of "memory allocation" WASM crash post SU-15 is not just limited to us or our code. We suspect this happens when WASM is asking the platform to reserve some memory, but it sometimes attempts to reserve memory its not allowed to and crash the WASM as a result. This is entirely the sim's doing and a process we do not have any control over. If yes, you're getting the crash consistently by following the exact same steps (clicking the same things in the FMS, on the same airport/fplan/procedure) then that's a bug we can further investigate. So please share a video of the entire process. Thanks! Vrishabh Sehgal ( @Richboy2307 ) Community Team Member & Tester IniBuilds Ltd. | inibuilds.com Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now