[image: 4d0da161-d43c-401a-85d3-155bc86995b7.png] [image: aed30554-4f84-4470-b6ea-aaafd0ea134c.png] [image: 33b1cfa0-730c-4f93-853a-6e75377c8f50.png]

The EDM shows the fuel flow while priming. Even when the ff gauge doesn't.

I would like to add that reinstalling the Fokker 100 solved the issue for 1 flight only.

One short input: IRL and in daytime the cabin temperature is more a question of radiation (sun). OAT does matter, but more subsidiar.

The glass looks great in the Commander! Expanding that to the rest of the fleet would be amazing.

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

The reference aircraft we use for the interior and exterior models can often be different, as we choose the best reference material we have to complete the work. In the case of the F70 & F100, the aircraft we used for our exterior modelling was fitted with one ADF system, and the aircraft we used for our interior modelling was fitted with two ADF systems. We'll log this feedback on our internal trackers to investigate the possibility of adding a second ADF receiver to the exterior in a future update. The model of the ADF receiver on the exterior matches our reference material; however, we are always open to receiving any additional reference material. If you would like to share any reference material with us, the best way to do that would be by opening a ticket with Just Flight Support via the following link, and then we can ensure it gets passed on to the relevant department: https://www.justflight.com/support Mark - Just Flight

If you haven't already received a reply to your ticket, one of our support team will be in touch soon to offer further assistance. Mark - Just Flight

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)

@Black-Square absolutely beautiful and no question why Black Square is one of the top developers!

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

@black-square-add-ons Thank you for your suggestion, which worked. I was able to get the co-pilot to show in all models of the Bonanza by only changing the main \bksq-aircraft-bonanzapro\navigation_graph\navigation_graph_pilot.cfg , which would indicate that the other model's navigation_graph_pilot.cfg files are being ignored. Unfortunately applying similar edits to the Baron, Duke and Turbine Duke packages does not work. There is no co-pilot visible at all. [image: db6dc631-de78-4e6f-a1a7-5bb848329157.png] [image: c3006814-70fe-4a7c-9768-b4a8e97e19be.png] [MAINGRAPH.0] nodes = 0,1,2 massSections = Pilot,Copilot coordinate_system = relative [NODE.0] name = 0 tag = PILOT node_occlusion_factor = 1 modelNode = PILOT_0 massSection = Pilot interactiveObject = FilePath: InteractionsPreset\Asobo\Seat\Seat_without_seatbelt #Param: ANIMATION_SIT:Idle1_PosePropeller [NODE.1] name = 1 projectOnGround = 1 tag = SPAWN_EXTERIOR pos = 5.5, 0, -10.0 ;x,z,y (+x=right, +y=forward) pbh = -15,0,-25 ;pitch, beta, heading: clockwise [NODE.2] name = 2 tag = COPILOT modelnode = PILOT_1 pos = 1.35,0.93,14 massSection = Copilot interactiveObject = FilePath: InteractionsPreset\Asobo\Seat\Seat_without_seatbelt #Param: ANIMATION_SIT:Idle1_PosePropeller [MassSection.0] name = Pilot stationLoadName = TT:MENU.PAYLOAD.PILOT maxMass = 300 [MassSection.1] name = Copilot stationLoadName = TT:MENU.PAYLOAD.COPILOT maxMass = 300

Thank you @Esoteric . That's what I thought you would do over here in the UK.

@ElZoido83 said in Headphone isolation and LOP: Shouldn't the EGT values go up when leaning the mixture? They rise until peak, and then begin to fall. LOP is finding that peak, and then operating the aircraft on the lean side of it. I will refrain from discussing it too much further right now, however, because bit improvements are coming specifically to the EDM's LOP operation in the next update.

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

Thanks for the clarification, didn't realize the BARO was only 3 units, that probably explains what was going wrong for me. I put in 30.17 and 3.5 for example thinking that was 3500 feet, but I was actually specifying 73,500 ft!

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]