Dave68

My CPU is a Ryzen 5800X3D and my GPU is a RTX 4090. I flew the route again, this time with the Resource Monitor running in the background but it didn't have that 1-second stutter that time and according to the Resource Monitor's graph, only around 1/5 of my total RAM was being used up during that flight. I did another flight from KDAL to KFTW with FS2020 in developer mode and according to the FPS OSD it was peaking at around 5.4GB of RAM and around 4.2GB VRAM usage during that flight and this time I didn't have a 1-second stutter in that area where I had it happen before a few miles west of downtown Dallas. I also have FS2020 installed on my 2nd 980 Pro NVMe which is running at PCI-E 3.0 instead of 4.0 because my motherboard is a B550 chipset one which only supports PCI-E 4.0 on the closer M.2 slot to the CPU, but that shouldn't be causing the 1-second stutters as it still happened when I had FS2020 installed on my 1st 980 Pro NVme that is installed in the PCI-E 4.0 M.2 slot.

I've been doing a flight in the Cessna 152 from Arlington to Waxahachi, TX in FS2020, and I noticed that when I'm around 5 miles north of Midlothian I get a 1-second stutter in the video. I currently have 32GB DDR4-3200 RAM and FS2020 is installed in my 2TB 980 Pro Samsung NVme (installed in the lower M.2 slot which operates at PCI-E 3.0 due to motherboard's limitations) and Windows 11 installed in another 980 Pro Samsung NVme (installed i the upper M.2 slot which operates at PCI-E 4.0). Will upgrading to 64GB RAM eliminate that 1-second stutter in that location or any location that would be prone to this 1-second stutter?

I recently purchased the PMDG DC-6 for MSFS and I'm having an issue that when I enable the gyro pilot and enable the gyro mechanical disconnect, I can't adjust the pitch trim from the Glide and Climb trim wheels. I had Altitude Control disabled like I'm suppose to so that I can adjust the pitch trim while in gyro mode, but even if then no matter how much I scroll the Climb or Glide time wheels, the pitch won't change. Also the main trim wheel is locked for some reason when in gyro mode. Basically, when I enable the gyro mode which is turning on the gyro pilot and turning on the gyro mechanical disconnect, the aircraft will stay the current pitch angle and won't respond to the Glide and Climb pitch wheel input. The only workaround I found was to enable Altitude Control then disable Altitude Control and then I can adjust the pitch trim through the gyro trim wheels. I watched some videos of tutorials/flights with the PMDG DC-6 in MSFS in youtube and they didn't switch on then off the Altitude Control before using the trim wheels and they were using the trim wheels before turning on the Altitude Control. Altitude Control was only turned on when the cruising altitude was established. Anyone else having the same issue I'm having with the PMDG DC-6 in MSFS?

Also the fuel is on the "off" position for all 4 throttles by default if I choose the Ready for TO configuration.

I noticed that when I click on the Ready for TO configuration on the tablet of the BAe 146, that I still have to wait for the engines to spool up one by one and this takes like 3 minutes or so. Is there a way to have it in a state where the engines are already fully spooled up and ready immediately when I start from the gate? Shouldn't the engines be fully spooled up and ready for throttle input by default in a Ready for TO configuration?

I went back to Windows 10. I installed the 526.47 drivers and no CTDs while running MSFS in Windows 10 (22H2) so far whereas I had CTDs with this driver version and some other drivers versions in Windows 11 (22H2). I think I'm going to be sticking with Windows 10 and will never go back to Windows 11.

I tried the 522.30 drivers and I would get the crashing out to the desktop with the overlocking video card message issue just like I did with the 522.25 drivers. The 526.47 drivers didn't have that issue on my system but I did get an issue with pixelated squares on the top 1/8 of my screen while panning in MSFS once I flew over a certain location on a flight from Sacramento to Ontario and that artifacting issue stayed for the rest of the flight and there was also severe stuttering during that artifacting. Weird thing is that this artifacting issue didn't occur in other routes I flew but when I went back to fly the Sacrament-Ontario flight, the artifacting issue happened again starting at around the same location and again for the rest of the flight. So I went back to the 516.94 drivers and with those I didn't get any CTDs in MSFS or artifacting on the Sacramento-Ontario flight. For the Sacramento-Ontario flight I flew the JF BAe 146-200. I haven't gone back to 517.48 drivers and tested for artifacting on the Sacramento-Ontario flight on the JF BAe 146-200 with those drivers.

I didn't mention that the spoilers are on the "rear of the wing". I said "rear of the of the fuselage underneath the tail" and the other spoilers are on the wings.

I'm referring to the airbrake on the rear of the aircraft underneath the tail that deploys when the spoiler lever is moved within the first range of the axis that is before the detent and then then spoilers on the wings that deploys in the next range of the axis after the detent. If you have the JF BAe 146 watching how the spoiler works while in external view should make it easier to understand what I'm what I'm talking about.

In MSFS is it possible to assign a button/key to extend the spoilers one notch at a time and retract the spoilers one notch at a time? In the JF BAe 146 the first extended increment of the spoilers is for the spoiler at the rear of the aircraft's fuselage and the next extended increment is for the spoilers on the wings of the aircraft. I seen some youtube videos of the BAe 146 landing that show that the rear spoiler (1st increment) is deployed shortly before touchdown and the wing spoilers (2nd increment) are deployed immediately on touchdown. I know that in X-Plane 11 a button/key can be assigned to do these functions for the spoilers but I can't find a way to do this in MSFS? I know that I could just pan around in the virtual cockpit with my mouse and drag the spoiler lever to the appropriate increment but I prefer not to do it that way. Also I'm using a Logitech Extreme 3D Pro joystick and therefore don't have a spare axis that I can assign to the spoilers.

Today I installed the 526.47 Game-Ready driver which was released today. I then did a flight from Dallas to Houston in MSFS in the JF BAe 146-200 and no CTD issues so far with this driver.

Is there a way to import a flight plan created through the game's world map into the FMS of the FlyByWire A320? I know that you can import a flight plan created through Sim Brief to this aircraft's FMS but I don't have a subscription to Navigraph which I would have to subscribe to Navigraph if I wanted to create a flight plan in Sim Brief with the latest AIRAC cycle and MSFS uses the latest AIRAC cycle all the time. If I can't do it through the game's world map, are there free alternatives to create a flight plan that uses the same AIRAC cycle as MSFS that works with the FlyByWire's A320 FMS?

It does not matter which aircraft I use either as it also happened while using the stock 747-8i.

I'm also having the same issue on my system in FS2020. I have a GTX 1080 Ti with the version 522.25 NVidia drivers installed. I reverted to 517.48 and the CTD did not reoccur in FS2020. A week later I reinstalled 522.25 and the issue returned 15 minutes into my flight. Both times this issue occurred, it was around 15 minutes into the flight. I was flying the JF BAe 146-200 both times but different routes. I think it's a video driver issue as it did not happen with the previous video driver as I mentioned. I'm also using Windows 11 as the OS. Also a few video driver versions ago, I would get CTD in FS2020 about 15 minutes into flight in Windows 11 but not in Windows 10 with those same video drivers, but those times I did not get that message when the CTD occurred but Event Viewer mentioned something about the NVidia display driver stopped responding during those time points of the CTDs. Also just before the CTD happens, the sim freezes for 3 seconds.

For those who have FSRealistic, does FSRealistic require manually opening up as a separate program first before starting FS2020 every time you want to use FSRealistic or once it's installed and activated is it transparent to the user from that point on?

I noticed that frequently whenever I load my saved camera cockpit view for the captain, it will go to the default captain view and then I have to press the key again to go to my saved captain view. Also when I pan to a certain spot in the cockpit, if I press the key to go to my saved captain view the view will only pan back halfway and I have to press the key again to get to my saved captain view. I just want it to go to my saved captain view directly each time I press the key I assigned to load my saved captain view. For my saved captain view I assigned numpad 4 and made sure that key wasn't assigned to anything else. Am I missing something in the settings here or is this a glitch in the camera loading of customs cockpit views in FS2020? I never had an issue like this in X-Plane 11.

Anyone here played FS2020 using the XBox Series X and a PC? If so, what would be the approximate Terrain LOD on the XBox Series X by a visual estimation?

Not really a problem, at least for now, as I think terrain at 300 with photogrammetry turned on is a good balance for my system. However, I have aircraft traffic and airport traffic turned off. I'm thinking about future headroom for DLC that might tank the fps further. However, in the future if a realistic AI aircraft traffic DLC and I decide to purchase it in the future that 29 fps could turn into 15-20 fps if it does not use a separate core for AI traffic. At LAX I get 27 fps right now with terrain LOD at 300 and photogrammetry enabled, and if I decided to add aircraft traffic (I don't like the stock AI aircraft traffic so I keep that disabled) in the future from a 3rd party, that 27 fps could turn into 14-18 fps if it does not use a separate core.

My system: Ryzen 5800x, Asus B550-F (Wi-Fi) motherboard, 32GB DDR4-3200, GTX 1080 Ti, 2TB 970 EVO Plus (Games), 2TB 980 Pro (Windows 11 OS) Render scale at 100 and screen resolution at 1080p, Ultra preset

Is it normal for Photogrammetry to cause a huge performance hit in FS2020 when at airports? For example, at CYQG, with photogrammetry enabled I get 25 fps sitting on runway 25 on the Cessna 172 G1000. With photogrammetry disabled I get 57 fps in the same spot. I disable vsync and uncap the fps for performance testing purposes only. This is with the terrain LOD set to 400 which I recently set to and that could be why I noticed the frame rate hit with photogrammetry enabled as it goes well below my capped 30 fps. With terrain LOD set to 200 (which I formerly had it set to), I get 39 fps at that spot with photogrammetry enabled and 75 fps with photogrammetry disabled, still a huge difference in fps between photogrammetry enabled and disabled. With terrain LOD set to 300 (which I also tried for a few days), I get 29 fps at that spot with photogrammetry enabled and 71 fps with photogrammetry disabled, still a huge difference in fps between photogrammetry enabled and disabled.When I'm actually in the air, the frame rates are much higher, even with photogrammetry enabled. I noticed that the type of aircraft does not make a difference in frame rates when I have the fps hit with photogrammetry turned on as frame rates are the same at that spot whether I'm using the 747-8i or the Cessna 172 (Classic). I also get less than 30 fps at other airports if I have photogrammetry turned on (with terrain LOD set to 400) and type of aircraft not making any difference in fps. So to sum it up: Terrian LOD at 400 (CYQG Rwy 25) Photogrammetry On - 25 fps Photogrammetry Off - 57 fps Terrain LOD at 300 (CYQG Rwy 25) Photogrammetry On - 29 fps Photogrammetry Off - 71 fps Terrain LOD at 200 (CYQG Rwy 25) Photogrammetry On - 39 fps Photogrammetry Off - 75 fps

Since installing today's hotfix, I got one CTD and that happened when I was 50 meters from the runway on final to Big Bear Airport. I took off from LAX. I was flying the Carenado CT182T and it happened about 45 minutes into the flight near the end of the flight. I had a CTD in MSFS in the early part of this year as well but on the 747-8i on approach to LAX, about a 10 mile radius from where I experienced the CTD today. I wonder if I corrupted something when I force closed MSFS when it was looping in the update endlessly in the installation manager screen and if I should uninstall MSFS and redownload the whole game again. I did that for the updated version before this hotfix was available and I don't look forward to redownloading the whole game again if it must be done. I did backup the Flight Simulator Packages folder before the hotfix was available but I wonder if that backup is now useless if I should be redownloading the whole game with the hotfix.

I'm having an issue updating MSFS with today's hotfix. It is looping at 7.90 KiB at 3% for the past 10 minutes and showing downloading A320 Neo Patch 1.95 over and over again. Anyone else having this issue?

The latest update that was released a few days ago solved the terrible stuttering I had in the Los Angeles area. In fact it seems the sim is running smoother everywhere else as well on my system than before this update and now I'm getting higher frame rates as well in the sim, for example at a certain airport I was getting 49 fps before the update and now I'm getting 74 fps at the same airport with the same aircraft. However, one issue that I'm now have is that when I pan vertically using the hat switch on my Logitech 3D Extreme joystick, when the viewpoint centers on the yoke, the panning hitches for like a millisecond while I'm sitting at the runway, but during flight, that hitch is gone. It does not seem to matter the aircraft I use or airport I'm at when this happens. Anyone else having this issue? I also moved my 2TB NVMe to the top M.2 slot of my motherboard which uses the CPU lanes instead of the chipset lanes for less latency even though it's a PCI-E 3.0 NVMe, so I'm not sure how much of a role that played in the smoothness of the sim as I reinstalled Windows 10 and MSFS after moving my 2TB NVMe to the top M.2 slot. Before I had my 2TB NVMe on the bottom m.2 slot which uses the chipset lane and had my 250GB NVMe for just the OS and basic programs on the top M.2 slot, now I have the OS and games include MSFS installed on the 2TB NVMe and decided to ditch my 250GB NVMe.

I shouldn't have to artificially downgrade my internet download speed either to get a reliable download, especially using a 3rd party program to do it. Unless my internet connection is unstable at it's rated speed, such as getting packet loss during downloads, I really shouldn't have to do that, and even if I do experience unreliable internet at the speed I'm suppose to be getting, I should contact my ISP about it and not run a 3rd party program to artificially slow it down to get a reliable connection not to mention that downloading through the MS Store never gets even close to my full download connection speed anyways. I'm on a 100 mbps plan and the fastest download speed I ever got from the MS Store when downloading this game was 85 mbps for a bit and then it went quickly back down and it usually hovered between 7-8 mbps while download this game from the MS Store. Also I finally got MSFS installed yesterday and didn't even need to slow down my internet speed to do it like you suggested and this time without the looping issue during the download at that particular spot. Also I noticed that this time, the installation didn't create a Program Files, Window Apps, and WPSystem folders on my D drive this time. The D drive is where I have MSFS installed. The only reason why I reinstalled Windows was in case there were any traces of MSFS and it's associated files left that could have possibly interfered with redownloading MSFS. Also would edited camera files for aircraft in MSFS interfere with downloading updates? Could that explain the looping problem I had with downloading those updates to the 747-8i, which is one of the aircraft I edited the camera.cfg file? I read that some people had to remove mods to get this game to update successfully, and I'm wondering if that includes user-edited camera.cfg files?

Yesterday I was trying to install the update for Flight Simulator (2020) and at around 18GB downloaded it kept looping between 18GB-18.26GB at 312 of 353 and I let it go on for about an hour it the update download still kept looping at the same 2 items. The items were a couple of the the 747-8i patches. When it hit 18.26GB it went back down to 18.06GB and started downloading those items again and did this repeating until I quit the update download and decided to just uninstall Flight Simulator (2020) to do a clean install of the game and even then it would not respond when I clicked on play. I finally found out on my own that I had to install the Digital Ownership app before clicking on play. I also ended up reinstalling Windows 10 and removing the folders that the previous Flight Simulator installation left on my D: drive during the troubleshooting. Finally at this point I'm almost done downloading Flight Simulator. Is a full clean install more reliable than just updating Flight Simulator each time an update for Flight Simulator is released? I never had so much trouble installing Flight Simulator as I did today and the recent update that was released yesterday was the first time I could not update Flight Simulator from my existing installation of Flight Simulator.