Lukasz Krajnik

Difficult, but doable 😏

Hi! No big deal. Just noticed when trying to enter +13 hours to set LT on arrival and got wrong format message. It goes fine with 12 and lower. Can anyone confirm? Still the best airframe among long haulers in FS2024. Cheers Lukasz

And HUD in VR and poor meteorological conditions…. well… masterpiece. I have never experienced such immersion (and using sim since 1995).

I can confirm your observations. Issue discussed also here:

Have you ativated autozoom in OIS?

It´s been a long time since I decided to wait with flying, mostly because of WASM and some graphic related CTDs in VR. Since 1.15 (and 1.16) combined with SU4b it works like a charm! 17 hours uninterrupted longhauls like WSSS-KJFK, no stuttering when on ground or in the air. Smoothly like it used to be in XPlane 11 VR. TRUTH Yes, the airframe has many bugs and some basic inconsistencies (like f.e. wrong ETA calculations) BUT None of these bugs is critical. What is most important, the airframe is flyable again without spending hundreds of hours at gate trying to solve this and that. SO Thank you iniBuilds! Once again you have achieved the most desirable feature of a long-haul aircraft - stability.

Looks like it is solved with 1.16 on SU4b

I found 2 workarounds: - having displayed page with time on FMC2 all the time gives accurate estimates on FMC1 - changing automatic time to manual does the same but than it breaks because manual time breaks and shows bad numbers after while I may be wrong but it looks like an issue with broken time settings. Wrong calculations are secondary to it.

I mean NAV1 and NAV2. ILS autotune works as expected.

Hi! Has anyone noticed NAV autotune not working with 1.15 on SU4b or is it only on my end? Cheers Lukasz Krajnik

Have you set up autozoom in AIO settings?

SU3 or 4beta? I have callibration and sensitivity issues on SU4beta.

If I read correctly dev forum, WASM on Xbox was/is neither error free. If addons like A350 will be equally unstable there, it will be no fun for Xbox gamers neither. And if, as you write, we don't know what causes these crashes, then I only secretly hope that all this fun with WASM won't turn out to be a dead end.

So, if every gauge freeze without any trace in log in airframe build using WASM means WASM crash , what will be the benefit from reporting this? If they are random, can occure any time, any system, any situation, any input or without input, and so forth, does developer benefit from reporting even if there is nothing in the log? If this is the case, I can see point with time consuming reporting but as for now I am not sure who is supposed to fix it - FS2024 deceloper or addons developers? Who should we report to? I can not believe that none of beta testers got this WASM crash and that developer was unaware this on a release day… And last question. If WASM crashes were known already in FS2020 was it wise to use WASM? Fenix for instance did all «outside» FS and is a winner in some sens, or I am thinking wrong?

How do you know if it was WASM crash if no WASM error saved in log? I had plenty of such without any WASM connection, reported some here without response from IniBuilds, neither confirmation that it is WASM. If we get WASM crashes without any log that it is WASM fault then IniBuilds is in deep… I just wonder how was it possible that P..G found workaround to this which works for most (but not every) users.

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.