Dave68

Now that MSFS has been released for XBox One Series X and S, I wonder if it runs without stutters in those areas in the Los Angeles that I experienced the terrible stuttering with my PC. The XBox One Series X has a more powerful GPU than a GTX 1080 Ti which is what I have plus it most likely has been optimized for XBox One Series X and S consoles and despite the CPU being slower than a Ryzen 5800x, after optimizations I'm guessing that it should be around 5800x performance the the XBox One Series X in terms of CPU and 3070 performance in terms of GPU and less stutters? Anyone here play it on both with a PC with a Ryzen 5600X-5900X with an RTX 3070-3080 and an XBox One Series X and on which system did it play smoother?

For FS2020, if buying right now, I'd recommend a Ryzen 5600X or better if you want go with AMD or an i5-11600k or better if you want to go with Intel. An i5-10600k is also fine for FS2020 but the 11600k is only $20 more than the 10600k at Microcenter. 6 cores with Hyperthreading/SMT is enough for FS2020 and single-threaded performance is a more important factor for FS2020 when it comes to frame rates and going past 6 cores with HT/SMT won't really do anything for FS2020 for frame rates, maybe load times would be shorter but I'm not even sure about that and FS2020 has super long load times even on my Ryzen 5800x with a 970 EVO Plus NVMe SSD. For RAM, I recommend 32GB DDR4-3200 with CL-16 or lower latency. You can go higher than DDR4-3200 RAM but it may or may not run stable since those CPU's don't officially support faster than DDR4-3200. For a video card, if you are going to do 4k, I recommend at least an RTX 3080 if you can get one at MSRP which is impossible right now. The RTX 3080 Ti was released yesterday but now they are sold out everywhere I checked, ebay does not count in my opinion. The RTX 3070 Ti will be released in 2 days, but I have doubts that 8GB of VRAM is enough for 4k in FS2020, especially if you want to maximize graphics settings at 4k. If you are only going to be playing FS2020 at 1080p, then I think a RTX 3060 Ti would be fine. I'd recommend that you install FS2020 to a fast SATA SSD or a NVMe SSD (I didn't notice any difference for load times in FS2020 between my Samsung 850 EVO SATA SSD and my Samsung 970 EVO Plus NVMe SSD, maybe there was a few seconds difference but I didn't time it.) SATA SSD's are a little cheaper than NVMe SSD's currently. However, I did notice that my NVMe SSD does load Windows 10 faster than my SATA SSD even though loading Windows 10 on my SATA SSD was still quick, it's just that my NVMe SSD loads Wnidows 10 quicker.

Well a few days ago I installed the latest update to FS2020. I still get the stuttering at the exact same locations in Los Angeles. Also recently my internet got a free upgrade to 100 mbps download speed and that did not get rid of that stuttering. It's just as bad as before the internet speed upgrade. I wonder if upgrading to a 3080 Ti will get rid of it even if it doesn't I still plan to get one if I can get one at no higher than MSRP price as I plan to upgrade to a 4k TV later this year.

It does it for me no matter which aircraft I fly it still happens. Also everything on lowest settings except keeping resolution at 1920x1080, it still stutters in that area in my system, only then the stutters are greatly reduced in both frequency and duration, but they are still there. Even with Game Mode turned off it still happens. Is it possible that the chipset latency from connection to the NVMe SSD in my system is being a bottleneck in that area of Los Angeles, since I'm using the lower M2 slot for the NVMe SSD that is storing my games and data? It did this on my SATA SSD drive as well as I mentioned before and SATA goes through the chipset as well. What motherboard and CPU are you using and are you using a SATA SSD or an NVMe SSD. If you installed FS2020 on an NVMe SSD, is it inserted in the upper M2 or lower M2 slot? Just trying to find out if there is some kind of bottleneck in my system that is responsible for the stuttering in that area. Here's my system configuration: Ryzen 5800x Asus B550-F Gaming Strix (Wi-Fi) GTX 1080 Ti 32GB DDR-3200 2TB Samsung 970 EVO Plus NVMe (Data/Games) 250GB Samsung 970 EVO Plus NVMe (Windows 10) Seasonic Focus GX 850 Power Supply

When I takeoff from LAX rwy 7L, flying at a 70 degree direction and I level off at 3000', the stutters start at around 2-3 miles west of the Los Angeles river for me. This stutterfest keeps going until I'm around parallel to ONT.

I'm wondering if these stutters will be solve if I switch M2 slots for my SSD's in my PC or if I just remove my 250GB Samsung 970 EVO Plus and just install everything on my 2TB Samsung 970 EVO Plus but make a dedicated 250GB partition for Windows/basic apps and the rest partitioned for games and data storage. Right now my 2TB Samsung 970 EVO Plus is installed on the bottom M2 slot which is the slot that uses the chipset lanes and my 250GB Samsung 970 EVO Plus is installed on the upper M2 slot which uses the CPU lanes. The 250GB SSD is just for the OS and basic apps and my 2TB SSD is for games including FS2020, and basic data storage. So will the reduced latency of utilizing the CPU lanes instead of the chipset lanes solve this stuttering? Do any of you that are getting these stutters as well, do you have an NVMe SSD (which FS2020 is installed on) installed on the top M2 (CPU lanes) or bottom M2 slot (chipset lanes)? Those that are not getting these stutters, same question. I have an Asus B550-F Gaming (Wi-Fi) motherboard and both M2 slots are PCI-E 3.0 but the upper one uses the CPU lanes therefore the upper M2 slot has less latency than the lower M2 slot on this motherboard.

I installed the Take Ownership registry hack and disabled fullscreen optimizations for the FlightSimulator.exe file. I saw no reductions in the stutters.

Correction: I meant setting terrain detail to 20.

With the most recent update as of this date I'm still getting the same stutters in that certain area in Los Angeles. In fact now I'm noticing the same stutters even with photogrammetry scenery disabled and just using the generic scenery whereas I it did not happen on my system before that update when photogrammetry scenery was disabled. Turning down the texture detail setting from 200 to 20 got rid of most of those stutters but it still has those stutters, the pauses just don't last as long in that area of Los Angeles and it look much worse at the 20 than 200 in my opinion. I thought that this update was suppose to fix stuttering issue but it mentioned it was for the DFW area and nothing mentioned for the LA area. My system is not running out of free VRAM as check with the Developer Menu turned on, not even close to the VRAM capacity of my video card when those stutters happen, so it's not a lack of VRAM issue with my system. It's SSD speed either as I used to have this game installed on my Samsung 850 EVO SSD and moved it to my Samsung 970 EVO Plus SSD and those stutters did not seem to shorten from that upgrade. Is FS2020 too much for the Directx 11 API to handle, especially in that area in Los Angeles. I'm no computer engineer, but I read that Directx has a huge limitation in draw calls compared to direct hardware accessing and I'm wondering if there are not enough draw calls sent from the API when this stuttering happens in that area in Los Angeles. I also have X-Plane 11 and ever since the 11.50 update that has the Vulkan option, X-Plane 11 has been running much smoother on my system, hardly a stutter on my system at the airports where I experienced the stuttering before the 11.50 update, and I'm wondering if the DirectX 11 API limitation has been reached with FS2020. Do you think it has or do you know if it has? I also set my rolling cache to 400GB on a 500GB Samsung 860 EVO that has nothing else on it, no difference, even the second time I flew over that area with that 400GB rolling cache.

I replaced my Samsung 2TB 850 EVO SSD with a Samsung 2TB 970 EVO Plus SSD and still no improvement in the stutters, especially those 2-4 second hitches while flying over that area in LA. I lowered the Texture Supersampling from 6x6 to 4x4. Objects Level of Detail from 200 to 100. Anti-Aliasing from TAA to FXAA. Terrain Level of Detail from 200 to 100. Shadow Maps from 2048 to 1024. Also no improvement in the stutters turning down those graphics settings. Once I'm crossing south in parallel of Ontario International Airport, those 2-4 second random hitches subside and the regular random stuttering stays. Also it happens when flying towards Bob Hope Airport as I get near downtown LA. Here's my system configuration: Ryzen 7 5800x 32GB DDR4-3200 Crucial Ballistix Gaming Asus B550-F Strix (Wi-Fi) motherboard EVGA GTX 1080Ti SC Black 250GB Samsung 970 EVO Plus (OS) 2TB Samsung 970 EVO Plus (Games/Data) Windows 10 Pro

I got around this issue by running the reinstall of FS (2020). I wonder what it did during the reinstall as it only downloaded 1.3GB, did not prompt me about the location of the Packages folder. Before when I reinstalled this game it did prompt me after the 1.3GB download as to where I want the Packages folder to install but this time it didn't. Is it possible that if Microsoft detects a different drive model that this game is installed on than before from the cloning it will see it as a different computer even though it the same computer, for just a drive change even with the same drive letter assigned as before to this game or did I screw something up by deleting those folders on the my old drive after the cloning?

Today I purchased a 2TB 970 EVO Plus SSD and cloned my old SSD to the new drive. I also deleted the Program Files and WindowsApps directories off the old drive after cloning to the new drive, as the hassle it was due to permissions in those directories and the steps I researched to get around this so I could delete these folders. I used Macrium Reflect to clone my old drive to the new drive. Now when I try to open FS (2020) I get a message saying: This app can't open Microsoft Flight Simulator can't open because it is offline. The Storage device might be missing or disconnected. See in Store I purchased this game through the Windows store. Those 2 folders did transfer to the new drive during the clone process so that's why I did not see the need to still have them on the old drive, especially when the new drive has the same drive letter as my old drive had and my old drive I changed the drive letter to E and redirected my user folders to the old drive.

I don't use a rolling cache and I disabled and deleted the rolling cache file after installing the game.

I set a -200MHz offset on the GPU clock and it still is doing those pauses while flying of the LA metropolitan area and the other stuttering is still there. The pauses start happening once I'm about 3 miles south of downtown LA, continuing flying eastward. I took off from KLAX RWY 25R on the Carenado CT182T and my destination was KONT. Cruise level was 5000'.

I did not overclock my GPU. However, it's an EVGA GTX 1080Ti SC Black Edition, which is a factory-overclocked card, so I see no reason to "underclock" it. Even if I "underclocked" it to the standard reference clock, and it did not solve those pauses, it could still be because of a defective GPU, and if it did fix the issue then the GPU is definitely defective since it won't run stable at it's factory advertised clocks. I"m also using a Seasonic Focus GX-850 power supply currently. In my old system I was using a CoolerMaster Silent Pro Gold 800W power supply and had the same issue.

Ultra settings and 1920x1080. However, I have AI aircraft traffic and airport ground ambient traffic turned off. Actual frame rates more than doubled for me with this system upgrade and still using the same video card and internet speed. Maybe 50 mbps download speed is not enough for Ultra settings without stuttering? I don't think my 1080 Ti is a bottleneck at 1920x1080 in this game as I was reading benchmark chart in an article online comparing CPU's and GPU's in this game and it showed the 1080 Ti close to the 2080 Ti at 1920x1080, but at 4k in this game the difference between those 2 GPUs was huge, but I'm not playing this game at 4k as I don't have a 4k monitor.

I disabled vsync just to get an accurate test result when comparing before and after the upgrade but I actually play the game with the frame rate locked at 30 set through the Nvidia Control Panel otherwise using the Developer Menu's FPS Display it would have read 22 before the upgrade and 30 after the upgrade instead of 53 after the upgrade if I limited to 30 during the test.

I recently upgrade from an i7-4930k, 32GB DDR3-1600 system to a Ryzen 5800x, 32GB DDR4-3200 system and I'm still getting terrible stuttering while flying over the Los Angeles metropolitan area. The stuttering is several pauses of 2-3 seconds long along with milder stuttering. When there is no stuttering, the frame rates are fine. Also with these pause-stutters I'm getting 2-3 second input lag, until everything is smooth again. Also the scenery will get blurry for about a second sometimes during these pauses. If I disable photogrammetry scenery, then these pauses don't happen but the less severe sutters still happen but then I get generic scenery and textures, and I find this as an unacceptable workaround because in my opinion one of the main attractions of this game is the photogrammertry scenery during a VFR flight. I did get a good increase in frame rates since upgrading to a faster PC recently. Frame rates went from about 22 fps before the upgrade to about 53 fps (at the same spot which I chose as Vancouver International Airport, RWY 8R, inside the 747) after the upgrade. Also I'm on a 45 mbps downstream plan (effectively 50 mbps measured from Speedtest.net). I have Flight Simulator installed on a Samsung 850 EVO 2TB SSD. My GPU is a GTX 1080 Ti. Those are the only components I transferred to the new system from the old system. Is there a bottleneck somewhere in my new system that is causing these stutters/pauses that were also present on my old system?

Right now when I click on FS2020, it won't start. Actually Forza Motorsport 7 won't start either. Anyone here having issues starting FS2020 right now or is it just on my end? Also this happened yesterday as well but later was working. I purchased FS2020 from the MS Store if that makes a difference.

Can any 3rd party DLC selling through the Marketplace in FS2020 still require activation keys to activate or is the DLC once purchased through the Marketplace in FS2020, tied to the purchaser's Microsoft account without requiring an activation key?

Does FS2020 have a minimum frame rate that must not be dropped below like X-Plane 11 does before it runs slower than real-time? If so what is the minimum frame rate I must achieve in FS2020 in order to stay in real-time?

Is there a way to increase the volume in FS2020? It's already maxed out by default in the game but I still want it a little louder and my physical speaker volume is at my preferred setting and Windows volume is at 100%. My other games are not this quiet.

I play other PC games besides flight sims on my gaming PC. Wouldn't a PC that is powerful enough for flight sims be powerful enough for gaming as well or are most flight simmers dedicating their PC just for flight sims and just use a console for gaming if they game at all despite having a high powered PC or do mean that most flight simmers don't play other games period whether it's console or PC gaming? I can understand that if someone uses the PC for a home-built flight sim cockpit not wanting to use that same PC for other PC games besides flight sims, but I just use a basic joystick for flight sims, don't have a home-built cockpit, no multi-monitor setup, and use a basic computer desk, and of course an XBox One X controller for other PC games. I guess I'm not a true flight simmer, but more of a general PC gamer?

Is it normal to have to press the that button twice to get to my saved view for Camera 0? I just want it to go straight to my custom saved view with a single button press from my joystick from whatever direction I'm viewing inside the cockpit and it is not doing that. It will do it on the 2nd press of the joystick button.

Yes, that's what I meant to say.