Piston & Turbine Dukes

Thanks for the quick reply :).

Without looking at either myself, the two things I have for the yoke buttons are: The Bonanza also has some buttons on the yoke and I'm pretty sure I saw them listed out in the manual. Or maybe it was looking at Mobiflight presets. I would check both places, the Bonanza manual (since Nick usually keeps variables as common as he can it seems) or the Mobiflight HubHop repository online, which is a community-sourced set of variables and presets for advanced binding shenanigans. The other thing would be to put the sim in Dev mode (in 2024 at least) and then go to Tools --> Behavior and pretty Ctrl+G while mousing over the yoke buttons, it should bring up the code snippet and variable for the button in question.

Hi - yes I’m on Xbox. That’s comforting news, thanks. Regards, Mike

@vliah Same thing happened to me recently, I posted it here: https://community.justflight.com/topic/10047/finally-got-an-ils-issue/5. It hasn't reproduced since I uninstalled the kln90B, tho I did not have it loaded into the aircraft and I don't understand why having the unit installed would cause this issue... It is also generally good practice to enter HDG mode before intercepting a localizer.

@Avio Can't say I would be jumping for joy over flying above 30C irl

@jmarkows Okay will take a look at those.

@vliah Click&drag was what i did, but dialling very slow.

@Black-Square Okay noted that.

@Black-Square I've been using the sim pretty frequently lately and this has only shown up once for me. I find my inability to reproduce the issue quite strange.

There is a large section of the manual dedicated to all input and output variables. On page ~145, L:var_PitchTrimPower. Let me know if there is anything else I can help you with!

Just checked on both the Turbine Duke and the Grand Duke - in both aircraft if you pull either the Cabin Temp breaker or the Vent Blwr Breaker the blower fan shuts off regardless of what Cabin Temp Mode you are in.

@MiRexer Ok will try switch both ON and await to see the cycling.

Generally speaking you should not utilize the autopilot when flying any light twin single engine. That said if you are single pilot and, it may not be a bad idea to engage it momentarily to maintain a safe attitude while completing something like an approach briefing. I used a KFC 225 momentarily on my Multi IFR training, but found I did not need it. In the sim where you are using a mouse and keyboard to look around and complete actions I can imagine it would be very helpful. Extra Blurb: When experiencing an engine failure you are to conduct the appropriate emergency checklist for the phase of flight from memory in a timely manner and then declare an emergency. My flow for the turbine duke would look like this: Disengage autopilot Maintain control (Maintain ALT if able and pitch up to compensate for power loss ensuring your speed does not fall below the blue line speed) If Fire: extinguish and continue below next two items Identify the failed engine visually with rpm gauge verify (utilizing the throttle to ensure the identified engine's gauges are unresponsive to inputs) Inop Eng Power Lever Idle Inop Eng Propeller Feather Inop Eng Condition Lever Cutoff Op Eng Propeller Full Forward (Not in Checklist but should be) Op Eng Power Lever 1200 FT-LBS if level; 1260 FT-LBS if climb is required Establish a safe flight attitude (very important and why you should not utilize A/P): Hold dead engine wing up with 3-5 degree bank and apply appropriate rudder to keep the turn coordinator ball half out towards the dead engine (consider using rudder trim if extended flight is required on one engine) Continue rest of checklist items utilizing emergency checklist and declare emergency with ATS Everything before last bullet point should be able to be executed within 15 seconds of the engine failing if you are proficient. In a piston engine aircraft in cruise phase of flight you would also need to demonstrate executing troubleshooting items from memory as well before cleaning up and feathering the failed engine if the failure was not obviously catastrophic.

I’ve identified the issue — it turned out to be a simple misconfiguration in SPAD.neXt.

Now that I noticed this behavior I cannot unsee it. You mentioned third party GPS already make use of the default NAV IDENT variable, which explains why you coded it this way. But could you make it more realistic when using one of the non-third party units? For example, when using the "default" GNS 530/430 and/or your KX155B/KNS81 combo (the so-called no-GPS config), would it be possible to give us at least the option to disable to automatic flipping of the relevant switch on the audio panel (perhaps selectable via the tablet)? I'd love to click both the PULL IDENT and also the NAV 1 swtich on the audio panel myself, rather than having some "invisble" hand manipulating switches I never clicked. I love Black Square for the ultra realism, and the current solution, while understandable, does not match the level of detail of the rest of the systems. First, the PULL IDENT click does not physically pull that knob, I'd love to see the knob animated. And second, clicking a static (non-animated) knob even triggers a different switch to physically move is kind of immersion-killing (for me). Please, at least for the default units (GNS 530/430 and your own KNS81), rework this to make it more realistic so that the pilot needs to click the PULL IDENT as well as the appropriate switch on the audio panel, rather than the NAV 1 switch moving by itself. I hope it's something you can implement.

That is the best news ever!

@Black-Square Disabling AI Trim helped. The noise is gone. I also had the noise in the Piston and the Grand Duke; it seems to affect all BlackSquare aircraft.