Flagrum Posted July 24, 2021 Posted July 24, 2021 (edited) Not sure, if I saw this also with the TPOD, but for the IRMAV there is some strange slewing behaviour: instead of slewing vertically, it slews diagonally. If your pipper is right at the nose of the aircraft and you slew it exactly vertically, it does not deviate from it's horizontal position. But if you start with a pipper some degrees left or right of the center line, the pipper will slew diagonally. So for example, if the pipper is i.e. 5° off to the left at the top of the HUD, it will end up something like 10° off to the left at the bottom of the HUD. The screenshot will illustrate this better: I have overlayed the position of the pipper in one picture, showing the positions on the top of the HUD and, after slewing exatly vertically, at the bottom of the HUD. It looks like the slewing considers one point in front of the nose of the aircraft (that it seems to be at the horizon might be just a coincidence?) as some sort of point-of-origin for the concept of "top" or "upwards". Strange. EDIT: I also just noticed, that the horizontal slewing is also affected in some way. If the aircraft is banked to one side, horizontal slewing causes the pipper to move always parallel to the horizon! Example: bank 90 °, the horizon is now vertically in your field of view. Slewing the pipper left and right makes the pipper go up and down on the hud, parallel to the horizon! Slewing up and down then also makes the pipper move vertically on the HUD. The difference is the slewing speed (see my other bug report). While slewing up/down is considered as farther away/closer nearby, the slew rate increases. But slewing left/right causes the pipper to move with a constant speed ... Edited July 24, 2021 by Flagrum
Flagrum Posted July 27, 2021 Author Posted July 27, 2021 I was made aware that I made an error here - instead of slewing the IRMAV, I was in INS mode and was moving the INS cursor on the EHSD. Seems to have nothing to do with the IRMAV, but rather seems to be just another manifestation of the bug that Kappa reported here:
Recommended Posts