Lukasz Krajnik

Hi, He wrote it is not a WASM crash. I have had same issue on every flight since 1.0.12. No need to do time consuming WASM crash report if we veryfied it is no WASM crash.

Well, after 1.0.12 I got same issue with „frozen cockpit” - not only displays but also sidestic and throttle not responding. Is this issue known to IniBuilds? The only thing I changed was A350 version (from 1.0.10 to 1.0.12, following all rules when updating) and some standard Windows 11 updates. No changes to FS2024 or graphic driver. I never had this one before, spent already 3 days trying to figure out things without any conclusions. Now I am expert in departure briefing but nothing more. I read here many writing about similar bugs but also many writing they have it just perfect. The latter one was my case also until now. And when it happende the airframe is good for training at the gate (no freezes in 1-2 hours) but as soon as engines go alive the clock starts ticking… It would be nice to get some feedback if developer is aware of this issue and does it affect FS2024 only or both simulator users?

After full clean install, WASM cleared, gpu drivers clean install. Well I got into the air but same bug 1,5h after. Still no error indicating WASM… this can not be FS2024 related as I stay on SU2 without any upgrades and it worked without any freezes on 1.0.10. I suggest kindly more bug hunting than new features on this airframe… as it getting more and more unusable. And I am kindly telling this as a huge fan of Inibuilds A350.

The same here. I got 2 freezes already on ground. Can interract with OIS and mark some of C/L, but nothing more. Sidestick, throttle, rudder not responding. Looks like WASM error but it is not that. I had no freezing issues at all on 1.0.10 and today upgraded to 1.0.12.

Roll is much better now as well, but at the cost of slow airframe reaction to sidestick movement. Overall feels better and more stable.

I do not know if it is new v1.0.10, SU2, or gpu drivers but… no more stutters and performance drop when manipulating OFP in OiS. Grat work whoever solved it

Looks like it is solved in v 1.0.10. Airframe behaves more like heavy one both on ground and in the air. Roll still quite sensitive but I am not 350 rated so can not compare. Will report if known bug with pilot induced roll oscillations were solved.

No issues on my side with A350 in VR. Not clickable cockpit can be related to FS2024 issue when one exits cockpit to menu while in VR. As a rule max a few times switch between menu and cockpit helps. I do not know if this is the issue on your side. Just trying to help. edit - are you sure it has nothing to do with WASM?

Hi IniBulids! Could you consider adding pilot monitoring callouts as fe.: - Takeoff: 100 kts, Vr, Positive ROC - Climb/descend: gear up/gear down confirmation, flaps confirmation when in position - Landing: reversers green/normal, spoilers up, evt decel, autobrakes off (is missing in 1.08)? Those could be selected/activated from OIS settings menu. Cheers! Lukasz M Krajnik

Because of many CTDs on SU2b I restored SU1. The performance is worse, but no CTDs. 4 ultra long hauls last 4 days with VR. on departure and arrival, rest of flight 2D. No problems at all.

Really strange behaviour. I do not have A350 type rating but in 737 I was used to rocket takeoff within ground effect and significant decrease in climb rate when clear of ground effect. I know there is nothing to compare between these two airframes but with A350 it is inversely. I am quite sure that she did not behave like this in earlier versions. Is it expected behaviour? Sometimes it require negativ input on sidestick to maintain flight path which is quite scarry 100f-200ft AGL.

I don't know if this is coincidence but as soon as IniBuilds disabled it I get stutters right before touchdown. I have map preloaded on descend and use BTV. So far 3 ULH, various airports, and I get it reproduced every time. Did not have it in previous versions when map was autoloading at touchdown. Apart from that smooth as butter.

Can you by chance tell us where exactly did you check in FS for duplicated scenery? Do you refer to FS2020 or FS2024?

I would say that the issue has to be on your side, not A350. With a rig as yours you should have no problems at all to get 30fps in all scenarios and settings medium/high. Difficult to say if it is something with airframe installation or other software/hardware issue.

Do you by any chance use weather injector (AS or similar?)