DAD

indeed, they all sound the same

good here, finally no more freeze after hitting Ready to Fly. zipping from LGAV to LGKR right now EDIT for the record, I DID NOT have any old panel state files. but whatever they did under the hood helped

Excellent. Will check now Official change log - not long but yet excellent if my 738 works now again: This is build 4.0.57. This build continues the effort to increase stability throughout the aircraft code files, with specific fixes for: WASM crashes from old panel state files

it would if it worked for me. de- and reinstalled the 737 and no cure. only have the default panel states, never created an own one before. still the 737 and actually MSFS2024 altogether freezes after I hit Fly Now. But well, as mentioned before, I am on SU6 beta and cannot expect it to work so no complaint. though as also mentioned, Fenix, iFly and the Avro RJ work perfectly. Wondering whether the PMDG has problems with ChasePlane maybe since I do not get the new WASM red/orange screens but just dead/black screens. But again, all the other planes work just fine... will maybe try again the PMDG but otherwise continue to use the others. I am anyway getting less and less tempted to use the PMDG-ware TBH, just not as "polished" like the others in terms of QOL (think about EFB....). just my 2cents though, no reason to get yet in another PMDG bashing/justification please EDIT I stand corrected. Tried the 738 - cargo version - and it loaded just fine. will do my return LGAV LGKR now with that one

which one exactly, just about to start a flight LEIB LGKR and will check EDIT just checked some, so these work e.g. with clicks (though sometime barely audible with AC running, had to turn my volume up): Landing Lights No Smoking / fasten seatbelt Supply/Exhaust normal and ALTN AC CAB/UTIL and IFE/PASS SEAT Wing Anti Ice Heat Probe

not very prominent, I myself missed it. happy to apologize should someone feel harmed by my double post

unfortunately not for me. only have the default ones. re-installed the 737 completely and still it just does not load beyond the Fly Now button, no orange WASM screen though, actually black screens and MSFS2024 freezes alltogether...

maybe he referred to as webassimply

not here, also SU6 beta

In case you missed it as communicated on Discord Hi Everyone! Hot Fix #3 is ready to install! Based on what we've seen reported, this hotfix focuses on refinements to performance and stability, contains a model fix and also a couple of EFB updates: (1) the cabin voice in use remains selected when MSFS is closed and then reloads and (2) the number of custom cabin announcement folders which can be seen is increased, as well as the space to display long folder names. Also, the iFly Manager is updated and the update is required to install Hot Flix #3. When you open the iFly Manager it will prompt you to update. Then you will be able to update to Hotfix #3 (1.1.0.3). Notes: Pro Tip: Remember to always exit to the MSFS main screen and reload your aircraft when it is first installed. This ensures that all systems are properly loaded. And it also provides better overall performance. If for any reason the aircraft does not behave as expected, do a full clean installation following these instructions: ⁠unknown. Happy iFlying!

thanks. but I had the freeze/crash also after a clean re-install of the 737? Anyway, deleted now the panel states from that working folder (though all their creation date was yesterday when I reinstalled the 737 so I would expect those are the ones which actually came fresh with the update). FWIW also, I never created a custom panel state.... anyway, will check later whether that fixed things. EDIT tried and still does not work after I deleted the panel states. now they are back with today's time/date stamp. but still 2024 froze after clicking fly now. will wait for a patch or SU6 final and fly the iFly and Fenix instead

As said above, all dead here too. De- and reinstalled the 737, switched to default livery and still no help. No red/yellow wasm crash messages though on the displays. They just remain dark and then 2024 freezes and I must kill it.

that may be right though the update does not fly on my end. the 737 just does not "activate". it loads fine but then freezes upon entering the cockpit, gauges remain blank, EFB is missing... did restart 2024 and no cure. deleted the WASM folder (sic!) and no cure. but I admit I am on SU6 beta, could be a compatability issue so I won't complain. though the iFly, Fenix, RJ, AS340 all work fine under SU6 beta...

Thanks! This is build 4.0.56. This build addresses code stability throughout the aircraft code files, with specific fixes for: Persist Engine Exceedance in Panel States Manual Airway Entry Error on RTE Page Disconnect Annunciator Flash Arc Magvar and Bridge Arc-to-Line Gap Low Brake Hydraulic Pressure Error PERF INIT FL Error EFIS/ND Rendering Issues Line Draw Gaps Those who want to keep reading RSR's post here may click on the spoiler RSR Wall of Words

same same

thanks, updated and now the iFly does not freeze anymore when loading a flight, resulting in a frozen screen. seems ChasePlane was the culprit. works beautifully now

just had a CTD after taking off in the updated AS A340 after I clicked a button on the overhead... ok, it's a beta. not complaining really

That was faster than expected. Downloading now…

Same here. Twice. Until I realized I used a livery from FS.to. Changed to a livery from the installer and all fine. Loading took some time though. Parts of the cockpit textures started blurry until they „came into place“. Thought the iFly is installed locally. Usually I seldom see this only when loading a plane which is streamed online. besides, something is very demanding. Started from Gaya‘s new LGKR and got this „exessive Resource“ warning message until I took off

If I could really keep just one: iFly737 and Fenix ;-) Other would be the RJ

Not seen this before. Long shot but do you happen to have dev mode enabled?

Yes. That is the factor. Took the iFly out of EGLC and Simbrief already gave me the warning the rwy length would not be enough. Did it anyway. So much for being smart :-). But hey, it’s a simulator.

Probably due to the short runway. There is usually a setting in either EFB or all those FMC menues that only Airports with rwy above a specific length are displayed which shall prevent you to divert to a local glider field for an emergency landing

you posted this elsewhere already, please see my answer there

you mean clicking the FMC like e.g. LSK buttons? just started EGLC to EDHD and FMC behaves nicely EDIT perfect flight, came down ILS13 nicely with some cross wind, no oscillations bouncing BTW and the FMC worked all fine