HDG bug & accelaration
-
Hi all,
I'm at a total loss, for a myriad of reasons, so asking for some more ideas of where to start at the very beginning. I've spent much of my Easter weekend trying to solve what I think are the most basic issues I am overlooking, including removing close do everything from my Community folder. Also, I suspect that things were working a few weeks ago and perhaps some SIM/WU broke stuff (but too confused at the moment to remember well).
The aim is simple (I think): being able to control the fabulous Piper Turbo Arrows III/IV with my Honeycomb Bravo, ideally without the use of the mouse. I always use the HSI. I already fail at getting the HDG bug to work properly/as expected, so unless I can get this sorted, there is probably no use in trying to ask for ideas for a solution for VOR1/2 or CRS or any of those settings (which also don't seem to work).
Problem: even with Bravo default settings that work for all other aircraft (e.g., C172 both G1000 and steam gauges, TBM930, Bonanza G36...), the HDG bug moves a minimum of 2 degrees, no way of getting a 1 degree precision unless using the mouse. Acceleration sometimes work but only randomly, sometimes it does not and it's difficult to tell by how much it moves when it does work. Other aircraft are more stable, moving the HDG bug by about 10-15 degrees (as intended/liveable).
This suggests an aircraft problem. I think there is also a Sim problem involved somewhere, as the VOR1/VOR2/ADF acceleration does not work in any aircraft, but that appears to be a different story.
Extended problem: I am learning to use SpadNext, and have managed to set it up it for pretty much all other settings unavailable in default MSFS control settings (e.g. the three-way fuel pump/selector settings). BUT: Spad's Data/Event monitor gives a variety of variables where I don't know which to choose and/or conflicting readings both for which variables are used by the PA28 for something as simple as the HDG bug, as well as what their values are. The Dev mode "Behaviour>LocalVariables" also gave non-matching variables/value settings (e.g. the values in dev mode did not match what was shown on the HSI). I have since removed SpadNext from my computer just to see if that was conflicting, to no avail, I am still not able control HDG in the precision required.
I'm completely lost as to where to "start" (MSFS, Honeycomb, Spad, JF aircraft), which sounds weird given the time I have invested into SDK, SpadNext (Data/Even Monitor). It is most likely not a Spad issue. At the moment it appears as if going with using the mouse is the only method that does what I want, but then I'd be asking myself what I got the Bravo for. But since the HDG issue works fine with all other aircraft, it does not appear to be a HC issue alone (although that also appears to be a culprit).
Long story short, I think I'm missing something very, very basic, as I appear to be the only one with this problem, as all forum/google hits are nearly a year old. Would I have to reinstall something? Any hints would be much appreciated!
-
tl;dr: when using the Bravo with default MSFS controller settings, HDG bug in the Turbo Arrows moves a minimum of 2 degrees, and does not accelerate (works in other aircraft), mouse achieves 1 degree precision. Unable to locate the (local) variable(s) that control(s) HDG/CRS via Dev mode and SpadNext event/data monitors, can't solve problem with SpadNext profiles.