IniJamir

Hi, I'll pass it along to the team for consideration. Thank you.

Noted for the team, thank you

Hi, I'll pass this along to the team. Thank you.

I'll pass this along to the team, thank you.

Hi, I'll ask the team about this, thank you.

Added for the team to take a look into again, thank you.

I'll pass this along to the team, thank you

Hi, the manual will be receiving an update to account for the new features were added.

More updates will be coming to the manual, thank you :)

Hi, If I went around and asked everyone in a polling fashion if they are having the issue that one user was having whilst also dealing with other work items, I'd be stuck with 1000 one off issues where a good majority of them would be user error unfortunately. The reason I ask for a video is in case the user is either doing something wrong, or it's some other issue entirely, and then if it's not those issues then I already have video that I can pass along to the team showing exactly how this is happening and the reproducibility of it. I'd say that's pretty good judgement if you ask me. Thank you :)

Hi, fix for this will be coming in v.1.0.6. Once that releases, update me in here if you are still having issues, thank you all :)

I'll pass this along to the team, feel free to add videos or images detailing the issue at hand, thank you :)

Sounds good, I'll pass it along to the team then. Thank you for checking :)

Hi, can you upload a video to either YouTube or Google Drive and then link it here so I can better assist with the issue at hand. Pushing in the Knobs set them to Managed Mode and Pulling them out set them to Manual mode

Hello, The issue appears to stem from something deeper within the simulator. Our current theory is that when SimConnect becomes overloaded with data, it effectively “pauses” WASM, causing it to stop updating. Its not pausing the A350 WASM, but the whole WASM module function of the sim itself. This isn’t a true WASM crash, which also makes it very difficult to reproduce or pinpoint, as it doesn’t trigger anything in the debugger. The functions being executed at the time of the freeze vary between reports, with no consistent pattern, and they don’t show any inherent issues—those same functions run normally in other situations. Hope this gives you some insight into the issue which has been known about and being combatted.

This issue is known; It’s a cue to let the user know the sim is paused but since SU5 we’re seeing it trigger more when the system is under strain during loading or complex calculations as well as when there is diminished perf.

Glad I could be of assistance, enjoy :)

Hi, can you try switching the winglet between long and short for me, also verify that there wasn't any livery update for the Xbox package, I don't think there was but just to make sure. Let me know, thanks.

Thank you for this, I've added it along for the devs to see :)

Hi, I can pass this along to the team. That being said I am not sure how the Oxygen system in the L1011 works, the reasoning from above is sound from what I can infer on this type of thing, if you have anything to add in the ways of source material then by all means. Thank you :)

Glad to hear it :)

I'll pass it along to the team :)

Hi, I'll pass this along to the team, thank you!

Hi, I'll pass this along to the team, thank you.

Hi, try uninstalling the aircraft completely and any liveries or mods associated with the aircraft, clear the WASM folder again and then load in the aircraft with blank livery at GVAC (low intensity airport) and then let me know if you're still having issues, thank you :)