jfitler

I'm a bit confused. Ctrl+8 (or Ctrl+8 numpad, or Ctrl+F8), do nothing on my system. Is it supposed to pull up a pop-up window of some sort (like on a 2D panel?) Every available switch on the TBM panel appears to be accessible thru the VC, and none seem to be related to avionics power. I should add that this issue (avionics displays blank) occurs roughly every third time the aircraft is loaded. Normally, the Garmin displays power up when the battery switch is thrown. Those instances where this doesn't happen are the ones that have me looking for a dedicated avionics power switch that all of the other cockpits appear to have.

Now that we are several updates into MSFS, I'm going to finally give the TBM another shot (I had several problems with this airplane in the initial release, and have been avoiding it.) Just one question... Where in the heck is the avionics power switch? I've been through every inch of the panel, figured out the bizarre "crash bar" feature on the battery/GPU switches, but no luck. I apologize in advance if this is another in a series of "brain farts" on my part, but can someone give me a hint? Thanks!

An update to overhaul PHNL / Hickam would be nice, too. (a la FSDreamTeam) !

I have exactly the same problem. Makes communicating with ATC and taxiing at the same time a whole lot of fun! It sounds as though this is an identified problem and is in the queue for getting fixed. I know that there is at least one bug report filed through Zendesk on this issue. Hopefully it will get addressed soon.

Do you happen to have dual or multiple monitors? I've found that once my mouse cursor crosses over to my second monitor (where I have the ATC window and moving map), then my joystick becomes unresponsive. As soon as I move the cursor back to my main display, the joystick comes back.

I remember seeing Flight II (originally A2-FS1) on a green screen Apple II (with the awesome 16k RAM card upgrade, of course) in 1977. Clunky as it was by today's standards, it was the coolest thing I had ever seen. And I was hooked!

There was nothing that came up that indicated that I could redirect where my "packages" directory was to be located, much less the "community" directory that I was looking for. If it was indicated, then it certainly did not make it clear that this was the point where you had the opportunity to define how the directory structure was to be laid out. The process is not even remotely intuitive in that regard!

Well, I just blew away everything in my Community folder, de-installed MSFS, and did a complete reinstall. Nowhere did it give me any option as to where to install the program, other than a drop-down menu that let me select which drive I wanted it to go to. No subdirectory, directory path, nothing. I was just able to point it to my external M: drive, and that was it. MSFS again set up the very same convoluted multi level directory structure that it set up the first time. I don't know how you were able to specify a directory path for installation. I was given a drop-down menu with available drive letters, and that was it. MSFS took it from there. This was with the Microsoft store install version.

Cruising yesterday in the Cessna Caravan on autopilot at 7000' over northern Ontario. Encountered moderate window icing in clouds, so I flipped the deice system from airframe to windshield. The moment I flipped the switch, it was pitch up, snap-roll right and down we go. The classic MSFS autopilot bug. It was especially discouraging since (for me) the Caravan has been the least amount of trouble, in terms of "bugginess". So today, I attempted to continue my flight from CYSK to CYQB in the Caravan. Again at 7000, fair weather. This time, about 30 minutes into the flight, I requested flight following and was acknowledging my squawk code setting (hitting "1" on keyboard since clicking on the ATC box works only half the time, but that's another problem). As soon as I pressed "1", guess what... pitch up, snap-roll right and down we go. And the aircraft would no longer follow heading settings input into the autopilot from that point. I've been exposed to enough software package releases to know that it's going to be a while before all the bugs get ironed out, especially with a package this complex. I'm just praying that it doesn't get into a cycle where each concurrent patch/hotfix/service pack, whatever - doesn't break more things than it repairs. Trying to hang on and stay positive. I know this sim has an awesome future ahead. I just hope I'm there to see it!

Thank Tiger for the tip on the transparent tooltip mod. I'll have to try it! I actually tried the numeric method on the ATC window first (it was the method I used most frequently in FSX), and couldn't activate a message that way, either.

First off, I am aware that the developers have their hands full with more important operational issues with FS2020 than the ones I am listing here. These that I am listing are not "show stoppers" by any stretch of the imagination - just my own "jot down" list of issues that I have encountered that I thought I would share. - At most airports, the blue taxiway lighting is randomly installed all over the place, though most of it is usually near a taxiway at least. - At night, green/white airport beacons are usually not visible until you are 1.5 to 2 miles from the airport (actually MS has not gotten this right in Flight Simulator for quite some time). - Random airport vehicles (buses, forklifts, etc) running wild on the taxiways. - Absurdly large mouse-over pop-up panel labels that cannot be turned off or made smaller. - On multi-monitor system, input device (joystick, yoke, etc) stops functioning the instant that the mouse cursor crosses over to second monitor. Putting cursor back on main display resumes functionality. - ATC window interface is "clunky" - sometimes does not respond to mouse clicks, requiring ATC window to be closed and reopened.

Well, update 1.10.8.0 seems to have remedied the CTD issues that 1.10.7.0 seemed to be causing. Two extended flights since the latest update and no CTDs. Encouraging, but time will tell.

Thanks for the tip! Will check into it.

Having MSFS bury the Community folder 11 levels down in my empty external drive was bad enough, but check out the ridiculous 44 character-long directory name it created on level 2...

I wish I'd tried that before letting MSFS generate all of the ridiculous subfolder structure that it came up with when I simply pointed it to M: I'd like to clean up the path leading to my Community folder on my M: drive, but I've got a feeling I would have to do a reinstall. I have the store version as well.

Since installing update 1.10.7.0 yesterday, I have flown two routine flights. Both ended in CTDs after about 10 minutes of flight time. This is not a good sign. I've had no CTD issues prior to this.

Sorry... I was referring to Windows Administrator mode, not MSFS's Developer mode.

Is anyone aware of there being any particular benefit (or hindrance) to running MSFS in administrator mode?

Fuel state around 65%, auto crossfeed enabled so the aircraft was completely in balance. It wasn't a gradual thing... one minute level and stable, then bam! Totally out of control. Almost exactly like what happens when you exit the disastrous "active pause" feature while in flight.

I know that the autopilot issue(s) have been thoroughly documented, but thought I would share my latest experience. Cruising at FL 140 in the Kingair, about an hour into a flight from KMCD to KCWF. Without warning the aircraft suddenly went nose up, snap rolled violently right and went immediately into a tailspin. While attempting to regain control, I switched to the external view and noticed that the elevator trim tabs were in the full nose-up position, and toggling the autopilot master switch had no effect on this. Fought the airplane all the way down to a (marginal) landing since now it flew like a dumpster in a tornado. The flight dynamics seemed to have been corrupted independent of the autopilot. Restarted MSFS and reloaded the aircraft and all was well - for now. Kind of disheartening because to this point I have never had an autopilot problem with the Kingair at all, believe it or not. I can't wait for this one to get sorted out.

Odd. When I installed it, I selected the destination as my M: drive, and MSFS took it from there. It created the complex path structure to the Community folder that I have in my screenshot below. Did you modify your directory path after MSFS installation?

When I installed MSFS, I directed the installation to my external 1Tb SSD, my drive M: Below is the path structure that MSFS set up to my M: drive. This directory path is quite convoluted (I have no idea why) which, when added to already very lengthy file names in MSFS, really eat into that 259 character path name limitation. I am just curious if anyone else that has installed to a non-C: drive location has a Community path structure similar to this?

I have a similar dual monitor setup - ac/panel on left display, on the right I typically have the ATC window, FlightShare and FSTramp. The instant that my mouse cursor crosses over to the right hand monitor, my joystick freezes and is unresponsive. A real pain when taxiing. Simple moving the cursor back to the left hand monitor returns everything to normal. I've used this setup for years on FSX without any problems whatsoever. Something has indeed changed in the way MSFS handles display focus.

Just like I-77 in the springtime! :)