No, don't have that on my end... There is an issue for me where the alternator switch turns off with some setting changes on chaseplane and also when using the physical keyboard to make entries in the WT 530/430
Hi, just to report back. I uninstalled the 114, downloaded a fresh download from my account. Installed it in Admin mode to a custom install location........The default was C/Just Flight/114.........Something like that. Then I click and dragged the contents to my 2024 community folder. Just doing a first flight since doing this using the basic 114 and all the tablet tabs are showing correctly. The missing Engine one is now present.
The Hobs meter appears to have yesterdays hours still, but it wouldn't have mattered at the minute as there is only about 4 hours on the aircraft at present.
I wanted to thank you for replying to my original post so quickly, I think all my issues seem to be ok now. It really is great when a developer who makes great aircraft is also willing to work with us, the community, to correct any issues which have inadvertently occurred with a product release. You get my vote every time when something new releases. Thanks again, and all the best Dave.
@SadBucket said in RNAV/VNAV with Commander 114:
@rinkerbuck In this instance I believe the way you want it to be configured in your aircraft irl.
what are you trying to say here?
@SebAvi Well, ISA temperature at FL180 is -21°C, so we know the density altitude is higher by approximately 2,000 ft. That means performance started to degrade at a density altitude of more like 16,000 ft, which I think is reasonable for a turbocharger installation of this nature. However, in my own testing the other day, I didn't see any loss of performance until between 17,000 and 18,000 ft.
No it's not sufficient. You have to engage the AP Master if it's not already on, and then activate set heading mode variable. With mobiflight it's working well this way, using only one hardware button. .
Thanks for the IRL insight. I suppose I was thinking more about the fact that straightforward NAV autopilot to a VOR seemed to work OK, but the oscillation just seemed to be happening with NAV autopilot to the pseudo VOR.
@Zacke It is true the temps can take time to rise or fall based on ambient conditions. I will point out something interesting however. It is very possible to get an overtemp (especially cylinders) when climbing up high. Though its generally colder, the decrease in air density means its less efficient at taking heat away. A few years ago I was flying a turbo mooney at 17500. If I even thought of closing the cowl flaps the cylinders would spike in temperature. Always best to use the cowl flaps to give an engine what it needs, not by some generalized procedure.
Thanks both of you. @Zacke I did observe an extreme version of my issue in a SoCal flight where the OAT was around 100F and of course sunny -- I wasn't surprised by the temp skyrocketing in the afternoon sunlight. But I also do a lot of early morning and early evening flying in places where there's not really a lot of sunlight -- cloudy Southeast Alaska, for example -- that's what made me question it.
@Black-Square thanks for confirming it wasn't my imagination. To be honest, cabin temp control flummoxes me in a number of aircraft, and I might fixate on it a bit too much as a result -- probably the main reason I even noticed this, because it put me behind the curve right from the start lol
Just to tag onto the LOP discussion, leaning LOP really pushes the CHTs up, which is the opposite of what I'd expect-- I'm having to crack Cowl flaps pretty frequently to stay below a conservative 380-- having not flown a 114, I don't know how normal that is.
If I lean more LOP, they seem to go even higher and you can lean pretty (probably a bit too?) aggressively before the engine starts complaining. In reality I'd expect CHT to fall off pretty hard anywhere leaner than best power, and the engine should falter sooner once you get past 50F LOP, imo.
I'd imagine a lot of this is MSFS being MSFS, but thought I'd share my thoughts anyway.
(Edit: I'm in the TN version)
Argh, I don't know how I missed the "H:" in front instead of "L:". Expectation bias?!
Anyways, in Spad, you simply create "Client Events" For HTML events that aren't already present. The SPad team will often add HTML events upon request for planes, but this is very easy to do. Screen shot below for anyone else wanting to do this, ignore the first entry. Nothing to configure, just paste the event names from the manual as shown. These work fine, though the buttons don't move (maybe I'll dig in the developer tools someday to see if that's possible).
Thanks as always, Nick!
[image: f98ac399-a133-4abc-ad26-19e57c019d48.png]
