Hello Jan and IPACS team,
I’d like to congratulate you on the immense effort of producing the new A350, which is certainly IPACS’ most advanced aircraft from a systems perspective. It’s beautifully modelled and the systems are wonderfully executed, so thank you for the hard work. However, I have some small observations that could greatly improve the quality of the aircraft.
Firstly, the FMS is properly modelled but the text entry for the FIX INFO page refuses to enter certain fixes. An autopopulated « cheat value » cannot be entered even if it is produced on-screen. Values such as « KMSP17 » without an L/R designation can be entered, but longer names such as « KMSP12R » or « EHAM36L » cannot be entered due to the character limit which should not exist. In the FPL page, estimated time on fixes are not shown.
On iOS devices, a strange grey texture flickers and covers the green status light for the FD button. I’m certain it is a bug.
The textures seem to be reduced when compared to other recent aircraft such as the 737s, 777F, and Airbuses. This can be seen especially around the cockpit window during flight. At night, the « mask » has white pixels that pulse for an unknown reason. Additionally, hollow windows do not exist so the fuselage seems to be made to a lower quality standard than other recent IPACS models. The flaps lack a depth of texturing that causes them to appear unfinished on iOS devices. Wingtip cameras are zoomed for the length of a -900 and thus the nose of the A35K extends beyond the width of the screen at default zoom.
The selection devices on either side are different. Can this be manually changed, as it’s extremely bothersome to interact with two differing interfaces.
Regardless of the inputed cost index, the climb speed remains set at 300 KIAS. Why is this? (CI adjustment failed)
Like the A380, the aircraft will not comply with direct V/S commands. For example, entering -2400fpm on the MCP results in an actual descent rate of -3100fpm without speedbrakes. Is this a mistrim or an error with the code?
The aircraft is unable to sustain a level cruise above FL390, when the ceiling is FL410. I’d like to be able to reach that altitude on empty repositioning runs.
The -900 (incorrect) wingtips are included on the -1000. Is this an indication that another variant is planned for an eventual release?
The flap sounds are fantastic, but the slat motors seem to have a higher-pitched « G » sound in real life, but I’m not sure why. Additionally, the slats seem to have an extra notch in real life at FLAPS 4 when compared to the sim model. The ailerons raise at 100 knots from what I can tell, not immediately after touchdown. The APU also produces a strange humming sound in the rear cabin views and is actually quieter than those on the A320 series aircraft. Why is this?
When using a thrust setting above 92% N1, 2 different notes can audibly be heard. The higher one accurately corresponds to the N1, but the lower (and louder) note sounds about 10% N1 lower and causes an odd sound. If that sound file could be updated to match the baseline sound, it would be appreciated. It’s not possible to discern the actual N1 during a flyby or tower view shot as a result.
BTV is an excellent feature, but it has confused me in several cases. Is it disabled at LSGG? I can’t seem to set it there, but it’s worked at every other airport I’ve flown the A350 into thus far. (KMSP, EHAM, EGLL, KJFK)
The seatbelt chime is quite interesting aboard the A350. From what I’ve noticed, it’s not possible to make sound using the « NO MOBILE » switch. Even in replay, the sound does not play when the gear are extended/retracted. Additionally, the « HI » chime, which is present on all Airbus models, is still not included. The tone is similar to a « G-D-B » cascade and is used during « MECH » or « ALL » calls from what I understand. Additionally, the sound is played on certain A350 models during a cockpit PA if optioned by the carrier. The volume is too quiet to the point that the chime can barely be heard from the cockpit. Can this be adjusted slightly? The gear « ding » may also be too quiet, but I appreciate that the seat belt chime itself can now be heard in replay.
As time passes, it would be greatly appreciated if the lineup could be expanded to include the Airbus A350-900. The aircraft can occupy the same size niche as the A330-300 with a seating capacity of 280-320 passengers. Unfortunately, the A350 directly overlaps with the B78X with seating for 366 and 370 passengers respectively. Excluding fuselage length, flap size, and landing gear set up, the aircraft is practically identical due to the inclusion of the long wingtips on our A35K. Operational variety and the length of flights would open as well (ex. WSSS-KJFK, KATL-FACT) and airlines such as Air France, Delta (N524DN), Singapore, Swiss, Edelweiss, Lufthansa, Emirates, China Airlines, Iberia, ITA, SAS, KLM (please show some love to EHAM by fixing its aprons) in the near future, Turkish Airlines, Air China, Korean, Asiana, LATAM, and many, many more operators would become available. As a personal note, I will be flying aboard an A350 for the first time in June, travelling from Minneapolis to Amsterdam. I would be overjoyed to replicate the flight with the A359 in-sim around that time, but if it isn’t yet available, I’d love to contribute some source material. Given how much time and resources went into the creation of the new systems and sounds of the A350, it would be a shame and waste to make variants wait in similar style to the B737NG/MAX, B787, CRJ line and B777 for 5 years (Until the -F came along).
Finally, there are some bug fixes that were excluded from this update. The ever-present erroneous FADEC of the B737 has not yet been fixed and the B747 still doesn’t have a working seat belt chime. Can these small errors be fixed in a coming update?
Best regards,
VolerSuisse333
Kindly let me know your thoughts and opinions!