
magret2canard
Member-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Everything posted by magret2canard
-
Yeah, considering what's happening, it could be nice to have a downgrade option. I miss v1.0.6 as well
-
me i'm still with the 566.36 :d
-
This issue is linked to the boarding done via GSX. Could you try just to load and apply ZFW/Fuel from the OIS without using GSX?
-
WASM Error MFD - wasm is now in a dirty state
magret2canard replied to David Bonnici's topic in Systems
i got the same -
Hello Since 1.0.8, I got the famous frozen displays issue airborne. I deleted all the wasm folder before updating. no error on the console MSFS 2024 SU2 beta i7-13700kf + 4070ti + 64g RAM Navigraph 2504 Now I have the aircraft unplayable on both sims, lucky me! 1745060662.bin 1745060832.bin 1745061001.bin 1745061173.bin 1745061342.bin
-
I tried to delete the wasm folder once again, but same problem
-
Hello Since the update, I have the "screens frozen" wasm crash. I deleted the wasm folder before updating. I got it straight when I clicked on the Init Page on ground (so basically few minutes after loading the aircraft at the gate) Specs : i7-13700KF, RTX4070TI, 64go RAM WASM: Exception c000001d in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm MSFS 2020 OFP : not relevant, I got the crash even before loading the FPLN Database : Navigraph 2504 thank you 1745051966.bin 1745051713.bin
-
Aircraft wont hold altitude after CTD recovery
magret2canard replied to felipeturbay's topic in Systems
same here. Have to use the ALT mode 😄 -
Of course. But the path should be calculated to descend with idle thrust until the first constraint, like Philippe explained 🙈 I will be surprised if the behavior seemed to be correct on your flights because it's definitely not on mine as well
-
same. Very annoying unfortunately
-
hello. Squawk code isn't saved as well 🙂
-
in my case I got the same issue and I noticed that I have to set BTV exit first then ARM autobrake. i don't know if it's normal or not
-
Hello Am I the only one who got some weird T/D indication on the F-PLN page? First screen: T/D is estimated at 1813z but on the ND we can see that the distance is less than 40nm Second screen: I overshot the T/D on purpose, I got the warning message but still this weird T/D waypoint with a wrong time in the F-PLN page... thank you