Lukasz Krajnik

No WASM on my end with 1.2.5, no CTDs or ghosts even on 17+h hauls. SU4 and SU5. But I noticed since 1.2.5 and SU5 dramatic stuttering and FPS drop mainly in VR. Anyone?

Same trigger when selecting new destination / approach on secondary flight plan. 1.2.4 is unflyable at this moment.

Yes. Issue is still occouring.

Interesting. Since I switched navigation source to Flight Simulator I have not experienced any WASM crash. I still have Navigraph subscription activated, AIRAC updated from Navigraph in FS2024 and A350, and all functions related to Navigraph are available in A350. Not sure if this is relevant but that's my observation.

First time got this issue after updating to 1.1.8. Flight on VATSIM network, no traffic in the vicinity. Not possible to reset indication changing to other system, turning whole TCAS off, neither logging off VATSIM.

TAT? SAT? What was around airframe?

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

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?

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?