Ongoing bugs that are not fixed in 1.2.5

[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