Commander 114

@Black-Square Oh my word I had no idea that it was that straightforward. I still have so much to learn! Thank you for your help ️

@SkipperMacz. That i a brilliant suggestion SkipperMacz. I just reconfigured my Master Alt button in the settings (see screen shot) and it works. Thank you so much, you just made my day. [image: bc9492af-2876-43a9-83dc-e28edebd3a79.png]

@Black-Square I wish I had some real insight for you, but I don't. I own all of your planes except the Velocity. From the Dukes onward, I've used Axis and Ohs for control bindings, and it's always been a crap shoot. I always start with default MSFS events and vars to keep it as simple as possible. But every plane inevitably has some that don't work the way they should (or at least the way I expect), and that's the point where I dig into the assignments listed in the manual. For any of those that don't work, I use the dev menu behaviors tool, and the Axis and Ohs "watch simulator events" dialog. But they both have their own failings: the behaviors tool doesn't always list bindings, so I have to inspect the code displayed and try to glean what I can do from that. And the simulator events dialog sometimes displays native events that are being triggered by code -- and often I can't bind those events directly and the dialog doesn't indicate what to use. There are a couple other tricks I use in Axis and Ohs, and I'm always learning. For example, just a couple days ago, I discovered I can use to program virtual button presses on an axis I create (for the Just Flight F28, where the fuel levers are seemingly not on an axis). Needless to say, due to the trial-and-error nature of this process, it sometimes takes a couple hours for me to bind a single plane, but it'd be awesome if I could just import an already existing control profile and have most of the assignments work out of the box. Usually I start by binding just enough to get into the air, fly until I want to switch to autopilot, and then do the rest while the plane hums along happily on its own lol

@Black-Square Does anyone know what the best settings are to mitigate this jittering effect? It seems to me that it shows up using TAA, and DLSS almost completely eliminates it, but using that results in horrible ghosting on glass cockpit displays for other planes. I suppose I can swap AA type for Commander only, but obviously a one size fits all solution would be great.

Did some flying today flying in South Africa in the Commander with twin MX 170B and the RNAV 511, weather was LIVE and clear and fine. First leg was FAPA to FAEL (57nm) and set the 'ELV' VOR as my NAV1 to get me to FAEL. I initially climbed to about 2000ft and the NAV dropped once, understandable as quite low altitude tbf. I then continued climbing to 6000ft and during cruise it dropped again, cant remember exactly but 30nm out. It then also dropped NAV about 15nm out with me at 6000ft with clean line of sight which seems unlikely that it would be a poor signal? I also had NAV2 tuned the same and the needle seemed rock solid and not showing signs of signal loss. Second leg was from FAEL to FAUG using the same VOR for outbound. Weirdly as I climbed out it dropped again at about 15nm on the outbound. In other legs I used the RNAV 511 and this 'holds' signal all the time but it does seem to lose signal SOFT lock and then CAP again and stays in NAV. So still I guess losing signal briefly but does its best to recapture and then proceed. Conclusion, not really sure but the degradation does seem to either be over sensitive or there is some other factor at play. I really couldn't see a reason for losing signal and NAV at about 15nm in and out at decent altitude and clear line of sight. Apart from that it was 6hrs of bliss touring around South Africa in the 114 ... such a great aircraft.

@FakeWayne Ah, yes, that makes sense, as the autopilot altimeter is altimeter index 2. I was just saying recently that it's a real shame Asobo neglected to give us a way to input an index or input variable to the countless native events that require one. In this case, you would need to use some third party application to adjust altimeter index 2.

@Woolies It's a real shame, isn't it? It's been like that since the debut of MSFS 2020.

@NixonRedgrave SU6 now installed as live and BATC still working just fine with EGHH Tower on Comm 1 and EGHH ATIS on Comm 2. So doesn't seem to be a general issue. Must be something in your install of MSFS or the 114 that is causing you the issue? Hope you resolve soon. [image: a96a693b-f533-4456-9491-0a3232341499.png]

glad to be of help!

Sometimes we miss the most glaringly obvious things while working on the minutia, don't we? Fixed for the next update. Thanks

You guys are ace. To the axisandohs!!

Just to follow up on the EDM-800 DIF temp, did a couple tests. At idle, DIF read 18F. When converted, it incorrectly displayed 10C (should be -8C). Cylinder readings, in F, across the 6 for EGT/CHT were: 444/310, 463/322, 440/308, 474/329, 453/315, 468/325. At around 1000 rpm, DIF read 22F, converted to 12C (should be -6C). Cylinders read: 531/234, 557/243, 528/233, 571/248, 542/238, 561/244. Another note I had was that when rapidly shifting the throttle, the DIF temp seemed to settle much much faster than the EGT/CHT temps were moving, in that the DIF temp was stable while the EGT/CHT temps were still moving fairly rapidly more than approx. 10 deg. Not sure I'd expect the DIF stability when temps are moving so quickly. Hope this helps!

Yes, that was the case....thanks !

@jmarkows no apology necessary. I'll have to study your program lines carefully, although I'm tempted to go the Mobiflight direction... @fredgarven thanks for this! I've downloaded your project and 'hey presto' I have full control of the cowl flaps ... and an awful lot of other things! Its good to see how a MF 'project' is formed and now I need to decide if I want to attempt to move over completely from FS24's clunky system. I might need to read the manual first though as those lines of code are seriously technical looking for an old geezer like myself lol.

@Jasemelbo No big rush! I'm glad that we know the culprit now. I really appreciate your willingness to help out

@rinkerbuck Next time you think you should be seeing strikes on the scope, could you please take note of the atmospheric conditions, as they would appear in a METAR, and report back? That's really the only way I can diagnose whether this is a software issue, an algorithmic issue, or a weather issue.

[image: 51191879mh.png] Partial solar eclipse over the Alsace on my way to Colmar.

@Voxen Sure that you are comparing the TAS? If you take the GS from the GTN there is also a possible wind component included.

Agreed, the Commander is really nice to fly as it is. No GPS, just old school navigation. Love it.