silentghostx

Hi team, While the overall A350 product is mature and can be very enjoyable, I'm writing this post in a sort of frustration. I believe most of these bugs are acknowledged in some form either here or on discord. However updates after updates - none has been resolved. I list them here for clarity. 1) CRUISE PAGE - LDG ELEVN - This should be rounded to the nearest 50ft based on the runway elevation. I.e. WSSS 02L Rwy is 22feet based on Navigraph charts - this gets rounded down to 0ft. At the moment the aircraft displays this as 100ft which is incorrect. - If it is 30ft and above - it gets rounded to 50ft. Like wise, if it is under 80ft it gets rounded down to 50ft, and so on. Above 80ft and up to 130ft, it gets rounded to 100ft. - The Landing Perf Page on the OIS shows 23ft so this data is obviously available somewhere, and just needs tweaking on how it is displayed on the CRUISE PAGE on the ECAM 2) HYD ELEC Pump on HYD Page - When the cargo doors are opening - the ELEC PUMPS on the HYD page do not reflect the current status that the pump is running and shows no PSI on the Yellow pump 3) Take off and Landing ECAMs - This NEEDs to be addressed. The A350 (like the A380) is different to the older airbuses. The formatting has been an issue that's there since the start, and has NOT been fixed despite multiple reports - T.O ECAM (See FBW A380 for reference) should be: SIGNS or SEAT BELTS ON GND SPLRs ARM <- currently the iniBuilds A350 still shows SPLRS (capital S) at the end on T.O ECAM Memo FLAPS : T.O <- iniBuilds A350 missing the "." between T.O AUTO BRK RTO T.O CONFIG NORM <- iniBuilds A350 again missing the "." between T.O - LDG ECAM Similar issues with GND SPLRs <- iniBuilds A350 does not even display the "s" just GND SPLR 4) HUD FPV issue - currently using community mod for this 5) VSD display on initial level off altitude not shown (see another topic since 1.2.1) / VSD does not display V/S profile when using V/S mode While issues 1, 2, 3 do not affect flying as much - some of these things are what makes an A350 an A350. The immersion factor is immediately lost or reduced as soon as you notice these things on a flight. These things are understandable if this aircraft was literally released today, however after 20+ updates and 14months since initial release, this is getting a bit ridiculous. Issues 4 and 5 might be harder to solve - at least for issue 4 we can use the community mod for the HUD. Thanks for your efforts in looking into these things. Cheers, Chen

Nope... still the same in 1.2.5

Just checking if this one should be fixed? It still persists in 1.2.4

Hi team, Just trialled the A350 v1.2.1. Re: VSD - glad to see some updates e.g. magenta area pre-departure. However have noted regression on the vertical profile no longer showing initial/non-cruise altitude level offs during climb phase or descends, with the predicted profile in dashed lines. V/S mode still not showing predicted profile - I believe this is known. See video of depature and climb - Thanks

I assume you’re using MobiFlight? I don’t have any checklist tick mapped for the A350. I used it in the A380 for the electronic checklist without issue though

This happened to me on a go around the other day, not sure if it’s a one off weird thing. I’ve taken off on flaps 2 before without this issue though

Interesting! What hardware peripherals do you have? I’ve never heard of that specific binding before - I have the Winwing Stick, FCU, MCDU, and Thrustmaster Airbus throttle.

Hmmm not sure what’s going on there with your set up. I tried the same ABN checklist on my side, forgot to record at the first few items but here’s mine - seems to be working ok.

Haven’t had or seen this issue before… have you checked hardware binding? Possibly an issue with a key or a component that’s doing the automatic tick off..?

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.

Current work around is ensure your simbrief plan is loaded into the inibuild manager, and exported. I was crashing MSFS every time I loaded NZAA/YBBN, but was ok with all the other airport combos. At the time my simbrief flight plan was NZAA/YBBN, but it wasn’t loaded into the inibuild manager. It will crash MSFS with whichever airport combo you have in simbrief. The current simbrief import doesn’t work for me, stuck on pending when I have my username in.

Hi all Had similar issues - the bindings for the A310 work if you use the throttle axis as “Throttle 0-100%” If you have the Fenix A320 the throttle axis is “Throttle”. It doesn’t work when you have set up it as “Throttle” axis, so save different binding profiles and change it to the “Throttle 0-100%” axis is the way to go here… Cheers, Chen