silentghostx

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…

Hi team, Also noted on the latest version 1.0.10 - the VSD is not showing the level off altitude. If the FCU altitude is set less than the cruise altitude, it should be showing in a solid green line on at the FCU altitude, with the predicted VNAV path shown in dashed line until the next altitude is selected. On the image below, the FCU altitude is set at 8000 ft, there should be a corresponding solid line at 8000ft on the VSD, with the rest of the predicted path as a dashed line.

This picture shows that CAB PRESS MAN is indicated - however the CAB PRESS section on the cruise page remains in AUTO for both CAB ALT and CAB V/S Both these show that the LDG ELEVN on the CRUISE PAGE IS 540ft, this is incorrect as for this approach (LFBO 14R) - it is 488ft on both the Navigraph charts and 488ft on the OIS Landing Perf page. The correct LDG ELEVN on the CAB PRESS section on the CRUISE PAGE should be 500ft (rounded to the nearest 50ft). Hope this helps to clarify the bugs described above.

That would be better, but if a bug is on page 4 of the forums it might be missed… a pinned list of sorts would help a lot. Thanks again for considering.

Hi team, Bugs noted 1) The cruise page pressurisation status remains in Auto even though Manual is selected from overhead panel, same with cabin altitude, remaining in Auto despite Manual selected. The pressurisation page appears to show Manual. 2) Landing altitude - should be rounded to nearest 50ft of field elevation. Currently this value from what I’ve observed is field elevation rounded to nearest 10ft, then add 50ft. Eg NZAA runway 23 has field elevation of 23ft, should be rounded to 0ft. At the moment it will show 70ft on the Inibuilds (23 rounded to 20, then add 50ft) Cheers, Chen

Hi Eddie and team, Thanks for all the hard work. I wish that there could be consideration given to having a pinned topic with “known and logged issues” that’s worked on by the team. We understand not everything will make into the next update, but at least we know it’s being worked on. This would reduce a lot of cross and double posting. Might also be useful to use it to create the next change log when there is an update, can just take the issues from the post into fixed. Cheers, Chen

Yep. I don't think the first waypoint/distance should be shown until the IRS is aligned.

Also first waypoint and distance is shown top right on ND before IRS is aligned in the picture. Not the case in prior versions and pretty sure it’s a bug.

TO config becomes green as soon as A/BRK is set to RTO on the C/L MENU Taxi Checklist page. This differs to the checklist on ECAM where the TO config is still blue until it is checked.

I was under the impression that the initial page should show the GPS position that the aircraft was positioned at, rather than dashed lines on the first screenshot of OP ahairyrat (as per other airbuses eg FBW A380). You would only use the align on other position if you are concerned that the current GPS position indicated is incorrect. Nevertheless this doesn’t negate the issue above, as it should still work. Could the Inibuilds team have a look at both of these issues? 1) initial GPS position aircraft is aligning to not showing 2) align to another position not working. Thanks!

This happens in FS2024 also

+1 Main flight control unit panel should remain lit with ground power on and battery off during the battery test.

Glad to see improvements on this in v1.0.6 and that LS button now only activates the LOC/GS scale on PFD, and APPR1 only engages after LOC* which is corrects ongoing issues: - Still no FLARE mode on manual landing. - APPR1 should not disappear until the plane has vacated the runway Thanks for the good work!

Just tried v1.0.6 appears to be an regression on this? Didn’t have auto zoom on touchdown with the flight