@JamesLaj On a single engine, try slowing it down to red line (VMC). There should be a strong yaw moment into the dead engine. Report back.

[image: 4b54ed76-cc18-491e-8c94-2c2dd7b3c9b1.jpg] Here's an example. Thermometer settled mid-cabin in the shade for about an hour (FL100). 15 higher than OAT.

@Black-Square Sorry been away flying for a while, so I haven't had a chance to fly until now. The new update is phenomenal!! Engine feels completely alive, the numbers are pretty much spot on. and the sounds are brilliant! Thanks Nick!

@Black-Square Because of the stroboscopic effect whenever I use the rudder trim it looks reversed, only for the rudder trim. I wouldn't mind having the reverse animation lol

@ggabor Been a minute since I've looked, but on PC you can find the state saving file in the MSFS AppData folder and you should be able to edit it.

Yup, managed to get to 279 KTAS at FL 280. [image: 0a9dae00-779a-4877-ac7f-c8a7b84094a6.png]

I've been doing some testing. The plot thickens: This behavior happens in either dual KX 155B units, or TDS GTN750/650 when in VLOC mode. It happens everywhere, not just Alaska. The same behavior happens in the Duke, though it changes from NAV to HDG mode. This behavior is across models, which we know from the Starship thread. When in GPS mode, everything works fine, as I'd expect. Here's where it gets interesting. I use SPAD for all of my planes. For a test, I restarted the sim, spawned the 208 on the runway, did NOT launch Spad but instead "moused it" for everything. No issues whatsoever, stayed in NAV tracking a VOR, departing KPHX 07L, and simply tracking the nearby PXR VOR to the east for 45+ miles. Turned around back to PXR, started Spad, briefly switched from NAV to HDG back to NAV just for kicks, and a couple of minutes later, ROL mode. In SPAD, I've tried both the standard "K:AP_xxx" events as well as the "H:KAP140_PUSH_xxx" commands for NAV/HDG/etc., no difference: I get ROL mode using each. If I start a test flight using SPAD, eventually get the NAV->ROL, and I turn off SPAD, the NAV->ROL issue still occurs. It seems that simply starting SPAD (with my rather extensive profile) correlates with this behavior. I'll look into this some more and report back, perhaps starting with an empty Spad profile and incrementally adding things. (In the meantime, I also might write some Spad code to detect when it goes from NAV to ROL and have it go back to NAV, though that might have some unintended side effects)

thx for confirming. BTW I am currently in Honduras on my way to Belize

BTW it is not only by spawning on Water, same happens if you spawn near a dirt strip. Damage in this case was 5%. Engine was spooling down.

Just a wee bit dark over the Indian Ocean, Mauritius to Colombo. [image: 376cb914-6740-46ee-942a-2609ea502045.png]

The one on flightsim seems to have been taken down. A2a has one that came with the Aerostar but it doesn't seem to work any more either. I'm guessing Asobo broke it with SU4.

@turnandbank oh yeah, different issue then -- I'm referring to the actual gauges. I find the cockpit to be very dark when the outside light is approaching full daylight, making it very difficult to read the gauges even if I scoot my view up a bit. I have a feeling it's a sim issue but maybe it's something else I'm not aware of.

Did you also Clear Engine and Clean Filters?

@Black-Square Sorry Nick, I had to crop the screenshots because 1440 is apparently too big for the forums to handle, and I thought I did a better job describing. And yes, I am in MSFS 2024, which I'm sure I missed saying in the OP. Yes, I have been starting with the propeller feathered, only for the last screenshot with the battery charging and positive instrument air had the propeller out of feather and in the high pitch position. Incidentally, I noticed with the propeller feathered that instrument air and fuel pressure reached nominal levels during startup, and then fell off again. I thought I had been keeping abreast of the propeller RPM issue, but apparently I missed how pervasive it is. Sorry about that. This is the same issue as the generator not being tied to the Ng, and therefore not putting out enough power at lower RPMs?

Hey guys, I don't know exactly how the throttle axis is configured on your TQ6s, but I had good results with my Velocity One quadrant using the MSFS 2024 sensitivity settings. I posted the results here if anyone would be interested in taking a look. This gives me the entire range of forward and reverse travel on one axis and roughly matches the virtual detents with the proper positions on my physical axis, though I don't have physical detents. If you guys have physical detents, this same method should, if I'm understanding it right, allow you to tweak it such that you can match the physical detents to the virtual ones, it might just require a different neutral and Sensitivity+/- settings.

I know this is not what you guys are looking for, but I highly recommend leaving the internal settings behind and switch to something like Axis-and-Ohs, spad.next, Mobiflight etc. This does not only solve the mysterious loosing of controls sometimes it also opens up a lot more options in terms of what you can control. Just as an example I can even manage my sunshades via hardware, every air intake,aso. Initial setup takes a bit longer for every new plane but it is worth it. Only limitation is the number of buttons and axis available as hardware.

@Mark Appreciate it as always.