silentghostx

To be fair, 1.1.9 has been a fairly stable release thus far, well done iniBuilds team! Sounds have improved. No major showstoppers except the known ones already. VSD a lot more stable and has improved in display, especially on approach. My only wishes are to have improvements to the formatting of T.O and landing ECAM messages, fix the landing elevation rounding for the Cruise page, and HUD fixes so that FPV is showing where the plane is going.

Further update - I did a short flight between EDDM and LSZH - cruising FL260. It did settle to 0 ft/min for cabin V/S. The previous flight when my cruise level was FL400 it was at +50ft/min the whole time. Not sure why this is.

Would really appreciate iniBuilds taking a look at this… especially A350 specific items such as GND SPLRs etc for takeoff and landing memos. Thanks

Yep, can confirm on my side as well. It doesn’t settle to 0ft/min after update to 1.1.9

Still the same in 1.1.9. The electric pump is only showing on in the hydraulic page when you turn it on manually.

Had this happen on approach to CYYZ today. Turn off icing effects from the sim itself seems to have fixed it. I had all the anti-ice on and it still didn’t stop the pitot freezing with IAS stuck at 180

This is actually correct behaviour on power up as far as I’m aware. There are several real power up videos on YouTube. This one starts around 3:00 for power up and note the initial engine display at around 3:20 https://youtu.be/CMeAvK4lyO0?si=RPklLvGVQj04AI3C

Mine was purple everywhere. Self resolved after around FL180? Then worked all the way down. However it wouldn’t display the vertical profile of mountains etc on the VSD

Approach and landing - see video below which demonstrates both issues. - HUD / FPV is still not fixed - that FPV points to somewhere like way beyond the touchdown zone. It is NOT usable as an aid during poor visibility approaches, will lead you astray. - VSD on approach. Like seriously. what is going on here I have no clue This is literally ONE flight. How is this quality assured AT ALL... we are version 1.1.7, if this was the first release I'd understand.

Nice report... Another 2 steps forward and 1 step back. VNAV predictions with simple things like TOC estimations are still off. For example - light plane A350-1000 with TOW 205.0T climbs at like 900ft/min on D CLB above FL300 (this may be correct as I don’t have climb data) but the TOC estimation for CRZ FL410 is like in 8min from FL300. There is no way based on the math it would make the climb in 8min at that rate so either the climb rate is wrong or the calculation needs serious rework. MORA is gone. TERR doesn’t show below around FL180 on my first flight with it (database downloaded as per instructions) LANDING ELEVN on cruise page still incorrect, I’ve made at least 2 reports prior re: how it should be rounded to the nearest 50ft based on the chart elevation. eg RCTP 05R elevation is 107 feet on navigraph, this should be rounded down to 100. The plane displays 150ft. I don’t know where they’re getting their databases on this - the LANDING PERF page has elevation for RCTP 05R at 79ft, either way this would get rounded up to 100ft. The FBW A380 freeware gets this coded correctly for comparison. All WASM folder deleted before initial boot. I mean the plane with all the bells and whistles of an A350 is fun to fly, is very pretty, but scratching anything beneath the surface of that leads to disappointment for this price level. Back to the Fenix for now…

I reflect your sentiments exactly and appreciate your report. This is why I have not pulled the trigger in purchasing just yet. I'd really like to see some of these systems issues worked out with fixes into the A350 before I buy this, there's enough bugs that is quite distracting from the awesome modelling otherwise. Looking through the youtube reviews on few well known channels, this aircraft definitely has heaps of potential to be one of the best.

Thanks Eddie!

I have no clue what’s going on in v1.1.2… VHHH 07L has elevation on the charts at 23ft. Now it’s displayed as 100ft on the cruise page Landing Elevation… it should round down to 0ft.

At the moment the FPV doesn’t actually point to where the aircraft is heading to, so it’s not that useful until it’s fixed…

Hi @haza2 Thanks to the team for continued improvements! 1st item here is completely resolved - thank you. Regarding the 2nd item, I don’t think it’s fully fixed. After the recent fix everything is rounded UP to the nearest 50ft. The correct logic should also include rounding DOWN to the nearest 50ft. eg ZSPD 34R being at 12ft elevation, this should round down to 0ft. Similarly WSSS 20R being at 13ft, should also round down to 0ft. At the moment both of these are rounded UP to 50ft on the inibuilds A350. When the landing elevation is equal or more than 25ft it should round UP 50ft, if it’s under 74ft it should round DOWN to 50ft; above 75ft / below 124ft should be rounded to 100ft and so on.. Thanks, Chen

Thanks heaps Eddie! Cheers, Chen

Could the inibuilds team please have a re-look at this? This message should NOT appear right after power on. Sorry for tagging but I’ve reported this also in discord without reply. Thanks @Eddie

Follow up on this - seems to be an issue with Navigraph. Only update via OIS. Do not install via navigraph hub. Seems to fix this.

I feel like this is an issue with Navigraph Hub updating AIRAC for the whole sim. I had issues with it and uninstalled it. It’s the same with the FBW A380.

Hmmm I wonder if this is a navdata issue? I’ve definitely seen the ILS listed beside the runways on departure page and the ILS freq shown. The most recent video by A330 Driver also shows it’s there for his OTHH departure @14:50

Agree. Especially when each update breaks things that have been working in the past. Slow down on the new features and fixing the inaccuracies to make the A350 an A350 would be appreciated.

It happens for me during autosaves.

Great report. although the first point - DCLB is indeed the first displayed thrust mode. see around 3:20 when he boots it from cold and dark.

Checking in to see if this is logged by the team? Thanks

Also on the gear page the gears should be numbered. It is in the 35K but the 359 gear numbers are missing…