Search the Community
Showing results for tags 'fixed in mu2 v2.0.3'.
I have not encountered such a case before. MU2 - version with GNS. At the ENBL airport (default scenery) there is a LOC (FD): 110.70 for RWY 07 or 109.35 for RWY 25. Why, after selecting the appropriate frequency, I am not able to set the NAV (or APR) mode on the autopilot ??? After selecting a frequency, the needle on the HSI "comes to life" and works properly. I checked the same in the C172SP and the autopilot can be easily armed in NAV (or APR) mode there. Is this a function MU2 or some kind of bug ???
I use a single paddle throttle (Logitech 3D) and previously on 2.0.1, I had no problems before as the 3D throttles would both lift and physically move themselves into the beta zone just by pressing the command I had set to lift them (I use the / key) when my hardware throttle was already set at say idle (all the way down). With 2.0.2, now the throttles only lift and MOVE when the command is HELD and the hardware throttle is nudged - the 3D throttles do not move when the command button is just pressed - they only lift. Is this intentional for this new update? I followed the manual's instructions as I did before for 2.0.1 - the only thing different is that I changed the lower limit to 0. Sorry if this is confusing, hopefully this video will explain better than I can over text. Ghost throttles basically show what I mean.
Greetings all, I accidentally forgot to disconnect the GPU and as a consequence, it was still attached when I was up in the air flying at FL210. I had no warning as such that I could see on the ground that it was still attached. I also could not remove it in Gizmo as the option was no longer available once I was airborne. Any fix for this if possible? Thanks in advance.
OEM and GNS versions exhibit the same behavior, the course can be set but the obs knob and the CDI card on the HSI do not rotate to reflect the new course. GNS version shows the behavior when in GPS mode according to another user