@Black-Square is it really only with Starship? I thought it would have been being rolled out to the rest of the fleet by now. Not having the workaround is less of an issue for most starting spots, but drastically limits your options for doing multi leg flights without going back to the menu.

@Black-Square Your responses and activity in this forum (and elsewhere, I'm sure), along with the quality of your products are of the highest calibre, sir. Your workloads must be high so I appreciate you having such an active and involved presence amongst the community who are using your aircraft. Keep doing what you're doing - arguably one of the best developers creating some of the best aircraft on the platform and easily the best customer interaction of all that I have seen to date.

@Rivet Thank you for this very nice note. It's always a pleasure to hear how my users are enjoying the aircraft, and that I can bring a little enjoyment to someone's life with my software. Have fun, and let me know if there is ever anything else I can do for you!

@louise No problem. That's what I'm here for! Glad you're enjoying it.

Did you try cycling the avionics selection away from the KLN, and then back to the KLN? I've found that can happen sometimes on rare occasion.

I've been trying to reproduce this for a while now, and then I had a realization. I was surprised to hear this, since it's the same basic battery temperature code I've been using in all my aircraft. I couldn't reproduce this with a 50% drained battery, 140°F ambient temperatures, and maximum electrical load in the aircraft. Then I remembered a problem I hadn't seen since my Analog King Air. MSFS erroneously connects the generator output to the propeller speed, instead of the gas generator in free turbine aircraft. Apparently my last minute beta range changes before release dropped the RPM just low enough in beta that the generator doesn't output sufficient power, and the battery is taking all the load. This problem will go away as a result of my beta range fixes in v1.1, but in the meantime, the fundamental problem is low propeller RPM. If you just keep the power lever at the flight idle detent when you don't need beta for taxiing, the battery will recharge and cool down. Feel free to pass this along to the Official Forums. We're planning on getting v1.1 out this week, as soon as Boris and Just Flight are back from FSWeekend. Sorry for the delay!

@batez No worries

@pequenyo Since I already have my own damage simulation, ideally I would like Asobo's to be completely inert. However, since it's quite confusing that "Aircraft Stress Damage" damages the engine, and not "Engine Stress Damage", I have just fixed the metric that was causing the issue so that the Asobo system will only receive damage long after the limits are exceeded. I still highly recommend disabling "Aircraft Stress Damage" when flying with all of my aircraft; however, since I hate to see anyone's flight ended prematurely by an errant click on the pilot's storm window. Thank you again so much for your helping tracking this one down! I was really losing sleep over it!

Wonderful! Thank you for putting this together. As I said elsewhere earlier, "anyone who labors to improve the experience of our fellow Black Square pilots deserves a heartfelt thank-you"

I asked the PMS50 GTN developer, and I tested some other avionics. It appears this just isn't a commonly supported feature amongst 3rd party GPS units. Kind of a shame, since my Commander 114 will use a similar method with a different autopilot. I suppose I could make the autopilot Altimeter #1, but I'm worried about that causing some undocumented weirdness, like in the HUD, or with ATC, or who knows what else. I figure we could get a solution for this from PMS and TDS pretty easily, but WT's deployment cycle would probably take until a convenient Sim Update.

Took care of the manual. Thank you.

Freeze lat/long retains the geo location, but not the direction. You're better off pressing pause. But a proper anchor/mooring would be the best solution, like in the CAS Cub.

This is actually good point. Most useful when traversing different time zones.

Thanks again.

In this post I explain my method to map a power + beta + reverse to one only lever: https://community.justflight.com/post/48782 It isn't for the Honeycomb, so the values should be different. But the method to configure them is the same. I hope it helps. Regards

@Black-Square No problem! My friend owns the Caravan and he also confirmed that this is happening, so this is probably affecting all Black Square products.