IniJamir

Do you have that page of the FCOM so I can send it along to our team alongside media of the aircraft in sim, failing to do so, if not no worries, I just have to find time to grab it

My apologies I meant a video in the simulator

Hi, are you using Chaseplane by chance?

Are you able to get media of this happening in the mean time, if not I'll try to get around to it, thank you 🙂

Hello, thank you for the report, the team are investigating.

I will ask the team, thank you.

Hello. I reached out to the team and it appears that this is indeed incorrect behavior from our A350 in relation to the FCOM, the team is investigating the matter now. Thank you for this report 🙂

Hi, In cases like this I am gonna go ahead and point you to our Direct Support Team as they are more versed in issues like this as well the knowledge to explore more options, sorry for this inconvenience, I'll pass this info along to our team in the meantime. Thank you. https://inibuilds.com/pages/contact

I'll pass it along to the team.

It's possible that the sim in itself is corrupted then, GVAC has virtually nothing around it and is an island so it's got nothing to really use resources to the point of loading and render issues. I'll ask the team and see what other solutions I could be missing.

Hi, try reinstalling the aircraft, it sounds like something corrupted during the install, let me know if this helps.

Hello, no as we do not export data for apps, only the physical hardware.

Hello, I was able to confirm this was indeed happening in v1.0.10, thank you.

I'll reach out to our team and ask, thank you for providing the video 🙂

You'll both be very happy then 🙂

Were you able to try GVAC? I am trying to confirm something, thank you for this additional info

I'll ask the team about it, thanks.

Glad to help, enjoy 🙂

Hello, this is a known issue that we are still actively investigating, I've only had it happen to myself once and that was in the last version of A340 when VIP had come out. It behaves in the same way as WASM, however it doesn't throw the errors as demonstrated when WASM does crash with the Orange Screens which were added in it's own in SU4. An update is already in works for A350 which includes fixes regarding WASM crashes, but these are tricky crashes and any aircraft can experience issues with WASM, this isn't to deflect the issue, we do work on them as with the most recent STAR/APP/RWY Change WASM Crashes; which in our internal testing where he had reproduced reported issues, applied fixes, and then could no longer repro them. Thank you for understanding

I'll reach out and ask one of our SMEs on the topic.

This is a WASM crash, unfortunately they are a thing that any aircraft in the sim can experience provided the aircraft is built on WASM. There are somethings that can be done to clear the WASM Cache and recompile the aircraft upon the next time you load in. This can be done in the link below. Additionally it should be noted that we do work on WASM crash issues constantly and there is a master thread with instructions regarding how to upload a WASM crash report properly (should you wish to do so), that we then use in order to reproduce and apply fixes to ultimately prevent these WASM crashes from happening. Link to the master thread can be found below the first link. I hope this answers your questions. Thank you.

I'll pass it along to the team.

Hi, To push this feedback along to SimPixel, you can contact them regarding the scenery here https://sim-pixel.com/airports Then click contact in the top right, thank you.

Can you spawn at this airport? GVAC and let me know if you still have issues loading the aircraft in properly and or any other noticeable frame loss issues?

Thank you for taking the time to log exactly what the issue was and how to fix it in case anyone else runs into this issue. Glad you were able to get it resolved 🙂