All Activity

Hi, I made my first flights today and had a problem :on approaching, the speed request stay at 210. It should decrease to lading speed, but does not. Any solution? Thek's Yves from ELLX

RTO kicking in is very strange, since the Autobrakes functions from 72 kts on. Below that, there is no Autobrake working for RTO. At least this is like it should be. In my issues, the braking started always at about 45 kts and without doing anything, the bird started accelerating again at about 7 kts.

Any news regarding this? Hasn’t made it in all the updates so far.

I am not sure if this is related, but I noticed once in air turning my sim rate to x4 helped cool them, they seemed stuck at over 1000 before that (but it is also possible it just sped up the cooling). Brake fan was on and didn't seem to do much beforehand.

with my experience, uninstall the aircraft and then reinstall it

Can we have the FLS button back pls. There is no A350 without it.

After going thru the entire process of loading the SIMBRIEF flight plan into the FMC, as I push back, the entire plan vanishes. The fuel, passengers etc are all there but the route is GONE! I cannot load the route again as the REQUEST FOR FLIGHT PLAN is greyed out. I have looked for conflicts in my key bindings etc to no avail. The A350 is fine. Any help is appreciated

The inertia is in all directions.

This won’t really help if you don’t want to use a mouse, but you should get a mouse :) I’m on XBOX, and using a mouse really helps a ton. I still use the controller for controlling the aircraft, but it’s a lot easier to click buttons inside the cockpit, and also, mouses come with binded keys to push/pull buttons in MSFS2024. For example, right click is Push, clicking the scroll wheel is Pull for me.

I have the same issue in all a380, a350 and a340 too

please see the thread a couple down. Kyle confirmed that they are looking in to fixing the RTO behaviour. (I am seeing it too).

I also have just experienced this on the A380, it manifested in the exact same way as the A350 and deactivating the auto-brake during the takeoff roll brought performance back to normal again, just like in the 350

You know I like to have a theory on this thread lol But I have updated to V1.0.6. Last night I operated EGLL - WSSS. I did not use the OANS system and on take off I had no stutters. This morning I loaded into a EGLL - KSFO with BAv, did not use the OANS to taxi around and again no stutters 🤷‍♂️. I still Nvidia App installed. Anything in this do you guys think?

Here you have......no turbulence. 1.mp4

Ok, I just learned that my issue is Autobrake related. I also have this Speedbrake indication coming here and then. But there is no surface deployment, just an indicating issue see screenshot.

Hi, I saw the post about autobrake activating during takeoff in the 1.27 of your A350 (which I do not own). However, today I had the same issue with the a380. The autobrake cicked in in two seperate instances between V1 and VR. First time closer to V1 resulting in a rejected takeoff, second time closer to VR where I managed to takeoff but had brake temperatureg going through the roof. Please investigate this. Thanks.

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.