July 10, 20223 yr I am using the Aerosoft DHC-6 Twin Otter. I load my flight plan and then find it in the GNS530 exactly as expected. I check that the GPS CDI is set to GPS. I set altitude and take off. Once airborne I engage autopilot (AP) and select altitude (ALT) and I set climb rate. The aircraft responds and climbs to altitude set. I set the heading bug to intercept the magenta line on the flight plane and select HDG and the aircraft turns to that heading. When I approach the active leg of the flight plan magenta) I turn off heading (click HDG) and HDG disappears. When I am just about to intercept the avtive flight plan leg I select NAV and it is displayed. The aircraft intercepts the active leg but continues on the same heading without turning onto the active leg. What am I doing wrong? Also according to a youtube video when the FPL is displayed clicking on the PUSH CRSR button is supposed to highlight the line in the flightplan (cursor mode) allowing manual changes to the flight plan. It does NOT highllght any line. What am I doing wrong here? Regards John Gigabyte Z390 m/b, i7 9700K cpu, 16Gb Hyper X Fury 3200 ram, RTX2060 6Gb, Gigabyte 32" monitor, MSFS 2020 store edition
July 10, 20223 yr Author I've got it. It seems that the angle you intercept the active leg must be important as I just tried again and the angle I intercept at was much less than before.\ STILL I have the problem of presses the 'cursor button' (CRSR) has no effect. Yet it worked in the tutorial I watched. Makes me wonder if there is a bug in the DHC-6 Twin Otter although I would have thought that the Garmin 530 would be a stock MSFS instrument and not one developed by Aerosoft? Regards John Gigabyte Z390 m/b, i7 9700K cpu, 16Gb Hyper X Fury 3200 ram, RTX2060 6Gb, Gigabyte 32" monitor, MSFS 2020 store edition
July 10, 20223 yr 3 hours ago, Jarnie said: STILL I have the problem of presses the 'cursor button' (CRSR) has no effect. If you are in Lock interaction mode (the default in the sim since SU4), pressing knobs in uses the following gesture: - Lock the knob by hovering over it and holding the right mouse button - Press the knob by clicking the left mouse button while still holding the right mouse button Edited July 10, 20223 yr by MattNischan
July 11, 20223 yr Author Thanks Actually when I tried your method I found it to be the opposite - ie press and hold the left mouse button (and the help message displays the same) and then press the right mouse button to select. Anyway I now know how to do it. I bet though in real life the CRSR only needs the pilot to press the button with a single finger so I wonder why on earth Asobo considered two button presses should be the norm? AND is this documented anywhere so that noobs like me are aware of the change? Edited July 11, 20223 yr by Jarnie typos Regards John Gigabyte Z390 m/b, i7 9700K cpu, 16Gb Hyper X Fury 3200 ram, RTX2060 6Gb, Gigabyte 32" monitor, MSFS 2020 store edition
July 11, 20223 yr 4 hours ago, Jarnie said: I bet though in real life the CRSR only needs the pilot to press the button with a single finger so I wonder why on earth Asobo considered two button presses should be the norm? AND is this documented anywhere so that noobs like me are aware of the change? You can change this back to single finger operation, by going into MSFS General options \ Accessibility \ Cockpit Interaction and changing from Lock to Legacy. Bert
July 11, 20223 yr Author Thanks Bert. Researching since my last post I note - The “Lock” option has been introduced primarily to benefit Xbox Controller, flight stick, or keyboard-only users who want to interact with the cockpit without relying on a separate mouse for cursor movement. And someone posted on the flightsimulator.com forum - Cannot interact with cockpit buttons. And that it was covered in the NOTES which came with a patch which I possibly read but did not understand. I think that I will set it back to legacy. Regards John Gigabyte Z390 m/b, i7 9700K cpu, 16Gb Hyper X Fury 3200 ram, RTX2060 6Gb, Gigabyte 32" monitor, MSFS 2020 store edition
July 11, 20223 yr 10 hours ago, Jarnie said: I think that I will set it back to legacy. That is what most of us have done.. 😉 Bert
Archived
This topic is now archived and is closed to further replies.