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.

Thanks again for your superb work BK! Just one question from a development perspective: would there be a possibility of integrating a G600 into the plane, or would that be too hard to code? @Black-Square

First guess would be.. RPM too low.

@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.

Try monitoring the status of the L:Var L:var_GeneratorTrip_L while you're trying to get this to work. I think that's what the reset position is actually toggling (with some other logic), so you should be able to turn the alternator on, the set L:var_GeneratorTrip_L to zero, and that should have the same effect as moving the switch to the reset position.

@Black-Square does using the native load manager have negative effects? Should we use the samevweightscas we use in your load manager? Or only one lbs?

@Black-Square Just go be sure I am understanding correctly, it is an intended behavior for it to be sitting bellow 25 volts with nothing on other than the battery? I just turned my game on to be sure and from cold and dark with only the battery switch on I get about 24.8 volts. I only ask because in the check lists it says to ensure the voltmeter is above 25 volts!

Been checking FSDT's release notes for GSX Pro-and yes, no seated passengers still it seems.

Hi thanks for the reply. the ticket number is 98591, i did have an automated response last Friday but since then it's being processed. The current hardware i'm using is the Thrustmaster Airbus throttle quadrant and joystick.

@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]

I suspect the engines might be damaged, possibly due to a hot start - I had similar symptoms after trying the CTRL E MSFS auto-start command when I was in a hurry testing a few things quite a while back. You can check and repair the engines via the menu system.

https://www.youtube.com/watch?v=MdalekIJsRk https://www.youtube.com/watch?v=gJjXwMgZT-w We have a TN Bonnie down the ramp for us and when he starts the nose pitches down. B2OSH, Bonnies start up and the nose goes down slightly depending on how they are loaded.

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

@BigRigDriver Since the Duke uses all third party avionics (except the KNS-81), flight plan importing and editing is up to the capabilities of whichever GPS you have installed and intend to use. However, I believe all the available options support importing Navigraph flight plans. Let me know if there's anything else I can help you with!

You guys are ace. To the axisandohs!!

@toby23 ah Ok. I’m having a similar problem with the Commander so was hoping you’d stumbled across something. I shall keep digging

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 !