Loading up a flight today and my trusty copilot is once again invisible. I think this is a problem with MSFS copilot, NOT Black Square's aircraft, as my copilot seems to deselect/unsave every time I start the sim. That means I have to reselect a copilot every time I start the sim but even this does not guarantee that they will appear.

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.

@Raiden84 If you get any problems with installation or activation, contact Just Flight Support. There are links on the website www.justflight.com

@Canit said in Missing glass on instruments: resulting in the reflections to be low quality or pixelated This is one of the problems. Asobo added some different cockpit panoramas for us to choose from in MSFS 2024, but none of them are good options, in my opinion, and they seem to be about a quarter of the resolution of the MSFS 2020 one. They also changed something about the glass material that makes surface imperfections almost inseparable from the panorama reflections. Honestly (and this is exclusively a Nick opinion), I think they look horrible in MSFS 2024, but I will always do my best to make everyone happy. I'm tweaking every parameter and choosing different panoramas on a per-aircraft basis to get the best results. It seems that I've won over some of the anti-reflection crowd with the 114, and it's acceptable to me, so I think that's what I will try to do for the rest. Thank you all for your opinions.

Seriously, this aircraft absolutely needs the RNAV certified version.

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

@Woolies That looks excellent! Great work

Thank you for the feedback. We have forwarded that to our artists for further investigation. Mark - Just Flight

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

We don't do support via email. However, Black Square do frequent these forums. Otherwise, you can contact Just Flight Support and they will be only too happy to resolve any questions you may have. I think the @ symbol is accepted in common usage on forums and social media to tag other users.

@Derek was on the ball - that solved the problem.

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)

Above issue was via EFB. Uninstalling and installing from fresh, inputting the code via the installer fixed this...

I can't reproduce being able to close the pilot door on the ladder. There's only one clickspot on the exterior for the pilot's door, and the code is simple, so I don't think there's anything wrong there. It's possible I fixed this a while back and forgot to document the change for myself. I've also now made the tablet buttons first stow the ladders if they are deployed. Then a second press will close the door.

The problem had started happening when i joined the SU6 beta, it also gave me issues with the sovereign, switching back to SU5 fixed the sovereign but not the F100, I did a fresh install of MSFS 24 on SU5 today and managed to do a F100 without the issue.

@Black-Square I'm happy to make little tweaks like this on my own, I just always assume it's way harder to do lol

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]