RandallR

I usually look at a few of them - I certainly appreciate variety.

Piston single: Bonanza Turbo Mod by Young Piston twin: Black Square Piston Duke Turboprop single: Black Square TBM 850 Turboprop twin: Black Square Starship - I try to rotate among a group of aircraft, but every time I start flying this, I have trouble stopping! Bush: Kodiak 100 Bizjet: Asobo Longitude

I had to remove my pedals a few years back as my business required so many multimedia devices they took all of my USB slots. I'll eventually get an expanded USB port and put my pedals back in - they are the best way to go. In the meantime I am surviving with my twist-stick rudder and can do fairly well with it (though it's hurt me a few times): Thrustmaster T.16000M

Though I have FS2024 installed, I'm not using it for flights yet. I believe this info is supposed to be available in the EFB? In FS2020 I can go to the Weather panel from the Toolbar and get the METAR. I usually obtain my weather from the Nav system of the aircraft if flying anything with a g1000 on up to an advanced FMS. Also, there's always https://metar-taf.com/

Absolutely second that 36 final view - one of the best. On 9/11 I was also in the air, but commercial. We were half-way over the pond returning from work in Italy when US airspace was closed and we were sent back to Europe (Schipol) where we spent the next four days stranded with thousands of other travelers. The world was never the same.

If you still have any issues regarding Reverse Thrust, here's some info on the default and some of my assigns: Command - Toggle Reverse Thrust: Keyboard Default: Unassigned! On my throttle: Assigned to a button. One press toggles to reverse. Even though I now move my throttle forward, the prop gives me reverse thrust for braking. Another press of that button toggles back to regular on the prop. I did program an alternate into my own keyboard profile in case I ever lost it on the throttle: Ctrl+R

Tres - there are a lot of things I can't see in your video, especially the MFD instrument display, so I can't tell if you're making throttle changes/settings at the proper time. Also, what are you using for a throttle system - do you have a hardware throttle or throttle quadrant of any kind or are you attempting to run your throttle with keyboard and/or voice commands? If so, it will be quite difficult to control the aircraft, as the TBM doesn't take kindly to a non-peripheral environment. I can tell you I flew the FS2020 version of the TBM several times a few days ago and have experienced no difficulties or changes in aircraft operations. You also stated that you made many flights with the system you were using in your video and that you had no issues until recently. Since I have seen no changes or problems, there is either a conflict with your setup OR the control settings may need to be verified for your throttle. MSFS has a history of inadvertently changing control settings with no warning so I would certainly check that your settings are still in place. Finally - be careful of your procedures - monitor the MFD instruments closely: Set LO-idle AFTER having obtained 13 % of Ng. I reach for the throttle as Ng is passing 12% so I don't engage that position too early. You appeared to move to that position early and that can cause damage. From the manual: When throttle is positioned on LO / IDLE before having obtained 13 % of Ng, there is a risk of overtemperature further to an excessive accumulation of fuel inside the combustion chamber before ignition. I recommend moving the throttle to FLIGHT-idle when Ng is at 52% and run everything from that position (including taxi) until you begin the shut-down sequence. I reach for the throttle for this as soon as it passes 50% and then initiate the move around 52%. You left the throttle in LO-idle for quite a while - I don't recommend this Check your throttle Reverse Axis assignment. It appeared that reverse prop initiated at one point when you were taxiing. If this stayed in reverse, you would no longer have been able to move forward. That's all I can think of for now.

On another note, there will always be a soft spot in my heart for Meigs - I had the pleasure of flying into the field late on an afternoon in 1972. A businessman desperate to make it to a meeting in the Chicago Loop showed up at the FBO's office just before one of my training flights. Considering what the owner was going to get from me for an hour of dual compared to a charter into Chicago my training got cancelled that day. However, I was offered a free seat for the trip. We took the owner's C182 into Meigs and dropped our grateful passenger at the Meigs FBO. We ended up in the Loop at a great restaurant. That night we flew back to our field in Rockford - it was an amazing flight. We lifted off over the dark water at the end of RWY 18, then turned west and flew out over the city. It was one of those amazing nights in Chicago - the weather was clear and the city just sparkled. We could see every bit of traffic going in and out of Midway and O'Hare. It felt like a punch to the gut when Daley destroyed the runway and shut down the field.

Legacy

I was wondering about that - I have 2024 running but the amount of work it will take to transition (set up all of my control parameters, sceneries and aircraft) is going to be substantial, so I still do my daily flying with FS2020.

No, there have not been or have there been added any mods for the aircraft, g3000 or g5000. The add-ons (Navigraph & Bijan seasons) are the same I've been using for years and were present when the Garmin units panning pads worked just fine. The only changes I'm aware of have been required FS2020 updates and maybe one video driver update. Thanks for the feedback - I just wanted to be sure that this was affecting only me.

I updated to the latest nVidia driver and ran another test using the TBM/g3000. No joy. Pressing the joystick just dims the GTC display and no panning or pinch notations appear.

This is not an image of the actual occurrence - I shot it after the touchpad failed to function and I backed out of touchpad access. When it was working, I would press in on the Garmin joystick and the GTC screen displayed the pan & touch indication - it worked great. Now, it just goes dim and doesn't respond. I'm wondering if a driver update I made at about that time is causing the issue. I see that nVidia came out with another driver since then, so I may give it a go and see if the issue is resolved. I'll post back here within a couple of days on how it all went.

Interesting - everything else functions properly - just not the touch pads. It makes me think that there may be a driver issue?

...is no longer functioning. I noticed that I could no longer pan charts in the g3000 and g5000 using the GTC touchpads a few weeks ago. This was a great feature of the Garmin simulations in such aircraft as the TBM and Longitude and simulated the real unit's performance I don't know if this is a glitch from an update or some other issue, but I sure miss the capability. I've attempted to pan the charts with the joystick, but get no response. The touchpad just goes dark and doesn't respond.