CBH

Hello, I seem to be experiencing the same WASM crash issue as you.🤔Here is my screenshot. I had a WASM crash when manually inserting waypoints, but the error message seemed to be the same.

This is a screenshot of the WASM crash in developer mode. As for the Auto Save file, it crashes before it even finishes the first auto save, so I can't provide it.😟

Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH Specs: CPU:i9-14900HX RAM: 32GB GPU: Nvidia GeForce RTX 4060 Laptop Hello, inibuilds team Yesterday I updated my A350 to v1.1.2, but after that I can no longer complete any flights. Every time I insert a waypoint manually, all screens freeze.(See the video below for details) This doesn't necessarily happen when I insert the first waypoint, but it will happen before I finish entering the route.(From ZSSS to RJAA use Navigraph Navdata), I have tried clearing the WASM folder, reinstalling the aircraft, but these do not solve the problem. 7月22日.mp4 This is a serious problem, I hope inibuilds can fix it as soon as possible, thank you.

Yes, I encountered this situation too. I had originally planned to fly two flights over the holiday, Auckland to Brisbane and Brisbane to Melbourne. But unfortunately, I had crash issues in both flights.I used Navigraph Navdata. Of course, I found that in both cases, the crash occurred during the 2-3 hour flight.If my cruise time is less than 2 hours, the crash will not occur. For example, I had no problems flying from Sydney to Brisbane. Finally, the crash issue broke my WASM and I had to delete the original WASM folder to get the flight working again.

@FarlisOf course I know, you can watch the video I uploaded. I pressed the button twice and silenced the warning sound. But the red text warning on the ECAM did not disappear.

Hi, inibuilds. I think this is a very detrimental issue for the gaming experience. When I was about to land in A350(v1.0.8), I used my mouse to click the red button on the side stick to disconnect the AP, but the warning if disconnect the AP didn't automatically disappear.Including warning sound and ECAM display. The warning on ECAM continued until I pressed the (✓) Button below the throttle.And in order to press this button, I often end up off the glideslope because I have to take my eyes off for a moment. video_20250419_174631_edit.mp4 This is a video I recorded to demonstrate the problem. I hope this can help the team quickly identify the problem.

@chinjhThis problem doesn't just happen on VHHH, I had the same problem yesterday when flying on CYVR and PANC. I saw someone on the msfs forum mention adding "A_" all over the scenery folder, but when I did that, I couldn't load a flight because the sim would freeze.

@AtulYes, use Navigraph navdata can be solve this problem. But unfortunately I don't have a Navigraph subscription because the monthly price is too expensive for a middle school student like me😭.

@AtulNo.You may have understood it wrong.If you look closely at the pictures I sent you will see the error I mentioned happen in departure not arrival. In addition, I used the default LIDO navigation data of msfs2024 without making any changes.

Hi, inibuilds I really like the aircraft you made for msfs2024, but unfortunately it seems like they all have problems with their navigation data(even include a350). When I load a flight at a 3rd-party addon airport(The addon officially claims to be fully compatible with msfs2024) and select SIDs,It does not load correctly as expected.Some waypoints are thousands of NM away!As picture. If you say this is a problem with msfs2024, I don't think so. Because I loaded the msfs2024 default Asobo737Max at the same airport, it loads the SID correctly. As picture. So I think this may be caused by the different way inibuilds aircraft handles navigation data. I hope inibuilds can check and fix this problem as soon as possible. It makes it almost impossible for me to fly normally. In addition, there is no such problem on the Fenix320 using independent navigation data.

I also have the same problem.

I have the same problem! Also the waypoints of my SIDs would run thousands of nautical miles away in all inibuilds aircraft for msfs2024.

@AceDucklingYou are right, importing the flight plan does alleviate this situation. But unfortunately I don't have a navigraph subscription, which means I can't use the new navdata in simbrief. I believe many people don't have it either, because its monthly price is still too expensive for some students such as me.Also I prefer entering the flight plan manually because it is more immersive.

I wonder if players who used the inibuilds a350 aircraft in msfs2024 have encountered this problem. when I manually entering F-Plan. When I was entering the next waypoint of a waypoint, the system prompted me to select one of several waypoints with the same name. I selected one of them. This waypoint should normally be placed after the previous waypoint, but it was not. It was placed after the SID of my departure airport! But if the waypoint does not have the same name, it is inserted correctly. I've had this problem on several flights.(I use the default LIDO NavData of msfs2024)

The default ATC menu of msfs2024 seems cannot respond to the request of connect to the jetway. I haven't found this function in OIS which makes it impossible for me to connect the aircraft to Jetway. I hope inibuilds can add this function to OIS. Thank you.