magret2canard
-
Posts
24 -
Joined
-
Last visited
magret2canard's Achievements
3
Reputation
-
Thank you haza2 for the reply. In my case, I only have this issue with Inibuilds's aircraft (350,330....) Kind regards
-
Hello everyone I hope you're doing well 🙂 Am I the only one still getting those blurry shades below the aircraft? Is there any fix for this issue? Kind regards
-
Hello After 3 long haul flights, I have the same issue. The flight time displayed is 1hr less than the one from the OFP.
-
fixed with 1.0.10 thank you
-
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 🙂
