DAD

well, it did compile WASM but now sits on the RWY EGNM and again all screens are black and MSFS2024 unresponsive... will let it sit for some more minutes and then need to kill the task I am afraid EDIT all sorted now, restarted a couple of time, picked a default livery and now it works.

That did work partly. WASM was compiled when I came back after a delicious gin tonic but then the cockpit di not load, blank screens all over. Now I bit the bullet and de- and now reinstalled the A346, currenly compiling again, hope that will help now. Let's see. Just that I cannot have another drink while I am waiting 😉

First AS must release the API SDK or whatsoever. Then WW can make their HW compatible. Based on my ticket I opened with AS

I am sure I let it sit at least 30min as I was working and in a call. but let me ensure, start MSFS2024 again, load that A340 and sit with my wife on the terrace in the sun which will easily take more than 30min...

initial load time too excessive here. way beyond 25min. deleted WASM folder but no cure. how long did you let it sit and stew for the initial compiling?

Glad that fixed it. Share the word. There are many like me who initially blamed a beta build

Just one idea since I had this recently as well for some settings incl. DLSS: realized that the NVIDIA app was set to „optimized“ for MSFS. Never was aware that was enabled as I only use this app for updating the driver. Anyway, disabling optimization for MSFS in the app seemingly helped MSFS to remember my GFX settings. So if you use the NVIDIA app you may check that. Just a thought, YMMV

Nope. Trying to find first whether this is a dummy topic or of epidemic nature

Interesting as I literally the same minute asked about the same „error“ with the Fenix so maybe it is neither the Fenix nor me…

Since recently I have almost constant Simbrief uplink errors using the Simbrief upload feature in the Fenix series via *Init in the MCDU. Anybody else? Wonder whether this comes from the recent Fenix update, updating AIRAC? Wouldn‘t know what else changed. I always use the Simbrief plugin to create a FP within the MSFS EFB/flight planer. Usually works like a charme. Upload into Fenix EFB still works, just not via MCDU. Did also cycle some preferred routes in Simbrief and in 1 of 10 cases I „hit“ one which can be imported. But this tedious and trial and error. FWIW I do not have a Navigraph subscription, never had and never will. Yet it worked before. Any idea here except that Navigraph wants to force me into an AIRAC subscription? So far I just enter the FP manually. Also tedious but at least no trial and error…

No issues here of any kind here. @GeoSkyman did you try to logoff from XBOX app, restart PC and then logon again in XBOX? Sometimes I need to do this when getting Authenticator errors, though cannot remember when I had one recently, happens maybe once a year

Will update later. Did not expect another build since they want to release SU5 next week I understand? Maybe this is basically the final release build then already?

Let’s face it - at least for me. I will *never* be out as long as they keep coming. I updated my PC for FS2020 and still run 2024 on my mediocre CPU like a charme on most settings high and some ultra like clouds and water waves (I like stormy approaches over water like ENHD or KBOS or PAKT in my tubeliners) although I was about to update my HW for 2024. my only update last year was from my 3060 to the 4070 and that still pays off. so should the next sequel now really tank performance then I would for sure bite the bullet and finally invest in new CPU before quitting this business. YMMV. Just my 2 cents

Thanks. Forgot about those settings. Thx for reminding me and putting the record straight

Hm. I only own their FCU and MCDU but there is no binding. Plug and Play. I start SimApp Pro and then FS2024. That’s it. Besides that I typically use Mobiflight …