Steam Gauge Overhaul

Hi...

No, it's not what you expect from overflying a ground based Navaid.. It's literally an angle offset error. First time I noticed it I was tracking a VOR radial outbound and I realized I needed a very large track correction to keep the HSI needle centered. It was acting as if I had a 100 knot crosswind. Then I did a few tests flying direct to a VOR inbound with the RMI 1&2 VOR needle, the HSI and the #2 OBS all set to the VOR. I noticed that any needles on the #2 nav would track the VOR correctly, but the needles on the #1 Nav were pointing roughly 10 degrees to the left and the closer I got to the VOR the bigger the error. It's almost like if the #1Nav radio was tuned to a phantom VOR that was always left of the one that it was tuned to. I was backing this test up by using the default MSFS VFR map.
Also, the NAV 1 DME was intermittent past 11 miles.. I could listen to the DME on the audio panel as a strong morse signal, but the DME indicator was blank. This was while tracking a back course localizer where the fixes had DME references out to 30ish miles from the localizer.

But the good news is, I just reinstalled everything associated with the King Air, including FSUIPC, TDS GTN, The Caravan and the 850 which I just bought last night, making sure to install the King Air and the TDS last and it appears whatever it was is now squashed. I kinda wish I had reinstalled things one at a time so I could at least find the culprit, but this beats any longer process off troubleshooting.

Hopefully growth can convert into investment in resourcing in order to sustain the momentum and timely updates to the larger product set. Contingency planning needs a second high skilled resource as well.
Wish I could have attended the expo to congratulate you on what you have achieved to date. Really fantastic, stepped up my enjoyment of flight sim which I take quite seriously in my retirement days.

Turned off McAfee and switched on Microsoft Defender. Downloaded and scanned without issue. Now up and running with McAfee switched back on

@DrZGard said in King Air, KNS-80 RNAV, AP NAV mode does not work!:

In the Duke the RNAV will drive the autopilot but only if no GPS is selected on the panel, a workaround discovered during the Duke's development. BlackSquare does plan to implement this functionality at least in the Baron and Bonanza and hopefully the King Air and Caravan as well. I am really hoping for a King Air panel with the CTL radio heads flanking the center radar and below that the KNS81 and KLN90B replacing the KNS80. I'd even ante up a C note to help make that happen!

Thumb Up 50x60.png

@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:

here is the full code

Thumb Up 50x60.png

Thanks, I got it. There are some nuances - but everything works adequately!

That's fine and makes sense in such a complex aircraft, but perhaps when you do the rework it might be worth mentioning in manual somewhere just in case anyone else gets confused!

Maybe it could be fixed on user's side before official patch comes.

Open camera.cfg and find "[CAMERADEFINITION.0]"
Then find "[CAMERADEFINITION.1]", then "[CAMERADEFINITION.2]" so on.
Make sure that the number is not skipped nor duplicated.
Manually renumber them when omission or duplication is found.
In my case the culprit was duplicated number.

And of course, always make a backup when you fiddle with original files.

Thx for your swift answer. Looking forward to it.

Thank you for your reply.

I have tried the following data and none of them work.

Set B:ENGINE_ENGINE_Push_Ignition to 1 Set B:ENGINE_Starter_Ignition_1 to 1 Set TURB ENG MASTER STARTER SWITCH to 1 Set GENERAL ENG STARTER ACTIVE to 1 Set GENERAL ENG STARTER ACTIVE:1 to 0 Set GENERAL ENG STARTER:1 to 1 Set MASTER IGNITION SWITCH to 1 Set TURB ENG IGNITION SWITCH EX1:1 to 1 Set TURB ENG IS IGNITING:1 to 1 Set B:ENGINE_ENGINE_Push_Ignition to 0 Set LVAR:XMLVAR_Starter1 to 0

And Engine_Ignition_1 controlls the ignition switch, but not the starter switch.

The only data that triggers the movement of the switch is LVar:XMLVAR_Starter_1 but unfortunately it does not stay on.

Might need a little more help here please.

My hope is that they redo the king air for MS2024 using a bespoke model and sounds from Boris. In the meantime, I’ve been using the FTSim sound pack which is much better than default.

Thank you, it worked!
White.png

Thank you Black Square for making this excellent addon!

I was able to reproduce the correct scenarios, and it looks like the ones I tried in my previous post were the expected outcomes.

I really enjoy the plane, and only see people praising it too!

I'll start with some additional questions, and then I'll write down what I did in this particular case and how they worked.

Is that ok that for flooded engine I was able to start the engine without leaning the mixture, and varying only the throttle? Not related to this issue: I read somewhere you're working on a similar tablet that Duke currently have: https://community.justflight.com/post/25841 . Is that really true? Not related: I've read in some places that the state saving has bugs, and that currently you're working on a fix? Is that also true? (I've created a ticket for that very recently.)

About the engine start. It looks like it works as in the manuals. (The environment: normally aspirated Bonanza, EHRD airport, 15 C outside temperature, at mean sea level, standard air pressure, "Clear Skies" weather in July. Propeller high RPM in all cases.)

(1),(2) The cold start and engine flooding case can be handled together. If the auxiliary fuel pump was running high, with full throttle and full mixture with 5, 15, 30, 60 seconds, then the correct throttle starting positions (with full mixture) were 5, 30, 50, 75 % respectively. (The percentages can be seen if the INSTRUMENT DESCRIPTION TOOLTIPS are turned on.) In these cases, it is not possible to start the engine with any other combinations that are listed here: so for example, it's not possible to start the engine if the auxiliary fuel pump was running for 15 seconds, and the throttle (after the fuel pump was turned off) are 5 % or 50 %. So it's pretty good, and very interesting that yes, you have to be careful with the engine.

(3) I was running the engine with 22 IN HG manifold pressure for 4 minutes, the cylinder head temperature went to around 210 C, with cowl flaps open. Then, I turned off the engine for 12 minutes (mixture cut-off, throttle fully closed). And as the documentation says, I was unable to start the engine with the normal cold procedures, but I was able to start it with the hot procedures. Works as expected too. On the other hand, I tried with different combinations, and I was able to start the engine sometimes easily.

Thanks, it really looks like I just didn't understand how the engine works, but I learned a lot.

@gaboro Hi, I submitted a ticket about it for the Duke, which has the same problem. They've been working on it, but haven't found a solution.

That's great to know thank you for the useful replies. The disengagement of the AP at the end of the run up checklist would make sense and is something I hadn't thought about!

Capture.JPG

@Black-Square THANKS for your response and usual pro-attitude regarding researching and fixing things up Nick! That's why Black Square is so good!

jmarkows: I noticed you and I have identical setups as far as 'fixes' applied on the BKSQ Caravan (FD on, jscript edits, etc.) except I am using the PMS50 GTN750 with its own WTT-package and that may be the crux of it, though I've posted at the PMS50 Discord server and they claim its not. I've actually not ever used or tested the 530/430 combo on its own for a flight, and my AP issues are very intermittent, it mostly works well all the time but for rare moments, so its difficult to verify, can't really complain too much.