Various LNAV/VNAV problems

[dfr997]

Hi folks,

Back in the A350 after a long time and it is massively improved. I don't even know if posts on here are read but I have noticed a few problems:
 

1) On STAR (INPIP1E into EGPH) the aircraft let me select a lower level than FL200 at ESKDO in managed descent and ALT CST did not activate when I went lower than FL200. On the A320 my understanding is that when you select a lower level in managed, the constraint level comes up in magenta. I would imagine this is the same in the A350 but doesn't seem to be working

2) During SLOP out after crossing the NAT track and the aircraft leaves the offset and returns to the originally planned track, it goes a bit mad and makes a massive turn away from track. You have to go into selected heading and then direct to to get it back on track. It offsets nicely, but the return back to normal from the offset doesn't appear to be working

3) The aircraft is still quite poor, in managed mode, in keeping the target airspeed in the climb or descent

4) the FMS is not accepting waypoints in the cyan alternate routing (from dest to alternate) - instead, it's placing them in the main flight plan route (departure to destination) - so at the moment one cannot properly set the alternate route (is there a way of importing an ALTN RTE SEL in the INIT page?)

EDIT 5) When step alts are selected in the FMS and the correct alt set in the FCU, the aircraft increases the thrust but does not achieve any rate of climb - you have to cycle between OP CLB and managed CLB and then it does it

This is all in the latest update in MSFS2024.

Can I ask when the custom cabins will work again too? I rather miss my Virgin Atlantic cabin, but it's not overly important. 

Thanks all

Edited Monday at 07:57 PM by dfr997

[IniJamir]

These issue are known regarding the VNAV and other flight logic and are being resolved in a future build

As for the custom cabins, they were depreciated following v1.1.7 in favor of better baseline performance and were made free up until that point. If you still have the cabins installed, their is a Hues Mod on FSTO that updates compatibility between versions following v1.1.7 and current for the cabin packs.

[dfr997]

22 hours ago, IniJamir said:

These issue are known regarding the VNAV and other flight logic and are being resolved in a future build

As for the custom cabins, they were depreciated following v1.1.7 in favor of better baseline performance and were made free up until that point. If you still have the cabins installed, their is a Hues Mod on FSTO that updates compatibility between versions following v1.1.7 and current for the cabin packs.

OK, all of those issues above are being addressed? Well, that's excellent news