Operator error on my part, apparently I wasn't logged in to Discord on sim rig - thanks!

Alright, thanks all

Click on the pilot's headphone jacks (below testing push buttons on the pilot's left subpanel). You can then use the arrows at the periphery of the clickspot, or your mouse wheel to adjust the amount of noise cancellation. Page 111 of the manual for examples.

@slipperfruit said in Why use cockpit blower when you can use alternate blower?: @Black-Square But in cruise, then I always need my cockpit blower to be on... Is it fine if I put my cockpit blower to 50 percent? (cabin temp is 68 fahrenheit/20 celsius) it can get my avionics temp all the way up to 50 celsius/120 fahrenheit If you are not getting warnings on the screen or screens blacking out the temperature is fine there is no need to add additional cooling. Granted this is the virtual space so when the Alt fans burns up from overuse there's no charge to you.

Thanks to all. I just set it to high to see if we can get the feeling back in our fingertips Cheers! EDIT: ffs I even have it highlighted in the manual

Sharing my experience. Below is my post in the PMS50 discord un Jun 29, 2025: Repeatable MSFS2020 CTD when PMS GTN750/650 is used. A/C is BlackSquare Duke. I've been testing this all morning, and can consistently and repeatably cause a CTD at the exact same position only when using the GTN750/650. I have NOTHING in my community folder other than the Blacksquare Duke and the PMS50 GTN750. When I try the exact route with the default DA62, no issues. When I try the exact route with the Blacksquare Duke and GNS530/430, no issues. When I try the exact route with the Blacksquare Duke and PMS50 GTN750, I get a CTD. I did this 4x times, and the CTD repeats consistently. I downloaded and installed the latest version 2.2.48 of the GTN750. Still CTD. If I don't use the GTN750, it does not CTD. I've read many post stating that PMS50 GTN750 cannot cause a CTD. I don't know what to say, but that's not my experience. Here's the flight plan. Cruise altitude is 13,000. Departure time about 10am local. KBTV DCT OMPEE DCT SQUAM DCT LIMER DCT KPWM The CTD occurs about halfway between OMPEE and SQUAM. Update: I still had version 2.2.36 on my PC. I had flown ~60 hrs with this version in the BlackSquare Duke without a single CTD, so I reverted to 2.2.36, and tried the problem flight plan. No CTD. So, I'm back to using 2.2.36 indefinitely. That's fine with me. Also, during my testing I had absolutely nothing else running at all, and it still CTDed. I didn't have any third party apps running.

@dadgametime yes, it's rocking back and forth. But I don't think it stops.

We have the following post that has an explanation of the FS Traffic arrival generation: https://community.justflight.com/post/22215 The post refers to an older build of FS Traffic, however, the comment is still valid for the latest build of FS Traffic and should hopefully answer some of the questions you have regarding the arrival traffic generation. Mark - Just Flight

If I’m in cruise, flying along at a set altitude in ALT mode, and I decide that I need to descend, without touching the AP, if I change the set altitude, the plane starts climbing or descending even if I’ve sent NO commands to the AP to climb or descend.

@Randolf good catch, really seems like that, however, unclear why done like that. Maybe because the screens above the knobs may spend enough light? Interesting. Thanks!

Hell yes! That is exactly it! If you need some support on this, I‘d be happy to do!

That’s the electrical system struggling. You’re lucky you haven’t lost you systems completely. Never ever leave the starter on after you have the engines running. They are a massive drain. Not a bug, a feature.

Can confirm that it's not saved between flights, have to flip it each time. Always exiting with the menu, Win 11, MSFS2020 steam edition

Yes, that's correct.

Ah so it's either/or. Wasn't sure if you had to do both.

I did have fps degradation issues, but they disappeared after a NVIDIA driver update for my VC.

@mxqn it took me a while to figure it out but what worked for me was to move all of the autopilot rotary knob functions into SPAD and make sure there were no duplicate binds in MSFS. In addition to setting up binds for clockwise and counterclockwise for each of the 5 selections (ALT, VS, HDG, CRS, IAS) I also added event triggers for knob push for VS (button 20), HDG (button 19), CRS (button 18), and IAS (button 17) and that prevents the issue where using the rotary knob for anything other than altitude would still change the altitude along with say heading or vertical speed. If I could attach a pic I would. I am glad I finally figured it out, was about to give up on SPAD and not buy a license but now that I understand it I plan to keep it - so maybe I can publish a profile or snippet next week.

I eagerly await the new version of the Cessna Caravan for MSFS2024.

I've never seen that. I use the TM Boeing yoke and assign a trim assignment through MSFS, not a 3rd party app.

@SebAvi Probably because no Starship has been equipped with that.