All Activity

It happens with the A380 too. Tried to take off in Narita to Tokyo, decel short after V1 for no apparent reason.

Previously, when loading into a new flight, the engine and pitot tube were covered with red protective caps that could be removed during the walkaround inspection. However, after updating to v1.2.8, these covers no longer appear when new loading, the aircraft directly enters a state where the walkaround is already completed. Is this an official change? Is there an option to enable or disable this feature?

The Cost Index (CI) value is automatically cleared when the aircraft transitions from CRZ (Cruise) to DES (Descent). For example, if I enter a Cost Index of 20 in the INIT A page before departure, the value is correctly displayed during the flight. However, as soon as I initiate the descent, the CI value disappears and is replaced by -- in both INIT A and PERF DES. This behaviour is unexpected and does not reflect the expected A320 FMGS behaviour. The Cost Index should remain available throughout the entire flight, including the descent phase. Platform and aircraft * Simulator: Microsoft Flight Simulator 2024 * Platform: PlayStation 5 (PS5) * Aircraft: iniBuilds Airbus A320neo V2 Steps to reproduce Load a flight in the iniBuilds A320neo V2 (Cold and Black) Enter CI 20 in the INIT A page. Complete the flight preparation and take off. Continue the flight in CRZ phase. Initiate the descent (DES phase). Open INIT A and PERF DES on the MCDU. Observe that the CI value has disappeared and is displayed as --. Actual result The CI value is automatically cleared when entering DES. Both INIT A and PERF DES display -- instead of the previously entered value. The FMGS no longer displays the original Cost Index. The expected ECON descent speed calculation may be affected. Expected result The previously entered CI (e.g. 20) should remain stored throughout all flight phases. The CI should not be automatically cleared when transitioning from CRZ to DES. The FMGS should continue using the entered Cost Index for ECON speed calculations during descent. Additional information This issue occurs consistently when entering the DES phase. Please investigate whether the transition from CRZ to DES is incorrectly clearing the Cost Index value or causing the FMGS to lose the stored CI parameter.

Hello i’m currently using navigraph but this issue was already present before i started using it i think it might be related to the scenery rather than the navigation database itself although i can’t say for sure. i’m using the technobrain RJTT freeware airport you can find in flightsim.to

Sorry for the delay - the answer is yes. And I have tried lots of different permutations also. As I said earlier, although not an expert i have had lots of experience abd also flown the inibuilds A350 without much hassle.

morning Kyle, That did the trick. It does seem to be the RTO kicking in. Without RTO set all was well. I have also noticed sometimes on landing the brakes get stuck and will not release. There may be something weird going on across the braking system in general. all the best Jane

Do you see this small cylinder? No. It’s supposed to be attached to a rod, but it’s floating in the air, far from where it should be. And this is the case behind every wheel. On the A380, this part is perfectly fine.

I think you mean roll?

iniKyle. I don’t see what you’re referring to here "SteamLibrary\steamapps\common\MSFS2024\Community" as it seems the aircraft are located in the MS Store — "SteamLibrary\steamapps\common\MSFS2024\Official2024\Steam" Here is the complete list of what I have here. Everything was purchased and is being used legally; these items were bought via the MS Store from within the game. -inibuilds-a220-liveries -inibuilds-aircraft-a220 -inibuilds-aircraft-a340 -inibuilds-aircraft-a380 -inibuilds-livery-a380-pack I have tried launching the game in "safe" mode and without any of my installed content, as you suggested. This did not help. To get the aircraft to load, I have to restart the game multiple times—specifically in relation to the WASM component. Deleting the WASM folder does not help, nor does reinstalling the aircraft. "%APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\" I should also mention that I’ve run into a major issue with INIManager, where I was denied access to certain arguments/features. Because of this, I am forced to purchase and use content exclusively through the in-game store. I even have an official letter from Microsoft clarifying that items purchased from them are never "blocked"—at most, they might be completely revoked—and in the event of a dispute or a serious violation, I would simply be able to purchase them again. I'm waiting for more advice on how to fix wasm.

a380

Good to know, thanks :-)

Do you also have the issue on Takeoff? I don't know if it is the same issue with the speedbrakes, but after setting takeoff thrust, the aircraft accelerates until about 50 kts and then is braking down to about 10 kts. Without doing anything, the plane accelerates thereafter to normal Takeoff power. I will check if the speedbrakes are out during this. I will report.

No. Normal default textures. It all worked fine in version 1.0.5.

I am pretty sure I have heard them in cockpit videos, but yes, they are probably a bit too loud from the flightdeck currently.

Since update 1.2.6 something is changed in the flight model. The pitch behaviour became very laggy, leading to overcontroling pitch input. Losing control of the aircraft. I thought it had to do with my settings but I now read complaints about this on Facebook. Please make the model as it was because its no fun to fly it anymore!

MSFS2024 beta, 1.2.8, A359, P11 Fix FL plan / sim Mach plan / sim TAS plan / sim (kt) Time from takeoff, plan / sim Fuel used plan / sim (kg) Extra fuel used FOB plan / sim (kg) FOB vs plan LAKOL 100 / 123 .58 / .47 370 / 293 0:06 / 0:06 – – 76,457 / 76,676 +219 BAKOR 251 / 248 .79 / .74 482 / 449 0:17 / 0:17 2,624 / 2,534 −90 73,833 / 74,142 +309 TOC 330 / 327 .85 / .84 497 / 492 0:26 / 0:27 4,254 / 4,330 +76 (+1.8%) 72,203 / 72,346 +143 CSO 330 / 330 .84 / .850 493 / 498 1:29 / 1:30 12,076 / 12,487 +411 (+3.4%) 64,381 / 64,189 −192 DJA 350 / 350 .85 / .849 493 / 495 2:59 / 2:59 23,025 / 23,628 +603 (+2.6%) 53,432 / 53,048 −384 USPOK 350 / 351 .84 / .852 495 / 501 4:17 / 4:17 32,287 / 33,472 +1,185 (+3.7%) 44,170 / 43,204 −966 MBA 370 / 370 .84 / .845 491 / 493 6:08 / 6:08 44,963 / 46,355 +1,392 (+3.1%) 31,494 / 30,321 −1,173 BUSIV 370 / 370 .84 / .847 490 / 494 7:00 / 6:59 50,633 / 52,197 +1,564 (+3.1%) 25,824 / 24,479 −1,345 VSA 390 / 390 .84 / .850 487 / 490 7:22 / 7:22 53,172 / 54,632 +1,460 (+2.7%) 23,285 / 22,044 −1,241 EPMAG 390 / 390 .84 / .850 484 / 489 8:28 / 8:26 59,983 / 61,250 +1,267 (+2.1%) 16,474 / 15,426 −1,048 RUDAS 390 / 390 .84 / .848 480 / 487 9:23 / 9:20 65,460 / 66,742 +1,282 (+2.0%) 10,997 / 9,934 −1,063 Landing – – – 9:52 / 9:49 66,780 / 68,212 +1,432 (+2.1%) 9,677 / 8,485 −1,192

Here is proof

I even removed the VHHH WASM folder, uninstalled everything, did a fresh reinstall, and still the same invalid rotation

I've reinstalled this 4 times and still keeps having the same issue again.

I even did a fresh reinstall and still it keeps saying invalid rotation regardless of gate and aircraft.

It broke again, this is after uninstalling and reinstalling twice.

Hi all something to look at Image 1 Once Engines are on the Spoilers raise and stay with the aircraft until after takeoff, turn engines off they drop down. Image 2 Inflight this occurs flashing/flickering as the wishing to deploy up every now and then once you land image 1 occurs until engines are switch off. as in image 2 I have tried massive dead zones for it to go away I just cannot fix the spoiler issue. I tried binding a key even removing all commands for this axis. Just stay up a fraction. I turned off all panels and hardware only using a mouse still stay as image 1 Something for you to look at Kind Regards Rich@VPDU Whitey

After updating to 1.2.8, Flaps are now extremely loud again...i hear the whinning sound as if i was siting in the wing section... If its a matter of opinion, id prefer where almost none sound was perceived...I beleive in the A350 flaps (rather than the lever moving) are supposed to not be heard...they are too far back... Any way we can lower them to our preference? o r add the option of not hearing them in the cockpit (I beleive the A380 has it) Amazing products though... Thank you!