foliainfx

Update it in the iniManager

Fyi, iniBuilds (atleast 350) has highly inaccurate systems.

Fenix also have a slightly inaccurate FBW/FM. The issue is that ini reuse things from previous aircraft (MCDU items, FBW, VNAV, EFB, etc.), and keep it that way without adjusting it a lot of the time. So the same issues carry over and then you're just kinda stuck with it because ini just won't fix it, all their fundemental systems are flawed (VNAV, LNAV, FBW, hydraulics, electrical network, bleed, packs, it just keeps going) and I doubt they will do much about it because it's cost and time intensive, although that's not really a reason not to do it imo.

You have to wait for iniBuilds to finally fix this, it should have been fixed in the last update but they didn't fix it.

I believe this is a performance limitation, since each state takes up performance, and when you have like 1000+ states it really gets on performance. It's also why developers like Fenix don't offer many customisation options, it's because it takes up too much performance.

The HUD isn't even supposed to be a thing in the ini 350 right now

iniBuilds will rarely give you a verbal warning, warning or kick if you do something wrong. They'll just permanently ban you out of nowhere, and their moderation functions in a way where no proof has to be provided by mods.

Is this due to a sim limitation?

The A350 VNAV from ini is currently very flawed. It has many issues like constraint handling, FMA modes, etc.

Opened/closed doors aswell as passengers affecting the cabin temp is deeper simulation, the implementation from ini is just very basic

Advertised functionality not functioning isn't anything new. But since you are using sim default instead of Navigraph, Navigraph exclusive features don't work because you're not using it.

No, it does not. It shows when reverse thrust engages. Make sure the EFB settings are right, it's an option that was added a few updates ago.

1. ANF doesn't show on touchdown irl either 2. Autobrake off callout is only above 65kts

No. The 380 has been developed with the 350, just less. It wasn't cancelled and they gave a small "update" about it a while ago.

No, iniBuilds have included a non-functional HUD that can't be disabled for the moment.

@Eddie Can you please make sure the first and fourth point are corrected as soon as possible?

It should be overridden by sidestick input, missing in the ini I assume

From https://forum.inibuilds.com/topic/30792-inibuilds-a350-airliner-for-microsoft-flight-simulator-2024-2020-v110-released/ - For those of you who value exact eye-level realism, we’ve fine-tuned the default pilot camera positions to better align with the eye reference indicator. This ensures that key HUD elements, flight displays, and visual references are positioned correctly in the user’s field of view, allowing for a more authentic perspective from the left seat. From https://forum.inibuilds.com/topic/24989-inibuilds-a350-airliner-for-microsoft-flight-simulator-2024-2020-introduction/ - MELs on startup - a fully functioning HUD - From status pages to memos and limitations, no detail has been overlooked! - every system sound is replicated to perfection

- FMA modes - VD incorrect radio height - VV missing spacing - missing behavior of hydraulics when using cargo doors - false eye reference point - false camera position - DCLB shows when engines aren't started - no optional HUD - HUD doesn't work although advertised - FCU BKUP AFS CP page overlapping text - 60 MFD issues were not corrected - missing HDG line - incorrect VD end when using HDG mode - incorrect VD when using HDG mode - missing ITO simulation - PACKs work without bleed air - A/THR modes when engines off and thrust levers idle - DATALINK INIT doesn't show aircraft registration or airline - HUD displaying items incorrectly - HUD items show on the plastic part, not just the screen - missing EGT simulation - approach data when at departure airport - nosewheel turning speed - missing failures functionality Majority of this should've been fixed in the last update according to iniBuilds.

Auto derotation doesn't help the pilot it replaces it. After touchdown of the MLG you are supposed to stop sidestick input, because the plane will lower the nose itself. This is usually not used though and most pilots do it manually (manual = overriden). The aircraft stays in flare law even during the manual state.

@richboy2307 Could you make sure this is included in the large update? It has a really big effect on images

This is probably an issue with your bindings, check all flaps related bindings and see if you can find the issue.

Licensing I assume

Liveries are updated for the next version already which has changes affecting the model. You have to use a livery from fs.to until the update is out.

It's mostly irrelevant if it's used irl or not, ROPS/ROW calculates with given data and checks if the runway is enough. Either you are outright unable to land there, the data given is wrong or it's a calculation issue. The liveries are currently updated for the next update scheduled for this month, so issues are to be expected.