MR.TX Posted August 2 Posted August 2 On a recent flight I thought it would be a nice idea to give the HUD a try and noticed a rather big issue with it. I was on an ILS approach into Doha in the A359 and wanted to land the aircraft by hand. Even before attempting to handfly the approach I noticed that although my aircraft was perfectly on the glide slope of the ILS, the velocity vector shown in the HUD was nowhere close to the touch down zone, but rather far above it. I then disconnected the autopilot and aimed the velocity vector right at the TDZ to see what would happen. To no big surprise I noticed that if I would continue to follow the velocity vector, my aicraft would probably crash a mile ahead of the runway into the ground. Hopefully this issue can be adressed in the future. 2
Bianfable Posted August 15 Posted August 15 Can confirm the same issue here, the velocity vector is always significantly too high and slightly to the right of the actual flight path. I tested v1.1.3 today, but while the field of view and MINIMUM issue are resolved, the same issue with the velocity vector is still there.
dectenor1 Posted August 17 Posted August 17 Yep, still an issue with v.1.1.4 I don't know why things are released like this that are clearly completely broken. The HUD as is is just a total gimmick.
kato217 Posted August 18 Posted August 18 (edited) Same here with v1.1.4... 1) Pitch ladder, Approach Reference Flight Path Angle (FPA), and hence velocity vector (or FPV) still at least 2.5 degrees high. 2) Vertical Speed Indicator (VSI) reads 100fpm less in HUD than on Primary Flight Display - e.g. if PFD reads -800fpm, then HUD VSI will read -700fmp. 3) Declutter switch does declutter the HUD, but immediately springs back to the lower position after clicking. In effect it is acting as a toggle switch rather than a 2 position switch which stays in either up or down position. Edited August 18 by kato217 Picture wouldn't show up, so I deleted it
Eddie Posted August 23 Posted August 23 Hello all, We're aware of all the issues that are currently present with the HUD and will resolve them in due time. I cannot give an ETA but it'll be fixed as soon as possible. For that reason, HUD-related threads will be locked until further notice as we already have the information we need. We apologize for the inconvenience. Thank you 🙂 1 EddieCommunity Manager iniBuilds Ltd. | inibuilds.com
Recommended Posts